[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174109554967.53872.7193131885074327926.b4-ty@kernel.org>
Date: Tue, 04 Mar 2025 13:39:09 +0000
From: Mark Brown <broonie@...nel.org>
To: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Philipp Zabel <p.zabel@...gutronix.de>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Arnd Bergmann <arnd@...db.de>, Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>, patrice.chotard@...s.st.com
Cc: linux-spi@...r.kernel.org, devicetree@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
christophe.kerello@...s.st.com
Subject: Re: (subset) [PATCH v5 0/8] Add STM32MP25 SPI NOR support
On Wed, 19 Feb 2025 09:00:51 +0100, patrice.chotard@...s.st.com wrote:
> This series adds SPI NOR support for STM32MP25 SoCs from STMicroelectronics.
>
> On STM32MP25 SoCs family, an Octo Memory Manager block manages the muxing,
> the memory area split, the chip select override and the time constraint
> between its 2 Octo SPI children.
>
> Due to these depedencies, this series adds support for:
> - Octo Memory Manager driver.
> - Octo SPI driver.
> - yaml schema for Octo Memory Manager and Octo SPI drivers.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/8] dt-bindings: spi: Add STM32 OSPI controller
commit: bed97e35786a7d0141d1ecaaace03c46b5435d75
[2/8] spi: stm32: Add OSPI driver
commit: 79b8a705e26c08f8f09dd55f1dd56f2375973d2d
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
Powered by blists - more mailing lists