From: Jon Hunter <jonathanh@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Paul Kocialkowski <contact@paulk.fr>
Cc: <linux-kernel@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>,
Alexandre Courbot <gnurou@gmail.com>,
Stephen Warren <swarren@wwwdotorg.org>
Subject: Re: [PATCH] ARM: tegra: nyan: Mark all USB ports as host
Date: Mon, 7 Nov 2016 14:09:31 +0000 [thread overview]
Message-ID: <13e7ff98-8bc2-ccf7-94bb-4e1d3c61b20d@nvidia.com> (raw)
In-Reply-To: <20161107132854.GF12559@ulmo.ba.sec>
On 07/11/16 13:28, Thierry Reding wrote:
> * PGP Signed by an unknown key
>
> On Sun, Sep 18, 2016 at 12:28:52PM +0200, Paul Kocialkowski wrote:
>> Nyan boards only have host USB ports (2 external, 1 internal), there is
>> no OTG-enabled connector.
>>
>> Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
>> ---
>> arch/arm/boot/dts/tegra124-nyan.dtsi | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Where is this information coming from? I don't have one of the Nyans
> myself, but one of the Tegra132 devices I have, which I think was
> derived from one of the Nyans uses one of the external host ports as
> forced recovery port, for which it would need OTG.
>
> I suspect that the way to get U-Boot onto the Nyans is via tegrarcm?
> In that case I think one of the ports must be OTG.
It is true that the port on the back on the nyan-big can be used with
recovery mode. I was thinking that this is not a true OTG port as it is
just a 4-pin type A socket and does not have an ID pin. Thinking some
more about this the USB spec does include a "Host Negotiation Protocol
(HNP)" that allows a host and device to swap roles and so keeping it as
OTG seems valid afterall.
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2016-11-07 14:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-18 10:28 Paul Kocialkowski
2016-09-20 11:51 ` Jon Hunter
2016-11-07 13:28 ` Thierry Reding
2016-11-07 14:09 ` Jon Hunter [this message]
2016-11-08 8:54 ` Peter De Schrijver
2016-11-08 9:09 ` Paul Kocialkowski
2016-11-08 9:47 ` Jon Hunter
2016-11-08 11:07 ` Thierry Reding
2016-11-08 11:09 ` Jon Hunter
2016-11-08 13:02 ` Paul Kocialkowski
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=13e7ff98-8bc2-ccf7-94bb-4e1d3c61b20d@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=contact@paulk.fr \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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
Powered by JetHome