From: Marek Vasut <marex@denx.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: linux-mips@linux-mips.org, Wills Wang <wills.wang@live.com>,
Daniel Schwierzeck <daniel.schwierzeck@gmail.com>,
Alban Bedel <albeu@free.fr>,
Alan Stern <stern@rowland.harvard.edu>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC v5 07/15] usb: ehci: add vbus-gpio parameter
Date: Tue, 9 Feb 2016 12:14:52 +0100 [thread overview]
Message-ID: <201602091214.52848.marex@denx.de> (raw)
In-Reply-To: <1455005641-7079-8-git-send-email-antonynpavlov@gmail.com>
On Tuesday, February 09, 2016 at 09:13:53 AM, Antony Pavlov wrote:
> This patch retrieves and configures the vbus control gpio via
> the device tree.
>
> This patch is based on a ehci-s5p.c commit fd81d59c90d38661
> ("USB: ehci-s5p: Add vbus setup function to the s5p ehci glue layer").
>
> Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
> Cc: Alan Stern <stern@rowland.harvard.edu>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: linux-usb@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> ---
> drivers/usb/host/ehci-platform.c | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
I think this patch will not be needed if you switch the ar9331 to chipidea hdrc
driver. There is CI HDRC in the ar9331.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-02-09 11:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1455005641-7079-1-git-send-email-antonynpavlov@gmail.com>
2016-02-09 8:13 ` [RFC v5 07/15] usb: ehci: add vbus-gpio parameter Antony Pavlov
2016-02-09 11:14 ` Marek Vasut [this message]
2016-02-09 22:15 ` Alban
2016-02-10 0:00 ` Antony Pavlov
2016-02-18 16:12 ` Alan Stern
2016-02-18 16:39 ` Marek Vasut
2016-02-18 18:06 ` Antony Pavlov
2016-02-18 18:31 ` Sergei Shtylyov
2016-02-18 22:11 ` Antony Pavlov
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=201602091214.52848.marex@denx.de \
--to=marex@denx.de \
--cc=albeu@free.fr \
--cc=antonynpavlov@gmail.com \
--cc=daniel.schwierzeck@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=wills.wang@live.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).