mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: soc@lists.linux.dev
Cc: Krzysztof Kozlowski <krzk@kernel.org>, linux-kernel@vger.kernel.org
Subject: [GIT PULL] memory: drivers for v7.4
Date: Mon,  5 Oct 2026 13:04:27 +0200	[thread overview]
Message-ID: <20261005110427.41458-2-krzk@kernel.org> (raw)

Hi Arnd and SoC folks,

Note that I do not treat untested, LLM-assisted fixes as critical fixes, thus
usually do not take them into fixes cycle.

Best regards,
Krzysztof


The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:

  Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)

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.4

for you to fetch changes up to a22355280361d2a376a2020059a2bae11e6cea10:

  memory: stm32_omm: fix child clock leak on set_amcr() error path (2026-09-23 19:57:14 +0200)

----------------------------------------------------------------
Memory controller drivers for v7.4

1. Broadcom DPFE: Fix handling kernel memory accesses with malicious or
   compromised firmware and possible out-of-bounds read triggered by
   buggy co-processor.  Also validate firmware image contents before
   processing it.

2. Renesas RPC IF: One fix for volatile register access, several
   cleanups and enable autosuspend in runtime PM.

3. Several minor improvements and fixes for various drivers: TI EMIF,
   Samsung Exynos5422 DMC, Nvidia Tegra264 and STM32 OMM.  The fixes
   seems to be effect of LLM usage, thus they were neither reproduced
   nor tested, making them non-critical fixes.

4. Mediatek SMI: Add support for MT8189 SoC.

----------------------------------------------------------------
Diego Fernando Mancera Gomez (1):
      memory: stm32_omm: fix child clock leak on set_amcr() error path

Jiawen Liu (1):
      memory: exynos5422-dmc: handle clock enable failures

Justin Chen (2):
      memory: brcmstb_dpfe: Fix out-of-bounds access due to DCPU offset
      memory: brcmstb_dpfe: Bounds check DCPU-supplied MSG_ARG_COUNT

Kees Cook (1):
      memory: emif: Remove const from min_tck allocation type

Ketan Patil (3):
      memory: tegra: Use named defines for Tegra264 MC apertures
      memory: tegra: Parameterise Tegra264 MCF slice bound
      memory: tegra: Refactor Tegra264 mc-err code

Lad Prabhakar (6):
      memory: renesas-rpc-if: Mark XSPI_CDD1BUF0 as volatile
      memory: renesas-rpc-if: Move static bridge configurations out of dirmap hot paths
      memory: renesas-rpc-if: Consolidate XSPI_CDTBUF0 updates in write path
      memory: renesas-rpc-if: Consolidate XSPI_CDTBUF0 updates in read path
      memory: renesas-rpc-if: Consolidate command setup register programming
      memory: renesas-rpc-if: Use runtime PM autosuspend after transfers

Miles Krause (1):
      memory: emif: fix device_node reference leak on np_ddr

Pengpeng Hou (1):
      memory: brcmstb_dpfe: validate firmware section sizes

Thomas Huth (1):
      memory: emif: Replace __ASSEMBLY__ with __ASSEMBLER__ in non-uapi headers

Zhengnan Chen (2):
      dt-bindings: memory-controllers: mtk-smi: Add support for mt8189
      memory: mtk-smi: Add MT8189 support

 .../memory-controllers/mediatek,smi-common.yaml    |  21 +-
 .../memory-controllers/mediatek,smi-larb.yaml      |   3 +
 drivers/memory/brcmstb_dpfe.c                      |  41 ++-
 drivers/memory/emif.c                              |   6 +-
 drivers/memory/emif.h                              |   4 +-
 drivers/memory/mtk-smi.c                           |  45 +++
 drivers/memory/renesas-rpc-if.c                    |  87 ++---
 drivers/memory/samsung/exynos5422-dmc.c            |  11 +-
 drivers/memory/stm32_omm.c                         |   2 +
 drivers/memory/tegra/tegra264.c                    | 392 +++++++++++++--------
 10 files changed, 398 insertions(+), 214 deletions(-)

                 reply	other threads:[~2026-10-05 11:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261005110427.41458-2-krzk@kernel.org \
    --to=krzk@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

all inboxes | Powered by JetHome®