linux-toradex.git/include/linux/usb/phy.h, branch v3.17-rc4

usb: phy: Add set_wakeup API

2014-03-05T20:40:08+00:00

This API is used to set wakeup enable at PHY registers, in that
case, the PHY can be waken up from suspend due to external events,
like vbus change, dp/dm change and id change.

Signed-off-by: Peter Chen 
Signed-off-by: Felipe Balbi

usb: phy: protect against NULL phy pointers

2013-07-29T10:56:45+00:00

In order to decrease the amount of work done
by PHY users, allow NULL phy pointers to be
passed.

Signed-off-by: Felipe Balbi

usb: add devicetree helpers for determining dr_mode and phy_type

2013-06-17T20:47:09+00:00

This adds two little devicetree helper functions for determining the
dr_mode (host, peripheral, otg) and phy_type (utmi, ulpi,...) from
the devicetree.

Signed-off-by: Michael Grzeschik 
Signed-off-by: Marc Kleine-Budde 
Signed-off-by: Sascha Hauer 
Acked-by: Felipe Balbi 
Signed-off-by: Alexander Shishkin 
Signed-off-by: Greg Kroah-Hartman

usb: phy: return -ENXIO when PHY layer isn't enabled

2013-03-18T09:18:26+00:00

in cases where PHY layer isn't enabled, we want
to still return an error code (actually an error
pointer) so that our users don't need to cope with
either error pointer of NULL.

This will simplify users as below:

-	return IS_ERR(phy) ? PTR_ERR(phy) : -ENODEV;
+	return PTR_ERR(phy);

Acked-by: Kishon Vijay Abraham I 
Reported-by: Alan Stern 
Signed-off-by: Felipe Balbi

usb: phy: introduce ->set_vbus() method

2013-03-18T09:18:09+00:00

this method will be used to enable or disable
the charge pump.

Whenever we have DRD devices, we need to be
able to turn VBUS on or off whenever we want.

Note that in the ideal case, this would be
controlled by the ID-pin Interrupt, but not
all devices have ID-pin properly routed since
manufacturers can choose to save that trace
if they're building a host-only product out
of a DRD IP.

This is also useful during debugging where
we might not have the proper cable hanging
around.

Signed-off-by: Felipe Balbi

usb: phy: make it a menuconfig

2013-03-18T09:18:05+00:00

We already have a considerable amount of USB
PHY drivers, making it a menuconfig just
prevents us from adding too much churn to
USB's menuconfig.

While at that, also select USB_OTG_UTILS from
this new menuconfig just to keep backwards
compatibility until we manage to remove
that symbol.

Signed-off-by: Felipe Balbi

usb: otg: add device tree support to otg library

2013-01-25T08:20:14+00:00

Added an API devm_usb_get_phy_by_phandle(), to get usb phy by passing a
device node phandle value. This function will return a pointer to
the phy on success, -EPROBE_DEFER if there is a device_node for the phandle,
but the phy has not been added, or a ERR_PTR() otherwise.

Cc: Marc Kleine-Budde 
Signed-off-by: Kishon Vijay Abraham I 
Signed-off-by: Felipe Balbi

usb: otg: utils: add facilities in phy lib to support multiple PHYs of same type

2013-01-25T08:20:14+00:00

In order to add support for multipe PHY's of the same type, new API's
for adding PHY and getting PHY has been added. Now the binding
information for the PHY and controller should be done in platform file
using usb_bind_phy API. And for getting a PHY, the device pointer of the
USB controller and an index should be passed. Based on the binding
information that is added in the platform file, usb_get_phy_dev will return the
appropriate PHY.
Already existing API's to add and get phy by type is not removed. These
API's are deprecated and will be removed once all the platforms start to
use the new API.

Signed-off-by: Kishon Vijay Abraham I 
Signed-off-by: Felipe Balbi

usb: otg: add an api to bind the usb controller and phy

2013-01-25T08:20:09+00:00

In order to support platforms which has multiple PHY's (of same type) and
which has multiple USB controllers, a new design is adopted wherin the binding
information (between the PHY and the USB controller) should be passed to the
PHY library from platform specific file (board file).
So added a new API to pass the binding information.

Signed-off-by: Kishon Vijay Abraham I 
Signed-off-by: Felipe Balbi

usb: phy: change phy notify connect/disconnect API

2012-11-16T01:44:51+00:00

The old parameter "port" is useless for phy notify, as one usb
phy is only for one usb port. New parameter "speed" stands for
the device's speed which is on the port, this "speed" parameter
is needed at some platforms which will do some phy operations
according to device's speed.

Signed-off-by: Peter Chen 
Tested-by: Mike Thompson 
Acked-by: Alan Stern 
Signed-off-by: Greg Kroah-Hartman