linux-tegra.vger.kernel.org archive mirror
 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 5/6] PCI: tegra: Changes for v6.5-rc1
Date: Fri,  9 Jun 2023 21:36:19 +0200	[thread overview]
Message-ID: <20230609193620.2275240-5-thierry.reding@gmail.com> (raw)
In-Reply-To: <20230609193620.2275240-1-thierry.reding@gmail.com>

Hi ARM SoC maintainers,

The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:

  Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.5-pci

for you to fetch changes up to 9365bf006f53d04b69d560ef7e2bf4be4c4d693a:

  PCI: tegra194: Add interconnect support in Tegra234 (2023-05-16 12:11:36 +0200)

Thanks,
Thierry

----------------------------------------------------------------
PCI: tegra: Changes for v6.5-rc1

This contains updates to the PCI driver for Tegra194 and later devices
that depend on the memory controller interconnect changes.

----------------------------------------------------------------
Shubhi Garg (1):
      dt-bindings: tegra: Document compatible for IGX

Sumit Gupta (7):
      dt-bindings: tegra: Add ICC IDs for dummy memory clients
      memory: tegra: Add interconnect support for DRAM scaling in Tegra234
      memory: tegra: Add memory clients for Tegra234
      memory: tegra: Add software memory clients in Tegra234
      memory: tegra: Make CPU cluster BW request a multiple of MC channels
      PCI: tegra194: Fix possible array out of bounds access
      PCI: tegra194: Add interconnect support in Tegra234

Thierry Reding (2):
      Merge branch 'for-6.5/dt-bindings' into for-6.5/memory
      Merge branch 'for-6.5/memory' into for-6.5/pci

 Documentation/devicetree/bindings/arm/tegra.yaml |   5 +
 drivers/memory/tegra/mc.c                        |  24 +
 drivers/memory/tegra/mc.h                        |   1 +
 drivers/memory/tegra/tegra186-emc.c              | 133 +++++
 drivers/memory/tegra/tegra234.c                  | 595 ++++++++++++++++++++++-
 drivers/pci/controller/dwc/pcie-tegra194.c       |  44 +-
 include/dt-bindings/memory/tegra234-mc.h         |   5 +
 include/linux/tegra-icc.h                        |  65 +++
 include/soc/tegra/mc.h                           |   8 +
 9 files changed, 871 insertions(+), 9 deletions(-)
 create mode 100644 include/linux/tegra-icc.h

  parent reply	other threads:[~2023-06-09 19:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09 19:36 [GIT PULL 1/6] soc/tegra: Changes for v6.5-rc1 Thierry Reding
2023-06-09 19:36 ` [GIT PULL 2/6] firmware: tegra: " Thierry Reding
2023-06-09 19:36 ` [GIT PULL 3/6] dt-bindings: " Thierry Reding
2023-06-14  9:27   ` Thierry Reding
2023-06-20 16:26   ` [GIT PULL v2] " Thierry Reding
2023-06-09 19:36 ` [GIT PULL 4/6] memory: tegra: " Thierry Reding
2023-06-09 19:36 ` Thierry Reding [this message]
2023-06-09 19:36 ` [GIT PULL 6/6] arm64: tegra: Device tree changes " 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=20230609193620.2275240-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).