[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <VI1PR04MB145568B8A2FFB8BE45E208948B730@VI1PR04MB1455.eurprd04.prod.outlook.com>
Date: Sun, 22 Jan 2017 01:34:40 +0000
From: Peter Chen <peter.chen@....com>
To: Stephen Boyd <stephen.boyd@...aro.org>,
Kishon Vijay Abraham I <kishon@...com>
CC: "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
Andy Gross <andy.gross@...aro.org>,
"Bjorn Andersson" <bjorn.andersson@...aro.org>,
Neil Armstrong <narmstrong@...libre.com>,
Arnd Bergmann <arnd@...db.de>, Felipe Balbi <balbi@...nel.org>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>
Subject: RE: [PATCH v7 3/5] phy: Add set_vbus callback
> * @set_mode: set the mode of the phy
>+ * @set_vbus: enable/disable vbus in the phy (USB)
> * @reset: resetting the phy
> * @owner: the module owner containing the ops
> */
>@@ -45,6 +46,7 @@ struct phy_ops {
> int (*power_on)(struct phy *phy);
> int (*power_off)(struct phy *phy);
> int (*set_mode)(struct phy *phy, enum phy_mode mode);
>+ int (*set_vbus)(struct phy *phy, int on);
How about using the name notify_vbus? The main purpose of this API is notify
PHY vbus status.
Peter
Powered by blists - more mailing lists