linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/5] ARM: tegra: DT-related fixes needed by the USB tree
Date: Fri, 14 Jun 2013 10:37:14 -0600	[thread overview]
Message-ID: <1371227838-18764-2-git-send-email-swarren@wwwdotorg.org> (raw)
In-Reply-To: <1371227838-18764-1-git-send-email-swarren@wwwdotorg.org>

The Tegra USB bindings were in bad shape. The patches in this branch
fix the binding definitions, and make all the necessary additions to
the DT files. Stale nodes/properties will be removed early in 3.12
once the USB driver has been updated for the new binding.

These changes are needed in both the USB tree, to allow the driver to
be updated to handle them, and the Tegra tree, so that various tree-
wide DT changes (e.g. conversion of IRQ/GPIO/clock constants to defines)
can be applied on top of them.

This branch is included in later pull request tegra-for-3.11-dt.

----------------------------------------------------------------

The following changes since commit f722406faae2d073cc1d01063d1123c35425939e:

  Linux 3.10-rc1

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git tegra-for-3.11-deps-for-usb

for you to fetch changes up to 4c94c8b5b3cc38b0d0b1ec79642f5710e19a3e01:

  ARM: tegra: update device trees for USB binding rework

----------------------------------------------------------------

Venu Byravarasu (3):
      ARM: tegra: finalize USB EHCI and PHY bindings
      ARM: tegra: modify ULPI reset GPIO properties
      ARM: tegra: update device trees for USB binding rework

 .../bindings/usb/nvidia,tegra20-ehci.txt        | 27 ++---------
 .../bindings/usb/nvidia,tegra20-usb-phy.txt     | 41 ++++++++++++++--
 arch/arm/boot/dts/tegra20-colibri-512.dtsi      |  6 ++-
 arch/arm/boot/dts/tegra20-harmony.dts           | 15 ++++--
 arch/arm/boot/dts/tegra20-iris-512.dts          |  9 +++-
 arch/arm/boot/dts/tegra20-paz00.dts             | 15 ++++--
 arch/arm/boot/dts/tegra20-seaboard.dts          | 26 +++++++++--
 arch/arm/boot/dts/tegra20-tamonten.dtsi         |  4 ++
 arch/arm/boot/dts/tegra20-trimslice.dts         | 25 ++++++++--
 arch/arm/boot/dts/tegra20-ventana.dts           | 15 ++++--
 arch/arm/boot/dts/tegra20-whistler.dts          | 28 +++++++++++
 arch/arm/boot/dts/tegra20.dtsi                  | 49 +++++++++++++++-----
 12 files changed, 206 insertions(+), 54 deletions(-)

  reply	other threads:[~2013-06-14 16:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-14 16:37 [GIT PULL 0/5] ARM: tegra: changes for 3.11 Stephen Warren
2013-06-14 16:37 ` Stephen Warren [this message]
2013-06-14 16:37 ` [GIT PULL 2/5] ARM: tegra: create headers for clock bindings Stephen Warren
2013-06-14 16:37 ` [GIT PULL 3/5] ARM: tegra: device tree updates Stephen Warren
2013-06-15  1:11   ` Olof Johansson
2013-06-14 16:37 ` [GIT PULL 4/5] ARM: tegra: core SoC support enhancements Stephen Warren
2013-06-15  1:12   ` Olof Johansson
2013-06-14 16:37 ` [GIT PULL 5/5] ARM: tegra: defconfig updates Stephen Warren
2013-06-15  1:14   ` Olof Johansson

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=1371227838-18764-2-git-send-email-swarren@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).