public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: marcel@ziswiler.com (Marcel Ziswiler)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] dt/bindings & ARM: dts: tegra: updates
Date: Sat, 10 Feb 2018 02:33:21 +0100	[thread overview]
Message-ID: <20180210013326.27771-1-marcel@ziswiler.com> (raw)


This series fixes the Tegra GMI controller DT/bindings example, a few
IRQ type definitions, removes some invalid uses of rsvd1 pin muxes on
Beaver and removes a duplicate pcie-1 node on Venice2.


Marcel Ziswiler (4):
  dt/bindings: fix binding examples for tegra gmi controller
  ARM: dts: tegra: use proper irq type definitions
  ARM: dts: tegra: beaver: remove invalid uses of rsvd1
  ARM: dts: tegra: venice2: remove duplicate pcie-1 node

 .../devicetree/bindings/bus/nvidia,tegra20-gmi.txt |  6 ++--
 arch/arm/boot/dts/tegra114-dalmore.dts             |  2 +-
 arch/arm/boot/dts/tegra124-jetson-tk1.dts          |  2 +-
 arch/arm/boot/dts/tegra124-venice2.dts             |  9 ++----
 arch/arm/boot/dts/tegra30-apalis.dtsi              |  4 +--
 arch/arm/boot/dts/tegra30-beaver.dts               | 32 +++++++++++-----------
 arch/arm/boot/dts/tegra30-colibri-eval-v3.dts      |  2 +-
 7 files changed, 25 insertions(+), 32 deletions(-)

-- 
2.14.3

             reply	other threads:[~2018-02-10  1:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-10  1:33 Marcel Ziswiler [this message]
2018-02-10  1:33 ` [PATCH 2/4] ARM: dts: tegra: use proper irq type definitions Marcel Ziswiler
2018-02-10  1:33 ` [PATCH 3/4] ARM: dts: tegra: beaver: remove invalid uses of rsvd1 Marcel Ziswiler
2018-02-10  1:33 ` [PATCH 4/4] ARM: dts: tegra: venice2: remove duplicate pcie-1 node Marcel Ziswiler
2018-03-08 15:07 ` [PATCH 0/4] dt/bindings & ARM: dts: tegra: updates Thierry Reding

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=20180210013326.27771-1-marcel@ziswiler.com \
    --to=marcel@ziswiler.com \
    --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