From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: balbi@ti.com
Cc: horms@verge.net.au, linux-sh@vger.kernel.org, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
devicetree@vger.kernel.org, magnus.damm@gmail.com,
linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org,
linux-usb@vger.kernel.org, yoshihiro.shimoda.uh@renesas.com
Subject: Re: [PATCH v3 2/3] ARM: shmobile: koelsch: enable HS-USB
Date: Wed, 08 Oct 2014 22:11:59 +0400 [thread overview]
Message-ID: <54357E6F.1080702@cogentembedded.com> (raw)
In-Reply-To: <20141008180852.GK22688@saruman>
On 10/08/2014 10:08 PM, Felipe Balbi wrote:
>>>> From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
>>>> Enable HS-USB device for the Koelsch board, defining the GPIO that the driver
>>>> should check when probing (which is the ID output from MAX3355 OTG chip).
>>>> Note that there will be pinctrl-related error messages if both internal PCI
>>>> and HS-USB drivers are enabled but they should be just ignored.
>>>> Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
>>>> [Sergei: added pin function/group and prop, moved device node, fixed summary,
>>>> added changelog]
>>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>>>> ---
>>>> Changes in version 3:
>>>> - added pinctrl-related properties;
>>> did you miss pinctrl here ?
>> No, AFAICS. Or what do you mean?
> usb0_pins doesn't appear to be defined anywhere.
They are defined in the same file, just not in this patch. If you're
looking at some of the USB trees or Linus' tree, the corresponding patch just
hasn't hit them yet, it's in renesas.git ATM.
WBR, Sergei
next prev parent reply other threads:[~2014-10-08 18:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 17:59 [PATCH v3 1/3] Add HS-USB device tree support for R8A7791/Koelsch/Henninger board Sergei Shtylyov
2014-10-08 18:00 ` [PATCH v3 1/3] ARM: shmobile: r8a7791: add HS-USB device node Sergei Shtylyov
2014-10-08 18:02 ` [PATCH v3 2/3] ARM: shmobile: koelsch: enable HS-USB Sergei Shtylyov
[not found] ` <8674731.7YYzQeH0h1-gHKXc3Y1Z8zGSmamagVegGFoWSdPRAKMAL8bYrjMMd8@public.gmane.org>
2014-10-08 18:05 ` Felipe Balbi
2014-10-08 18:07 ` Sergei Shtylyov
[not found] ` <54357D76.4050104-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2014-10-08 18:08 ` Felipe Balbi
2014-10-08 18:11 ` Sergei Shtylyov [this message]
2014-10-08 18:22 ` Felipe Balbi
2014-10-09 1:07 ` Yoshihiro Shimoda
2014-10-09 12:51 ` Sergei Shtylyov
[not found] ` <543684B6.6060708-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2014-10-10 0:17 ` Yoshihiro Shimoda
2014-10-08 18:04 ` [PATCH v3 3/3] ARM: shmobile: henninger: " Sergei Shtylyov
[not found] ` <1511869.4ca9KHmSFr-gHKXc3Y1Z8zGSmamagVegGFoWSdPRAKMAL8bYrjMMd8@public.gmane.org>
2014-10-08 18:05 ` [PATCH v3 1/3] Add HS-USB device tree support for R8A7791/Koelsch/Henninger board Sergei Shtylyov
2014-10-24 5:23 ` Yoshihiro Shimoda
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=54357E6F.1080702@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=horms@verge.net.au \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.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 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).