From: Stephen Warren <swarren@nvidia.com>
To: Simon Glass <sjg@chromium.org>, LKML <linux-kernel@vger.kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Devicetree Discuss <devicetree-discuss@lists.ozlabs.org>
Subject: RE: [PATCH 0/3] arm: tegra: dts: USB Updates for Tegra legacy mode / OTG
Date: Fri, 3 Feb 2012 11:59:29 -0800 [thread overview]
Message-ID: <74CDBE0F657A3D45AFBB94109FB122FF178E5D2FF5@HQMAIL01.nvidia.com> (raw)
In-Reply-To: <1328288172-8059-1-git-send-email-sjg@chromium.org>
Simon Glass wrote at riday, February 03, 2012 9:56 AM:
> This little series brings in some bindings that seem useful for U-Boot.
>
> I am working mostly in U-Boot, but since there is no shared .dts repo
> I was asked to commit these changes to the kernel. I do not propose to
> update the Linux USB drivers to match.
I think the series looks reasonable, so:
Acked-by: Stephen Warren <swarren@nvidia.com<>
(I note that the kernel's USB driver for USB1 doesn't attempt to clear
legacy mode; I wonder how we're getting away with that. Perhaps it's
only been tested with a bootloader that's already cleared legacy mode)
--
nvpublic
next prev parent reply other threads:[~2012-02-03 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 16:56 Simon Glass
2012-02-03 16:56 ` [PATCH 1/3] arm: tegra: dts: Support host/device selection and legacy mode Simon Glass
2012-02-03 16:56 ` [PATCH 2/3] arm: tegra: dts: Add legacy mode support to Tegra2x USB1 port Simon Glass
2012-02-03 16:56 ` [PATCH 3/3] arm: tegra: dts: Mark USB1 as an OTG port on Seaboard Simon Glass
2012-02-03 19:59 ` Stephen Warren [this message]
2012-03-07 3:16 ` [PATCH 0/3] arm: tegra: dts: USB Updates for Tegra legacy mode / OTG Simon Glass
2012-03-07 4:40 ` Olof Johansson
2012-03-07 5:06 ` Simon Glass
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=74CDBE0F657A3D45AFBB94109FB122FF178E5D2FF5@HQMAIL01.nvidia.com \
--to=swarren@nvidia.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=sjg@chromium.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
all inboxes | Powered by JetHome®