Re: [RFC/PATCH 3/4] disociate chipidea PHY low power suspend control from hostpc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, May 14, 2012 at 05:17:46PM +0200, Matthieu CASTET wrote:
> Signed-off-by: Matthieu CASTET <matthieu.castet@xxxxxxxxxx>
> ---
>  drivers/usb/host/ehci-hcd.c |    4 +-
>  drivers/usb/host/ehci-hub.c |  104 ++++++++++++++++++++-----------------------
>  drivers/usb/host/ehci.h     |    6 ++-
>  3 files changed, 57 insertions(+), 57 deletions(-)
Hi Matthieu,

USB transceiver (PHY) may be different for kinds of SoC vendors.
Some uses chipidea internal UTMI PHY, in this case, only PHCD is 
needed to controller PHY's suspend/resume. Some does not use
chipidea PHY (ULPI or vendor's UTMI PHY), in this case, PHY's operation
is not only set/clear phcd, it may includes some others, like close 
PHY's analog part, PHY's clock, etc.

So, I prefer to put PHY's operation at PHY's driver, it is platform
related.

-- 

Best Regards,
Peter Chen

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux