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 4/8] soc: tegra: Changes for v5.6-rc1
Date: Sat, 11 Jan 2020 01:35:49 +0100 [thread overview]
Message-ID: <20200111003553.2411874-4-thierry.reding@gmail.com> (raw)
In-Reply-To: <20200111003553.2411874-1-thierry.reding@gmail.com>
Hi ARM SoC maintainers,
The following changes since commit e42617b825f8073569da76dc4510bfa019b1c35a:
Linux 5.5-rc1 (2019-12-08 14:57:55 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-5.6-soc
for you to fetch changes up to 02676345e9b31ad8907af3755960e3cfef575f8d:
soc/tegra: fuse: Unmap registers once they are not needed anymore (2020-01-10 15:59:43 +0100)
Thanks,
Thierry
----------------------------------------------------------------
soc: tegra: Changes for v5.6-rc1
This adds a couple of optimizations to how the chip ID and straps are
read and adds support for the FUSE block on Tegra194. Included is also a
small optimization for the coupled regulator driver to abort early if no
voltage change has occurred.
----------------------------------------------------------------
Dmitry Osipenko (6):
soc/tegra: fuse: Add APB DMA dependency for Tegra20
soc/tegra: regulators: Do nothing if voltage is unchanged
soc/tegra: fuse: Cache values of straps and Chip ID registers
soc/tegra: fuse: Warn if straps are not ready
soc/tegra: fuse: Correct straps' address for older Tegra124 device trees
soc/tegra: fuse: Unmap registers once they are not needed anymore
JC Kuo (1):
soc/tegra: fuse: Add Tegra194 support
drivers/soc/tegra/Kconfig | 1 +
drivers/soc/tegra/fuse/fuse-tegra.c | 3 +++
drivers/soc/tegra/fuse/fuse-tegra30.c | 29 +++++++++++++++++++++++++++++
drivers/soc/tegra/fuse/fuse.h | 4 ++++
drivers/soc/tegra/fuse/tegra-apbmisc.c | 34 ++++++++++++++++++++--------------
drivers/soc/tegra/regulators-tegra20.c | 8 +++++++-
drivers/soc/tegra/regulators-tegra30.c | 6 ++++++
7 files changed, 70 insertions(+), 15 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:[~2020-01-11 0:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 0:35 [GIT PULL 1/8] dt-bindings: Changes for v5.6-rc1 Thierry Reding
2020-01-11 0:35 ` [GIT PULL 2/8] bus: tegra: " Thierry Reding
2020-01-11 0:35 ` [GIT PULL 3/8] memory: " Thierry Reding
2020-01-11 0:35 ` Thierry Reding [this message]
2020-01-11 0:35 ` [GIT PULL 5/8] ARM: tegra: Core changes " Thierry Reding
2020-01-11 0:35 ` [GIT PULL 6/8] ARM: tegra: Device tree " Thierry Reding
2020-01-11 0:35 ` [GIT PULL 7/8] arm64: " Thierry Reding
2020-01-11 0:35 ` [GIT PULL 8/8] dt-bindings: Changes " Thierry Reding
2020-01-11 0:57 ` Thierry Reding
2020-01-11 0:55 ` [GIT PULL 8/8] arm64: tegra: Default configuration updates " Thierry Reding
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=20200111003553.2411874-4-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).