summaryrefslogtreecommitdiffstats
path: root/lib/earlycpio.c
diff options
context:
space:
mode:
authorHeikki Krogerus <heikki.krogerus@linux.intel.com>2015-05-13 15:26:42 +0300
committerFelipe Balbi <balbi@ti.com>2015-05-13 12:04:55 -0500
commit289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f (patch)
tree7c5156a0a503fccc18a449de06edda6c07060160 /lib/earlycpio.c
parent3521a399dae8d66fc784cef70a78e65ce73e364f (diff)
downloadop-kernel-dev-289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f.zip
op-kernel-dev-289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f.tar.gz
usb: add bus type for USB ULPI
UTMI+ Low Pin Interface (ULPI) is a commonly used PHY interface for USB 2.0. The ULPI specification describes a standard set of registers which the vendors can extend for their specific needs. ULPI PHYs provide often functions such as charger detection and ADP sensing and probing. There are two major issues that the bus type is meant to tackle: Firstly, ULPI registers are accessed from the controller. The bus provides convenient method for the controller drivers to share that access with the actual PHY drivers. Secondly, there are already platforms that assume ULPI PHYs are runtime detected, such as many Intel Baytrail based platforms. They do not provide any kind of hardware description for the ULPI PHYs like separate ACPI device object that could be used to enumerate a device from. Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com> Acked-by: David Cohen <david.a.cohen@linux.intel.com> Signed-off-by: Felipe Balbi <balbi@ti.com>
Diffstat (limited to 'lib/earlycpio.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud