On Tue, Jan 15, 2013 at 02:08:34PM +0800, Peter Chen wrote:
For mxs-phy user i.mx6q, the PHY's clock is controlled by
hardware automatically, the software only needs to enable it
at probe, disable it at remove. During the runtime,
we don't need to control it. So for the usbphy clk policy:
-
On Wed, Jan 16, 2013 at 09:48:57AM +0800, Shawn Guo wrote:
On Wed, Jan 16, 2013 at 09:18:46AM +0800, Peter Chen wrote:
On Tue, Jan 15, 2013 at 07:33:16PM +0800, Shawn Guo wrote:
On Tue, Jan 15, 2013 at 02:08:34PM +0800, Peter Chen wrote:
For mxs-phy user i.mx6q, the PHY's clock is
For mxs-phy user i.mx6q, the PHY's clock is controlled by
hardware automatically, the software only needs to enable it
at probe, disable it at remove. During the runtime,
we don't need to control it. So for the usbphy clk policy:
- Keep refcount for usbphy as clk framework needs to know if
it is