linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: arm@kernel.org, soc@kernel.org
Cc: Thierry Reding <thierry.reding@gmail.com>,
	Jon Hunter <jonathanh@nvidia.com>,
	linux-tegra@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/7] dt-bindings: Changes for v5.16-rc1
Date: Fri,  8 Oct 2021 22:11:26 +0200	[thread overview]
Message-ID: <20211008201132.1678814-2-thierry.reding@gmail.com> (raw)
In-Reply-To: <20211008201132.1678814-1-thierry.reding@gmail.com>

Hi ARM SoC maintainers,

The following changes since commit 6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f:

  Linux 5.15-rc1 (2021-09-12 16:28:37 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 354754f559507e0dba014aa830c70e73e7d52f98:

  dt-bindings: PCI: tegra194: Fix PCIe endpoint node names (2021-10-07 21:24:25 +0200)

Thanks,
Thierry

----------------------------------------------------------------
dt-bindings: Changes for v5.16-rc1

This contains the DT bindings for the NVDEC hardware video decoder found
on Tegra210 and later chips as well as a node name fix for the examples
in the Tegra194 PCIe controller (endpoint mode) DT bindings.

----------------------------------------------------------------
Mauro Carvalho Chehab (1):
      dt-bindings: PCI: tegra194: Fix PCIe endpoint node names

Mikko Perttunen (1):
      dt-bindings: Add YAML bindings for NVDEC

 .../bindings/gpu/host1x/nvidia,tegra210-nvdec.yaml | 106 +++++++++++++++++++++
 .../bindings/pci/nvidia,tegra194-pcie.txt          |   2 +-
 MAINTAINERS                                        |   1 +
 3 files changed, 108 insertions(+), 1 deletion(-)
 create mode 100644 Documentation/devicetree/bindings/gpu/host1x/nvidia,tegra210-nvdec.yaml

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

  reply	other threads:[~2021-10-08 20:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08 20:11 [GIT PULL 0/7] NVIDIA Tegra changes for v5.16-rc1 Thierry Reding
2021-10-08 20:11 ` Thierry Reding [this message]
2021-10-11 22:11   ` [GIT PULL 1/7] dt-bindings: Changes " Arnd Bergmann
2021-10-08 20:11 ` [GIT PULL 2/7] firmware: tegra: " Thierry Reding
2021-10-11 14:54   ` Arnd Bergmann
2021-10-08 20:11 ` [GIT PULL 3/7] soc/tegra: " Thierry Reding
2021-10-11 14:54   ` Arnd Bergmann
2021-10-08 20:11 ` [GIT PULL 4/7] cpuidle: tegra: " Thierry Reding
2021-10-11 14:54   ` Arnd Bergmann
2021-10-08 20:11 ` [GIT PULL 5/7] ARM: tegra: Device tree changes " Thierry Reding
2021-10-11 22:11   ` Arnd Bergmann
2021-10-08 20:11 ` [GIT PULL 6/7] arm64: " Thierry Reding
2021-10-11 22:11   ` Arnd Bergmann
2021-10-08 20:11 ` [GIT PULL 7/7] arm64: tegra: Default configuration " Thierry Reding
2021-10-12 12:50   ` Arnd Bergmann

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=20211008201132.1678814-2-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 \
    --cc=soc@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;
as well as URLs for NNTP newsgroup(s).