All of lore.kernel.org
 help / color / mirror / Atom feed
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 2/6] soc/tegra: Changes for v5.19-rc1
Date: Fri,  6 May 2022 16:30:01 +0200	[thread overview]
Message-ID: <20220506143005.3916655-2-thierry.reding@gmail.com> (raw)
In-Reply-To: <20220506143005.3916655-1-thierry.reding@gmail.com>

Hi ARM SoC maintainers,

The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:

  Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-5.19-soc

for you to fetch changes up to d3a20dcbca4880ada8974b2d0167df99161bbfaf:

  soc/tegra: pmc: Document core domain fields (2022-05-06 10:53:19 +0200)

Thanks,
Thierry

----------------------------------------------------------------
soc/tegra: Changes for v5.19-rc1

This set of changes adds nvmem cell lookup entries for Tegra194 that are
used to read calibration data from the SoC fuses, and updates the reset
sources for Tegra234.

Other than that, included is a minor build fix for a missing dependency
that can be encountered very rarely in random config builds. Lastly some
kerneldoc comments are added to avoid build warnings.

----------------------------------------------------------------
Sagar Kamble (1):
      soc/tegra: fuse: Add nvmem cell lookup entries for Tegra194

Sandipan Patra (1):
      soc/tegra: pmc: Update Tegra234 reset sources

Thierry Reding (2):
      soc/tegra: pmc: Select REGMAP
      soc/tegra: pmc: Document core domain fields

 drivers/soc/tegra/Kconfig             |  1 +
 drivers/soc/tegra/fuse/fuse-tegra.c   |  8 ++++----
 drivers/soc/tegra/fuse/fuse-tegra30.c | 17 ++++++++++++++++-
 drivers/soc/tegra/pmc.c               | 35 +++++++++++++++++++++++++++--------
 4 files changed, 48 insertions(+), 13 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
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 2/6] soc/tegra: Changes for v5.19-rc1
Date: Fri,  6 May 2022 16:30:01 +0200	[thread overview]
Message-ID: <20220506143005.3916655-2-thierry.reding@gmail.com> (raw)
In-Reply-To: <20220506143005.3916655-1-thierry.reding@gmail.com>

Hi ARM SoC maintainers,

The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:

  Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-5.19-soc

for you to fetch changes up to d3a20dcbca4880ada8974b2d0167df99161bbfaf:

  soc/tegra: pmc: Document core domain fields (2022-05-06 10:53:19 +0200)

Thanks,
Thierry

----------------------------------------------------------------
soc/tegra: Changes for v5.19-rc1

This set of changes adds nvmem cell lookup entries for Tegra194 that are
used to read calibration data from the SoC fuses, and updates the reset
sources for Tegra234.

Other than that, included is a minor build fix for a missing dependency
that can be encountered very rarely in random config builds. Lastly some
kerneldoc comments are added to avoid build warnings.

----------------------------------------------------------------
Sagar Kamble (1):
      soc/tegra: fuse: Add nvmem cell lookup entries for Tegra194

Sandipan Patra (1):
      soc/tegra: pmc: Update Tegra234 reset sources

Thierry Reding (2):
      soc/tegra: pmc: Select REGMAP
      soc/tegra: pmc: Document core domain fields

 drivers/soc/tegra/Kconfig             |  1 +
 drivers/soc/tegra/fuse/fuse-tegra.c   |  8 ++++----
 drivers/soc/tegra/fuse/fuse-tegra30.c | 17 ++++++++++++++++-
 drivers/soc/tegra/pmc.c               | 35 +++++++++++++++++++++++++++--------
 4 files changed, 48 insertions(+), 13 deletions(-)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-05-06 14:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06 14:30 [GIT PULL 1/6] ARM: tegra: Core changes for v5.19-rc1 Thierry Reding
2022-05-06 14:30 ` Thierry Reding
2022-05-06 14:30 ` Thierry Reding [this message]
2022-05-06 14:30   ` [GIT PULL 2/6] soc/tegra: Changes " Thierry Reding
2022-05-06 14:30 ` [GIT PULL 3/6] dt-bindings: " Thierry Reding
2022-05-06 14:30   ` Thierry Reding
2022-05-06 14:30 ` [GIT PULL 4/6] ARM: tegra: Default configuration fixes for v5.18 Thierry Reding
2022-05-06 14:30   ` Thierry Reding
2022-05-06 14:33   ` Thierry Reding
2022-05-06 14:33     ` Thierry Reding
2022-05-06 14:30 ` [GIT PULL 5/6] arm64: tegra: Device tree changes for v5.19-rc1 Thierry Reding
2022-05-06 14:30   ` Thierry Reding
2022-05-06 14:30 ` [GIT PULL 6/6] arm64: tegra: Default configuration updates " Thierry Reding
2022-05-06 14:30   ` Thierry Reding
2022-05-06 21:10 ` [GIT PULL 1/6] ARM: tegra: Core changes " patchwork-bot+linux-soc
2022-05-09 21:40 ` 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=20220506143005.3916655-2-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.