Linux SOC development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Linus Walleij <linusw@kernel.org>,
	Drew Fustini <fustini@kernel.org>,
	soc@lists.linux.dev
Cc: Krzysztof Kozlowski <krzk@kernel.org>, linux-kernel@vger.kernel.org
Subject: [GIT PULL] memory: drivers for v7.2
Date: Sun, 31 May 2026 14:19:15 +0200	[thread overview]
Message-ID: <20260531121914.22421-2-krzk@kernel.org> (raw)

Hi Arnd and SoC folks,

On top of previous fixes tags/memory-controller-drv-fixes-7.1
(which contains only one commit)

Best regards,
Krzysztof


The following changes since commit 754d60ad1c91895be0bc7d771fbf9fb3c9448640:

  memory: atmel-ebi: Allow deferred probing (2026-05-04 19:15:59 +0200)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-mem-ctrl.git tags/memory-controller-drv-7.2

for you to fetch changes up to d530ed059dac445dc5b81d564adf1952b5c4adba:

  memory: tegra264: Add full set of MC clients (2026-05-27 14:50:19 +0200)

----------------------------------------------------------------
Memory controller drivers for v7.2

1. Tegra MC/EMC:
   - Handle system sleep, necessary to re-program registers after system
     resume.  A few more improvements.
   - Add Tegra114 and Tegra238 Memory Controller, and Tegra114 External
     MC support.
   - Grow Tegra264 support.

2. Renesas XSPI: Document RZ/T2H and RZ/N2H variants, compatible with
   existing devices.

----------------------------------------------------------------
Ashish Mhetre (5):
      memory: tegra: Make ->resume() callback return void
      memory: tegra: Wire up system sleep PM ops
      memory: tegra: Restore MC interrupt masks on resume
      dt-bindings: memory: tegra: Add nvidia,tegra238-mc compatible
      memory: tegra: Add Tegra238 MC support

Ethan Tidmore (1):
      memory: tegra: Fix possible null pointer dereference

Krzysztof Kozlowski (4):
      Merge branch 'for-v7.2/tegra114-mc-bindings' into mem-ctrl-next
      memory: tegra114-emc: Do not print error on icc_node_create() failure
      memory: tegra114-emc: Simplify tegra114_emc_interconnect_init() error message
      memory: omap-gpmc: Silence W=1 kerneldoc warnings

Lad Prabhakar (2):
      dt-bindings: memory: renesas,rzg3e-xspi: Add RZ/T2H and RZ/N2H support
      memory: renesas-rpc-if: Fix duplicate device name on multi-instance platforms

Mikko Perttunen (1):
      memory: tegra: Deduplicate rate request management code

Sumit Gupta (3):
      memory: tegra264: Skip clients without bpmp_id or type
      dt-bindings: memory: tegra264: Add full set of MC client IDs
      memory: tegra264: Add full set of MC clients

Svyatoslav Ryhel (4):
      dt-bindings: memory: Document Tegra114 Memory Controller
      dt-bindings: memory: Document Tegra114 External Memory Controller
      memory: tegra: Implement EMEM regs and ICC ops for Tegra114
      memory: tegra: Add Tegra114 EMC driver

 .../memory-controllers/nvidia,tegra124-emc.yaml    |  174 +--
 .../memory-controllers/nvidia,tegra124-mc.yaml     |   31 +-
 .../memory-controllers/nvidia,tegra186-mc.yaml     |   31 +
 .../memory-controllers/renesas,rzg3e-xspi.yaml     |   60 +-
 drivers/memory/omap-gpmc.c                         |    6 +-
 drivers/memory/renesas-rpc-if.c                    |    2 +-
 drivers/memory/tegra/Kconfig                       |   19 +
 drivers/memory/tegra/Makefile                      |    3 +
 drivers/memory/tegra/mc.c                          |   40 +-
 drivers/memory/tegra/mc.h                          |    9 +
 drivers/memory/tegra/tegra-emc-common.c            |  143 +++
 drivers/memory/tegra/tegra-emc-common.h            |   46 +
 drivers/memory/tegra/tegra114-emc.c                | 1351 ++++++++++++++++++++
 drivers/memory/tegra/tegra114.c                    |  193 +++
 drivers/memory/tegra/tegra124-emc.c                |  107 +-
 drivers/memory/tegra/tegra186.c                    |    4 +-
 drivers/memory/tegra/tegra20-emc.c                 |  110 +-
 drivers/memory/tegra/tegra234.c                    |    2 +-
 drivers/memory/tegra/tegra238.c                    |  391 ++++++
 drivers/memory/tegra/tegra264.c                    |  568 +++++++-
 drivers/memory/tegra/tegra30-emc.c                 |  107 +-
 include/dt-bindings/memory/nvidia,tegra238-mc.h    |   74 ++
 include/dt-bindings/memory/nvidia,tegra264.h       |  287 +++++
 include/dt-bindings/memory/tegra114-mc.h           |   67 +
 include/soc/tegra/mc.h                             |    2 +-
 25 files changed, 3291 insertions(+), 536 deletions(-)
 create mode 100644 drivers/memory/tegra/tegra-emc-common.c
 create mode 100644 drivers/memory/tegra/tegra-emc-common.h
 create mode 100644 drivers/memory/tegra/tegra114-emc.c
 create mode 100644 drivers/memory/tegra/tegra238.c
 create mode 100644 include/dt-bindings/memory/nvidia,tegra238-mc.h

             reply	other threads:[~2026-05-31 12:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-31 12:19 Krzysztof Kozlowski [this message]
2026-06-09 16:40 ` [GIT PULL] memory: drivers for v7.2 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=20260531121914.22421-2-krzk@kernel.org \
    --to=krzk@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=fustini@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=soc@lists.linux.dev \
    /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