^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1) ULPI bus binding
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2) ----------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 3)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 4) Phys that are behind a ULPI connection can be described with the following
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 5) binding. The host controller shall have a "ulpi" named node as a child, and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 6) that node shall have one enabled node underneath it representing the ulpi
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7) device on the bus.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9) EXAMPLE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) -------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) usb {
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) compatible = "vendor,usb-controller";
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) ulpi {
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) phy {
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) compatible = "vendor,phy";
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) };
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) };
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20) };