forked from Minki/linux
bd27fa44e1
Modelling the RESET line as a regulator supply wasn't a good idea as it kind of abuses the regulator framework and also makes adaptation code more complex. Instead, manage the RESET gpio line directly in the driver. Update the device tree binding information. This also makes us easy to migrate to a dedicated GPIO RESET controller whenever it becomes available. Signed-off-by: Roger Quadros <rogerq@ti.com> Signed-off-by: Felipe Balbi <balbi@ti.com>
20 lines
440 B
C
20 lines
440 B
C
#ifndef _PHY_GENERIC_H_
|
|
#define _PHY_GENERIC_H_
|
|
|
|
struct usb_phy_gen_xceiv {
|
|
struct usb_phy phy;
|
|
struct device *dev;
|
|
struct clk *clk;
|
|
struct regulator *vcc;
|
|
int gpio_reset;
|
|
bool reset_active_low;
|
|
};
|
|
|
|
int usb_gen_phy_init(struct usb_phy *phy);
|
|
void usb_gen_phy_shutdown(struct usb_phy *phy);
|
|
|
|
int usb_phy_gen_create_phy(struct device *dev, struct usb_phy_gen_xceiv *nop,
|
|
enum usb_phy_type type, u32 clk_rate, bool needs_vcc);
|
|
|
|
#endif
|