public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: arm@kernel.org
Cc: linux-tegra@vger.kernel.org,
	Thierry Reding <thierry.reding@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	Jon Hunter <jonathanh@nvidia.com>
Subject: [GIT PULL 1/6] dt-bindings: Changes for v4.21-rc1
Date: Fri,  7 Dec 2018 15:17:34 +0100	[thread overview]
Message-ID: <20181207141739.9085-1-thierry.reding@gmail.com> (raw)

Hi ARM SoC maintainers,

The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:

  Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.21-dt-bindings

for you to fetch changes up to b4c7bf003cb57220af64b59e887581e74f0ce527:

  dt-bindings: tegra186-pmc: Add interrupt controller properties (2018-11-28 16:42:58 +0100)

Thanks,
Thierry

----------------------------------------------------------------
dt-bindings: Changes for v4.21-rc1

This contains a few cleanups of and additions to existing device tree
bindings, such as XUSB, EMC, PMC and thermal.

----------------------------------------------------------------
Dmitry Osipenko (3):
      dt: bindings: tegra20-emc: Document interrupt property
      dt: bindings: tegra20-emc: Document clock property
      dt: bindings: Move tegra20-emc binding to memory-controllers directory

Jon Hunter (1):
      dt-bindings: usb: xhci-tegra: Add power-domain details

Thierry Reding (2):
      dt-bindings: thermal: tegra-bpmp: Add Tegra194 support
      dt-bindings: tegra186-pmc: Add interrupt controller properties

 .../devicetree/bindings/arm/tegra/nvidia,tegra186-pmc.txt |  3 +++
 .../tegra => memory-controllers}/nvidia,tegra20-emc.txt   |  4 ++++
 .../bindings/thermal/nvidia,tegra186-bpmp-thermal.txt     |  3 ++-
 .../devicetree/bindings/usb/nvidia,tegra124-xusb.txt      |  8 ++++++++
 include/dt-bindings/thermal/tegra194-bpmp-thermal.h       | 15 +++++++++++++++
 5 files changed, 32 insertions(+), 1 deletion(-)
 rename Documentation/devicetree/bindings/{arm/tegra => memory-controllers}/nvidia,tegra20-emc.txt (95%)
 create mode 100644 include/dt-bindings/thermal/tegra194-bpmp-thermal.h

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2018-12-07 14:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-07 14:17 Thierry Reding [this message]
2018-12-07 14:17 ` [GIT PULL 2/6] soc/tegra: Changes for v4.21-rc1 Thierry Reding
2018-12-12 21:28   ` Olof Johansson
2018-12-07 14:17 ` [GIT PULL 3/6] firmware: tegra: " Thierry Reding
2018-12-12 21:31   ` Olof Johansson
2018-12-07 14:17 ` [GIT PULL 4/6] memory: " Thierry Reding
2018-12-12 21:45   ` Olof Johansson
2018-12-07 14:17 ` [GIT PULL 5/6] ARM: tegra: Device tree changes " Thierry Reding
2018-12-11 16:07   ` Olof Johansson
2018-12-07 14:17 ` [GIT PULL 6/6] arm64: tegra: Device tree change " Thierry Reding
2018-12-11 16:11   ` Olof Johansson
2018-12-11 16:06 ` [GIT PULL 1/6] dt-bindings: Changes " 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=20181207141739.9085-1-thierry.reding@gmail.com \
    --to=thierry.reding@gmail.com \
    --cc=arm@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.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