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 v2 5/7] memory: tegra: Changes for v6.2-rc1
Date: Mon, 21 Nov 2022 18:12:37 +0100 [thread overview]
Message-ID: <20221121171239.2041835-5-thierry.reding@gmail.com> (raw)
In-Reply-To: <20221121171239.2041835-1-thierry.reding@gmail.com>
Hi ARM SoC maintainers,
The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.2-memory-v2
for you to fetch changes up to 5cd24ca0985f2dfb5628354fb63ede67b1dd993d:
memory: tegra: Add DLA clients for Tegra234 (2022-11-21 13:29:02 +0100)
Thanks,
Thierry
----------------------------------------------------------------
memory: tegra: Changes for v6.2-rc1
Some cleanups replace open-coded debugfs attributes and memory client
IDs are added for the DLA IP found on Tegra234 SoCs.
----------------------------------------------------------------
Jon Hunter (2):
dt-bindings: tegra: Update headers for Tegra234
memory: tegra: Add DLA clients for Tegra234
Liu Shixin (4):
memory: tegra20-emc: Use DEFINE_SHOW_ATTRIBUTE to simplify code
memory: tegra30-emc: Use DEFINE_SHOW_ATTRIBUTE to simplify code
memory: tegra210-emc: Use DEFINE_SHOW_ATTRIBUTE to simplify code
memory: tegra186-emc: Use DEFINE_SHOW_ATTRIBUTE to simplify code
Mikko Perttunen (1):
dt-bindings: Add headers for NVDEC on Tegra234
Thierry Reding (1):
Merge branch for-6.2/dt-bindings into for-6.2/memory
drivers/memory/tegra/tegra186-emc.c | 15 +-
drivers/memory/tegra/tegra20-emc.c | 15 +-
drivers/memory/tegra/tegra210-emc-core.c | 15 +-
drivers/memory/tegra/tegra234.c | 160 +++++++
drivers/memory/tegra/tegra30-emc.c | 15 +-
include/dt-bindings/clock/tegra234-clock.h | 639 ++++++++++++++++++++++++-
include/dt-bindings/memory/tegra234-mc.h | 440 ++++++++++++++++-
include/dt-bindings/power/tegra234-powergate.h | 15 +
include/dt-bindings/reset/tegra234-reset.h | 111 ++++-
9 files changed, 1339 insertions(+), 86 deletions(-)
next prev parent reply other threads:[~2022-11-21 17:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 17:12 [GIT PULL v2 1/7] soc/tegra: Changes for v6.2-rc1 Thierry Reding
2022-11-21 17:12 ` [GIT PULL v2 2/7] firmware: tegra: " Thierry Reding
2022-11-22 21:25 ` Arnd Bergmann
2022-11-23 11:33 ` Thierry Reding
2022-11-23 13:23 ` Arnd Bergmann
2022-11-25 10:12 ` Thierry Reding
2022-11-21 17:12 ` [GIT PULL v2 3/7] clk: " Thierry Reding
2022-11-21 17:12 ` [GIT PULL v2 4/7] dt-bindings: " Thierry Reding
2022-11-29 17:16 ` Rob Herring
2022-11-21 17:12 ` Thierry Reding [this message]
2022-11-21 17:12 ` [GIT PULL v2 6/7] ARM: tegra: Device tree changes " Thierry Reding
2022-11-21 17:12 ` [GIT PULL v2 7/7] arm64: " Thierry Reding
2022-11-22 22:09 ` Arnd Bergmann
2022-11-23 11:36 ` Thierry Reding
2022-11-22 22:20 ` [GIT PULL v2 1/7] soc/tegra: Changes " patchwork-bot+linux-soc
2022-11-23 12:00 ` 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=20221121171239.2041835-5-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