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 4/7] cpuidle: tegra: Changes for v5.16-rc1
Date: Fri, 8 Oct 2021 22:11:29 +0200 [thread overview]
Message-ID: <20211008201132.1678814-5-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-cpuidle
for you to fetch changes up to bdb1ffdad3b73e4d0538098fc02e2ea87a6b27cd:
cpuidle: tegra: Check whether PMC is ready (2021-10-05 19:11:40 +0200)
Thanks,
Thierry
----------------------------------------------------------------
cpuidle: tegra: Changes for v5.16-rc1
This pulls in the for-5.16/clk and for-5.16/soc branches and uses the
stubs added in them to enable compile testing of the cpuidle driver.
While at it, this also fixes a potential driver probe order race
condition between the PMC and the cpuidle driver.
----------------------------------------------------------------
Dmitry Osipenko (5):
soc/tegra: fuse: Add stubs needed for compile testing
soc/tegra: irq: Add stubs needed for compile testing
soc/tegra: pm: Make stubs usable for compile testing
cpuidle: tegra: Enable compile testing
cpuidle: tegra: Check whether PMC is ready
Thierry Reding (3):
clk: tegra: Add stubs needed for compile testing
Merge branch 'for-5.16/clk' into for-5.16/cpuidle
Merge branch 'for-5.16/soc' into for-5.16/cpuidle
drivers/cpuidle/Kconfig.arm | 2 +-
drivers/cpuidle/cpuidle-tegra.c | 3 +++
include/linux/clk/tegra.h | 24 +++++++++++++++++++++++-
include/soc/tegra/fuse.h | 31 ++++++++++++++++++++++++++-----
include/soc/tegra/irq.h | 9 ++++++++-
include/soc/tegra/pm.h | 2 +-
6 files changed, 62 insertions(+), 9 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-10-08 20:14 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 ` [GIT PULL 1/7] dt-bindings: Changes " Thierry Reding
2021-10-11 22:11 ` 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 ` Thierry Reding [this message]
2021-10-11 14:54 ` [GIT PULL 4/7] cpuidle: tegra: " 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-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;
as well as URLs for NNTP newsgroup(s).