From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v2 2/5] soc/tegra: Changes for v4.16-rc1
Date: Thu, 21 Dec 2017 17:12:52 +0100 [thread overview]
Message-ID: <20171221161252.12920-1-thierry.reding@gmail.com> (raw)
In-Reply-To: <20171220191900.757-2-thierry.reding@gmail.com>
Hi ARM SoC maintainers,
The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.16-soc-2
for you to fetch changes up to ccf151847b81a3ad779b64f5f71f0632f2009eb6:
soc/tegra: fuse: Explicitly request DMA channel from APB DMA driver (2017-12-21 17:04:12 +0100)
This includes two additional patches that have been sitting in patchwork
for a long time and that I had forgotten to include. Please ignore the
first pull request and pull this instead.
Thanks,
Thierry
----------------------------------------------------------------
soc/tegra: Changes for v4.16-rc1
Fuse and chip ID support for Tegra186 is added in this set of changes,
followed by some unification work for the PMC driver in order to avoid
code duplication between Tegra186 and prior chips.
This also contains a couple of fixes for reading fuses on Tegra20.
----------------------------------------------------------------
Dmitry Osipenko (2):
soc/tegra: fuse: Fix reading registers using DMA on Tegra20
soc/tegra: fuse: Explicitly request DMA channel from APB DMA driver
Thierry Reding (7):
dt-bindings: misc: Add Tegra186 MISC registers bindings
Merge branch 'for-4.16/dt-bindings' into for-4.16/soc
soc/tegra: fuse: Move register mapping check
soc/tegra: fuse: Warn if accessing unmapped registers
soc/tegra: fuse: Add Tegra186 chip ID support
soc/tegra: pmc: Parameterize driver
soc/tegra: pmc: Consolidate Tegra186 support
Timo Alho (1):
soc/tegra: fuse: Add Tegra186 support
.../bindings/misc/nvidia,tegra186-misc.txt | 12 +
drivers/soc/tegra/Kconfig | 5 +-
drivers/soc/tegra/Makefile | 1 -
drivers/soc/tegra/fuse/fuse-tegra.c | 4 +
drivers/soc/tegra/fuse/fuse-tegra20.c | 13 +-
drivers/soc/tegra/fuse/fuse-tegra30.c | 24 +-
drivers/soc/tegra/fuse/fuse.h | 4 +
drivers/soc/tegra/fuse/tegra-apbmisc.c | 11 +-
drivers/soc/tegra/pmc-tegra186.c | 169 ------------
drivers/soc/tegra/pmc.c | 304 +++++++++++++++++----
include/soc/tegra/pmc.h | 12 +
11 files changed, 322 insertions(+), 237 deletions(-)
create mode 100644 Documentation/devicetree/bindings/misc/nvidia,tegra186-misc.txt
delete mode 100644 drivers/soc/tegra/pmc-tegra186.c
next prev parent reply other threads:[~2017-12-21 16:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 19:18 [GIT PULL 1/5] dt-bindings: Updates for v4.16-rc1 Thierry Reding
2017-12-20 19:18 ` [GIT PULL 2/5] soc/tegra: Changes " Thierry Reding
2017-12-20 20:00 ` Dmitry Osipenko
2017-12-21 16:12 ` Thierry Reding [this message]
2017-12-21 17:04 ` [GIT PULL v2 " Arnd Bergmann
2017-12-20 19:18 ` [GIT PULL 3/5] memory: tegra: " Thierry Reding
2017-12-21 17:07 ` Arnd Bergmann
2017-12-20 19:18 ` [GIT PULL 4/5] ARM: tegra: Device tree changes " Thierry Reding
2017-12-21 16:55 ` Arnd Bergmann
2017-12-20 19:19 ` [GIT PULL 5/5] arm64: tegra: Changes " Thierry Reding
2017-12-21 16:56 ` Arnd Bergmann
2017-12-21 16:54 ` [GIT PULL 1/5] dt-bindings: Updates " 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=20171221161252.12920-1-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).