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/6] dt-bindings: Changes for v5.11-rc1 Date: Fri, 27 Nov 2020 15:43:24 +0100 [thread overview] Message-ID: <20201127144329.124891-1-thierry.reding@gmail.com> (raw) Hi ARM SoC maintainers, The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec: Linux 5.10-rc1 (2020-10-25 15:14:11 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-5.11-dt-bindings for you to fetch changes up to e36f9381420b28e1785d7900d4c1d9db6149cbcd: dt-bindings: bus: Convert ACONNECT doc to json-schema (2020-11-26 19:05:17 +0100) Thanks, Thierry ---------------------------------------------------------------- dt-bindings: Changes for v5.11-rc1 This contains a couple of conversions of bindings to json-schema, as well as symbolic names for the various memory clients on Tegra20, Tegra30 and Tegra124. There's also a couple of fixes for Tegra194 pinmux and ARM GIC bindings. Finally, a new vendor prefix is added for Ouya and the Ouya game console compatible string is defined. ---------------------------------------------------------------- Dmitry Osipenko (3): dt-bindings: memory: tegra20: Add memory client IDs dt-bindings: memory: tegra30: Add memory client IDs dt-bindings: memory: tegra124: Add memory client IDs Peter Geis (2): dt-bindings: Add vendor prefix for Ouya Inc. dt-bindings: ARM: tegra: Add Ouya game console Sameer Pujar (3): dt-bindings: dma: Convert ADMA doc to json-schema dt-bindings: interrupt-controller: arm,gic: Update Tegra compatibles dt-bindings: bus: Convert ACONNECT doc to json-schema Vidya Sagar (1): dt-bindings: Fix entry name for I/O High Voltage property Documentation/devicetree/bindings/arm/tegra.yaml | 3 + .../bindings/bus/nvidia,tegra210-aconnect.txt | 44 ---------- .../bindings/bus/nvidia,tegra210-aconnect.yaml | 82 ++++++++++++++++++ .../bindings/dma/nvidia,tegra210-adma.txt | 56 ------------ .../bindings/dma/nvidia,tegra210-adma.yaml | 99 ++++++++++++++++++++++ .../bindings/interrupt-controller/arm,gic.yaml | 9 +- .../bindings/pinctrl/nvidia,tegra194-pinmux.txt | 2 +- .../devicetree/bindings/vendor-prefixes.yaml | 2 + include/dt-bindings/memory/tegra124-mc.h | 68 +++++++++++++++ include/dt-bindings/memory/tegra20-mc.h | 53 ++++++++++++ include/dt-bindings/memory/tegra30-mc.h | 67 +++++++++++++++ 11 files changed, 383 insertions(+), 102 deletions(-) delete mode 100644 Documentation/devicetree/bindings/bus/nvidia,tegra210-aconnect.txt create mode 100644 Documentation/devicetree/bindings/bus/nvidia,tegra210-aconnect.yaml delete mode 100644 Documentation/devicetree/bindings/dma/nvidia,tegra210-adma.txt create mode 100644 Documentation/devicetree/bindings/dma/nvidia,tegra210-adma.yaml
WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com> To: arm@kernel.org, soc@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 v5.11-rc1 Date: Fri, 27 Nov 2020 15:43:24 +0100 [thread overview] Message-ID: <20201127144329.124891-1-thierry.reding@gmail.com> (raw) Message-ID: <20201127144324.uZgjGfo7zABh8-g53MLIg44v2BiMwhJZ5lOMgg81kHo@z> (raw) Hi ARM SoC maintainers, The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec: Linux 5.10-rc1 (2020-10-25 15:14:11 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-5.11-dt-bindings for you to fetch changes up to e36f9381420b28e1785d7900d4c1d9db6149cbcd: dt-bindings: bus: Convert ACONNECT doc to json-schema (2020-11-26 19:05:17 +0100) Thanks, Thierry ---------------------------------------------------------------- dt-bindings: Changes for v5.11-rc1 This contains a couple of conversions of bindings to json-schema, as well as symbolic names for the various memory clients on Tegra20, Tegra30 and Tegra124. There's also a couple of fixes for Tegra194 pinmux and ARM GIC bindings. Finally, a new vendor prefix is added for Ouya and the Ouya game console compatible string is defined. ---------------------------------------------------------------- Dmitry Osipenko (3): dt-bindings: memory: tegra20: Add memory client IDs dt-bindings: memory: tegra30: Add memory client IDs dt-bindings: memory: tegra124: Add memory client IDs Peter Geis (2): dt-bindings: Add vendor prefix for Ouya Inc. dt-bindings: ARM: tegra: Add Ouya game console Sameer Pujar (3): dt-bindings: dma: Convert ADMA doc to json-schema dt-bindings: interrupt-controller: arm,gic: Update Tegra compatibles dt-bindings: bus: Convert ACONNECT doc to json-schema Vidya Sagar (1): dt-bindings: Fix entry name for I/O High Voltage property Documentation/devicetree/bindings/arm/tegra.yaml | 3 + .../bindings/bus/nvidia,tegra210-aconnect.txt | 44 ---------- .../bindings/bus/nvidia,tegra210-aconnect.yaml | 82 ++++++++++++++++++ .../bindings/dma/nvidia,tegra210-adma.txt | 56 ------------ .../bindings/dma/nvidia,tegra210-adma.yaml | 99 ++++++++++++++++++++++ .../bindings/interrupt-controller/arm,gic.yaml | 9 +- .../bindings/pinctrl/nvidia,tegra194-pinmux.txt | 2 +- .../devicetree/bindings/vendor-prefixes.yaml | 2 + include/dt-bindings/memory/tegra124-mc.h | 68 +++++++++++++++ include/dt-bindings/memory/tegra20-mc.h | 53 ++++++++++++ include/dt-bindings/memory/tegra30-mc.h | 67 +++++++++++++++ 11 files changed, 383 insertions(+), 102 deletions(-) delete mode 100644 Documentation/devicetree/bindings/bus/nvidia,tegra210-aconnect.txt create mode 100644 Documentation/devicetree/bindings/bus/nvidia,tegra210-aconnect.yaml delete mode 100644 Documentation/devicetree/bindings/dma/nvidia,tegra210-adma.txt create mode 100644 Documentation/devicetree/bindings/dma/nvidia,tegra210-adma.yaml _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-11-27 14:43 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-27 14:43 Thierry Reding [this message] 2020-11-27 14:43 ` [GIT PULL 1/6] dt-bindings: Changes for v5.11-rc1 Thierry Reding 2020-11-27 14:43 ` [GIT PULL 2/6] soc/tegra: " Thierry Reding 2020-11-27 14:43 ` Thierry Reding 2020-11-27 14:43 ` [GIT PULL 3/6] firmware: tegra: " Thierry Reding 2020-11-27 14:43 ` Thierry Reding 2020-11-27 14:43 ` [GIT PULL 4/6] ARM: tegra: Device tree changes " Thierry Reding 2020-11-27 14:43 ` Thierry Reding 2020-11-27 14:43 ` [GIT PULL 5/6] arm64: " Thierry Reding 2020-11-27 14:43 ` Thierry Reding 2020-11-27 19:44 ` Arnd Bergmann 2020-11-27 19:44 ` Arnd Bergmann 2020-11-27 14:43 ` [GIT PULL 6/6] arm64: tegra: Default configuration " Thierry Reding 2020-11-27 14:43 ` Thierry Reding 2020-11-27 17:10 ` [GIT PULL 1/6] dt-bindings: Changes " patchwork-bot+linux-soc
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=20201127144329.124891-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 \ --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: linkBe 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).