linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valentine <valentine.barshak@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/3] arm: shmobile: lager: Add USBHS support
Date: Fri, 17 Jan 2014 18:31:16 +0000	[thread overview]
Message-ID: <52D976F4.5080600@cogentembedded.com> (raw)
In-Reply-To: <1387548804-20829-2-git-send-email-valentine.barshak@cogentembedded.com>

On 01/15/2014 04:39 PM, Magnus Damm wrote:
> On Fri, Dec 20, 2013 at 11:13 PM, Valentine Barshak
> <valentine.barshak@cogentembedded.com> wrote:
>> This adds USBHS PHY and registers USBHS device if the driver is enabled.
>>
>> Signed-off-by: Valentine Barshak <valentine.barshak@cogentembedded.com>
>> ---
>>   arch/arm/mach-shmobile/board-lager.c | 117 +++++++++++++++++++++++++++++++++++
>>   1 file changed, 117 insertions(+)
>
> Hi Valentine,

Magnus, Simon,

>
> Thanks for this USB function patch. I'd like to switch focus to USB
> function soon.
>
> By the way, I'm happy to see that SATA platform device support is
> picked up by Simon. I intend to give your SATA DTS patches a go later
> this week, they should be ready to queue up rather soon I believe.
>
> Would it be possible for you to update your USB function platform
> device patches for Lager and Koelsch? I'd like to merge those after
> SATA, and the platform device files shouldn't change now so USB can go
> next now unless I'm mistaken. Please send a complete per-board series
> for USB function so patch pick up and testing gets easy - same style
> as SATA would be great.

Just respinned the USB series for Lager and Koelsch.
I did not include defconfig changes yet.
I think we need to enable kernel modules in the defconfig first,
so that multiple USB gadgets can be selected as modules.
Besides, I think that the USBHS device should be disabled in the defconfigs
since the boards have USB channel 0 configured as PCI USB host by default.

Please, let me know your thoughts regarding defconfig changes and I'll prepare the patches then.

Currently, the following options should be enabled if you want to test USB:
* USB device and USB host
CONFIG_USB=y
CONFIG_USB_RCAR_GEN2_PHY=y
* USB device
CONFIG_USB_RENESAS_USBHS=y
CONFIG_USB_GADGET=y
CONFIG_USB_RENESAS_USBHS_UDC=y
* USB Host
CONFIG_PCI=y
CONFIG_PCI_RCAR_GEN2=y
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_OHCI_HCD=y

>
> I suppose we need to control MSTP bits via Runtime PM for USBHS, so
> some patch for clock control may be needed as well.

Works for me without any additional clock control changes.

>
> Thanks,
>
> / magnus
>

Thanks,
Val.

  parent reply	other threads:[~2014-01-17 18:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20 14:13 [PATCH 1/3] arm: shmobile: lager: Add USBHS support Valentine Barshak
2014-01-15 12:39 ` Magnus Damm
2014-01-17 18:31 ` Valentine [this message]
2014-01-24  4:40 ` Magnus Damm
2014-01-24 23:05 ` Valentine
2014-01-27 10:26 ` Magnus Damm
2014-01-29  6:11 ` Simon Horman
2014-01-29  9:21 ` Valentine
2014-02-04 12:44 ` Simon Horman
2014-02-05  7:13 ` Magnus Damm

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=52D976F4.5080600@cogentembedded.com \
    --to=valentine.barshak@cogentembedded.com \
    --cc=linux-sh@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).