public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap dts changes for v4.10, part 2
Date: Sat, 26 Nov 2016 10:42:57 -0800	[thread overview]
Message-ID: <pull-1480185760-723915> (raw)

The following changes since commit 7e2f8c0ae670327cbe0348ad2f3df7d9a55a8e5d:

  ARM: dts: Add minimal support for motorola droid 4 xt894 (2016-11-15 10:28:49 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.10/dt-late-signed

for you to fetch changes up to 5817430ba7250cfc5a9c4a397935b07da16c9762:

  ARM: dts: AM571x-IDK Initial Support (2016-11-23 08:40:05 -0800)

----------------------------------------------------------------
Second set of device tree changes for omaps for v4.10 merge window:

- Fix up new instances of gpio-key,wakeup to use wakeup-source

- Add beaglebone LCDC blue-and-red-wiring property to make use
  of the new driver features

- Add bindings for IIO support for am335x and am437x

- Add palmas PMIC overide powerhold property for am57xx

- Update am335x-baltos to use phy-handle property

- Add initial support for am571x-idk

----------------------------------------------------------------
Andrew F. Davis (7):
      ARM: dts: am335x-icev2: Add Industrial input support
      ARM: dts: am335x-icev2: Disable Industrial I/O LEDs and fix naming
      ARM: dts: am335x-icev2: Add ADC support
      ARM: dts: am437x-idk: Add Industrial input support
      ARM: dts: am437x-idk: Add Industrial output support
      ARM: dts: am57xx-idk: Add Industrial input support
      ARM: dts: am57xx-idk: Add Industrial output support

Jyri Sarha (1):
      ARM: dts: am335x-boneblack: Add blue-and-red-wiring -property to LCDC node

Keerthy (2):
      ARM: dts: am57xx-beagle-x15-common: Add overide powerhold property
      ARM: dts: am57xx-idk-common: Add overide powerhold property

Schuyler Patton (1):
      ARM: dts: AM571x-IDK Initial Support

Sudeep Holla (1):
      ARM: dts: omap5: replace gpio-key,wakeup with wakeup-source property

Yegor Yefremov (1):
      ARM: dts: am335x-baltos: use phy-phandle declarations

 .../devicetree/bindings/arm/omap/omap.txt          |   3 +
 arch/arm/boot/dts/Makefile                         |   1 +
 arch/arm/boot/dts/am335x-baltos-ir2110.dts         |  10 +-
 arch/arm/boot/dts/am335x-baltos-ir3220.dts         |   2 +-
 arch/arm/boot/dts/am335x-baltos-ir5221.dts         |   2 +-
 arch/arm/boot/dts/am335x-baltos.dtsi               |   5 +-
 arch/arm/boot/dts/am335x-boneblack.dts             |  11 +++
 arch/arm/boot/dts/am335x-icev2.dts                 |  47 ++++++++--
 arch/arm/boot/dts/am437x-idk-evm.dts               | 101 +++++++++++++++++++++
 arch/arm/boot/dts/am571x-idk.dts                   |  81 +++++++++++++++++
 arch/arm/boot/dts/am572x-idk.dts                   |   4 +
 arch/arm/boot/dts/am57xx-beagle-x15-common.dtsi    |   1 +
 arch/arm/boot/dts/am57xx-idk-common.dtsi           |  75 +++++++++++++++
 arch/arm/boot/dts/omap5-uevm.dts                   |   2 +-
 14 files changed, 329 insertions(+), 16 deletions(-)
 create mode 100644 arch/arm/boot/dts/am571x-idk.dts

                 reply	other threads:[~2016-11-26 18:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=pull-1480185760-723915 \
    --to=tony@atomide.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