From: David Daney <ddaney@caviumnetworks.com>
To: mkl0301@gmail.com
Cc: cbouatmailru@gmail.com, avorontsov@mvista.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
dbrownell@users.sourceforge.net, linux-usb@vger.kernel.org
Subject: Re: [PATCH v3 1/1] USB: cns3xxx: Add EHCI and OHCI bus glue for cns3xxx SOCs
Date: Mon, 29 Nov 2010 11:23:32 -0800 [thread overview]
Message-ID: <4CF3FDB4.4050108@caviumnetworks.com> (raw)
In-Reply-To: <1290700680-20066-1-git-send-email-mkl0301@gmail.com>
On 11/25/2010 07:58 AM, mkl0301@gmail.com wrote:
> From: Mac Lin<mkl0301@gmail.com>
>
> The CNS3XXX SOC has include USB EHCI and OHCI compatible controllers. This
> patch adds the necessary glue logic to allow ehci-hcd and ohci-hcd drivers to
> work on CNS3XXX
>
> The EHCI and OHCI controllers share a common clock control and reset bit,
> therefore additional check for the timming of enabling and disabling is
> required. The USB bit of PLL Power Down Control is also shared by OTG, 24MHz
> UART clock, Crypto clock, PCIe reference clock, and Clock Scale Generator.
> Therefore we only ensure it is enabled, while not disabling it.
>
> Signed-off-by: Mac Lin<mkl0301@gmail.com>
> ---
> drivers/usb/Kconfig | 2 +
> drivers/usb/host/Kconfig | 15 ++++
> drivers/usb/host/ehci-cns3xxx.c | 171 +++++++++++++++++++++++++++++++++++++++
> drivers/usb/host/ehci-hcd.c | 5 +
> drivers/usb/host/ohci-cns3xxx.c | 165 +++++++++++++++++++++++++++++++++++++
> drivers/usb/host/ohci-hcd.c | 5 +
> 6 files changed, 363 insertions(+), 0 deletions(-)
> create mode 100644 drivers/usb/host/ehci-cns3xxx.c
> create mode 100644 drivers/usb/host/ohci-cns3xxx.c
>
> diff --git a/drivers/usb/Kconfig b/drivers/usb/Kconfig
> index 67eb377..5a7c8f1 100644
> --- a/drivers/usb/Kconfig
> +++ b/drivers/usb/Kconfig
> @@ -41,6 +41,7 @@ config USB_ARCH_HAS_OHCI
> default y if MFD_TC6393XB
> default y if ARCH_W90X900
> default y if ARCH_DAVINCI_DA8XX
> + default y if ARCH_CNS3XXX
> # PPC:
> default y if STB03xxx
> default y if PPC_MPC52xx
> @@ -66,6 +67,7 @@ config USB_ARCH_HAS_EHCI
> default y if ARCH_AT91SAM9G45
> default y if ARCH_MXC
> default y if ARCH_OMAP3
> + default y if ARCH_CNS3XXX
> default PCI
>
Can these be moved to the archecture Kconfig as:
select USB_ARCH_HAS_OHCI
select USB_ARCH_HAS_EHCI
Well to answer my own question, yes they can.
Should they? I think so.
David Daney
prev parent reply other threads:[~2010-11-29 19:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 15:58 [PATCH v3 1/1] USB: cns3xxx: Add EHCI and OHCI bus glue for cns3xxx SOCs mkl0301 at gmail.com
2010-11-25 15:58 ` mkl0301
2010-11-25 16:21 ` Anton Vorontsov
2010-11-25 16:21 ` Anton Vorontsov
2010-11-25 17:15 ` Greg KH
2010-11-25 17:15 ` Greg KH
2010-11-25 20:22 ` Alan Stern
2010-11-25 20:22 ` Alan Stern
2010-11-26 15:11 ` Anton Vorontsov
2010-11-26 15:11 ` Anton Vorontsov
2010-11-26 17:03 ` Greg KH
2010-11-26 17:03 ` Greg KH
2010-11-26 18:23 ` Anton Vorontsov
2010-11-26 18:23 ` Anton Vorontsov
2010-11-27 15:02 ` Lin Mac
2010-11-27 15:02 ` Lin Mac
2010-11-29 3:58 ` Lin Mac
2010-11-29 3:58 ` Lin Mac
2010-11-29 15:32 ` Anton Vorontsov
2010-11-29 15:32 ` Anton Vorontsov
2010-11-29 19:23 ` David Daney [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CF3FDB4.4050108@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=avorontsov@mvista.com \
--cc=cbouatmailru@gmail.com \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mkl0301@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.