From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 4/4 v2] ARM: shmobile: bockw: add USB Function support
Date: Wed, 10 Jul 2013 12:06:45 +0000 [thread overview]
Message-ID: <51DD4E55.4030808@cogentembedded.com> (raw)
In-Reply-To: <87r4f7uoxx.wl%kuninori.morimoto.gx@renesas.com>
Hello.
On 10-07-2013 6:30, Kuninori Morimoto wrote:
> Bock-W USB1 (CN29) can be USB Host/Func by SW98/SW99 settings.
> USB Func will be enabled if CONFIG_USB_RENESAS_USBHS_UDC[_MODULE]
> was selected by this patch
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
[...]
> diff --git a/arch/arm/mach-shmobile/board-bockw.c b/arch/arm/mach-shmobile/board-bockw.c
> index a57be8a..afc3fcf 100644
> --- a/arch/arm/mach-shmobile/board-bockw.c
> +++ b/arch/arm/mach-shmobile/board-bockw.c
[...]
> @@ -162,10 +199,13 @@ static const struct pinctrl_map bockw_pinctrl_map[] = {
> /* SDHI0 */
> PIN_MAP_MUX_GROUP_DEFAULT("sh_mobile_sdhi.0", "pfc-r8a7778",
> "sdhi0", "sdhi0"),
> + /* USB */
> PIN_MAP_MUX_GROUP_DEFAULT("ehci-platform", "pfc-r8a7778",
> "usb0", "usb0"),
> PIN_MAP_MUX_GROUP_DEFAULT("ehci-platform", "pfc-r8a7778",
> "usb1", "usb1"),
> + PIN_MAP_MUX_GROUP_DEFAULT("renesas_usbhs", "pfc-r8a7778",
> + "usb1", "usb1"),
Won't it cause conflict with the previous group when both EHCI and
USB function drivers are enabled?
WBR, Sergei
next prev parent reply other threads:[~2013-07-10 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 2:30 [PATCH 4/4 v2] ARM: shmobile: bockw: add USB Function support Kuninori Morimoto
2013-07-10 12:06 ` Sergei Shtylyov [this message]
2013-10-02 8:34 ` [PATCH 4/4 v2] ARM: shmobile: bockw: add SMSC support on DTS Kuninori Morimoto
2013-10-03 4:14 ` Simon Horman
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=51DD4E55.4030808@cogentembedded.com \
--to=sergei.shtylyov@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).