From: Mark Jackson <mpfj-list@newflow.co.uk>
To: Michael Grzeschik <mgr@pengutronix.de>
Cc: linux-usb@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
Felipe Balbi <balbi@ti.com>,
bigeasy@linutronix.de, Greg KH <gregkh@linuxfoundation.org>,
jkosina@suse.cz, anatol.pomozov@gmail.com,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] Allow MUSB DSPS to use "force host" mode
Date: Fri, 22 Nov 2013 16:45:12 +0000 [thread overview]
Message-ID: <528F8A18.5080807@newflow.co.uk> (raw)
In-Reply-To: <20131122163835.GF24508@pengutronix.de>
On 22/11/13 16:38, Michael Grzeschik wrote:
> Hallo,
>
> On Fri, Nov 22, 2013 at 03:55:59PM +0000, Mark Jackson wrote:
>> The IDDIG input pin is normally used to determine the USB mode
>> (i.e. HOST or DEVICE).
>>
>> On some systems (e.g. AM335x) leaving this pin floating allows
>> the USB mode to be set via software.
>>
>> This patch adds support for this via the device tree.
>>
>> Signed-off-by: Mark Jackson <mpfj@newflow.co.uk>
>> ---
>> .../devicetree/bindings/usb/am33xx-usb.txt | 2 ++
>> drivers/usb/musb/musb_dsps.c | 14 ++++++++++++++
>> include/linux/usb/musb.h | 1 +
>> 3 files changed, 17 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/usb/am33xx-usb.txt b/Documentation/devicetree/bindings/usb/am33xx-usb.txt
>> index 20c2ff2..560b7ff 100644
>> --- a/Documentation/devicetree/bindings/usb/am33xx-usb.txt
>> +++ b/Documentation/devicetree/bindings/usb/am33xx-usb.txt
>> @@ -47,6 +47,8 @@ USB
>> - dmas: specifies the dma channels
>> - dma-names: specifies the names of the channels. Use "rxN" for receive
>> and "txN" for transmit endpoints. N specifies the endpoint number.
>> +- ti,force-host: specifies that the IDDIG input be ignored and the device be
>> + put into host mode regardless.
>
> You should always CC devicetree-discuss if adding new bindings. Why
> another binding anyway? We have the common binding dr_mode already.
> Please use this and of_usb_get_dr_mode from drivers/usb/usb-common.c
> instead.
Sure ... that's a nicer solution.
I'll do that for v2
Mark J.
next prev parent reply other threads:[~2013-11-22 16:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 15:55 [PATCH] Allow MUSB DSPS to use "force host" mode Mark Jackson
2013-11-22 16:33 ` Sebastian Andrzej Siewior
2013-11-22 16:49 ` Mark Jackson
2013-11-22 17:01 ` Sebastian Andrzej Siewior
2013-11-22 17:07 ` Mark Jackson
2013-11-22 17:22 ` Sebastian Andrzej Siewior
[not found] ` <528F7E8F.5050807-2FZW7xY0fHgqdlJmJB21zg@public.gmane.org>
2013-11-22 16:38 ` Michael Grzeschik
2013-11-22 16:38 ` Michael Grzeschik
2013-11-22 16:45 ` Mark Jackson [this message]
2013-11-25 21:24 ` Felipe Balbi
2013-11-25 21:24 ` Felipe Balbi
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=528F8A18.5080807@newflow.co.uk \
--to=mpfj-list@newflow.co.uk \
--cc=anatol.pomozov@gmail.com \
--cc=balbi@ti.com \
--cc=bigeasy@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mgr@pengutronix.de \
/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.