[Linux-stm32] [PATCH v8 0/7] Add STM32MP25 SPI NOR support
Patrice CHOTARD
patrice.chotard at foss.st.com
Wed Apr 9 09:13:19 PDT 2025
On 4/9/25 17:54, Patrice CHOTARD wrote:
>
>
> On 4/8/25 08:38, Krzysztof Kozlowski wrote:
>> On Mon, Apr 07, 2025 at 03:27:31PM GMT, Patrice Chotard wrote:
>>> Signed-off-by: Patrice Chotard <patrice.chotard at foss.st.com>
>>> ---
>>> Patrice Chotard (7):
>>> MAINTAINERS: add entry for STM32 OCTO MEMORY MANAGER driver
>>> dt-bindings: memory-controllers: Add STM32 Octo Memory Manager controller
>>> memory: Add STM32 Octo Memory Manager driver
>>> arm64: dts: st: Add OMM node on stm32mp251
>>> arm64: dts: st: Add ospi port1 pinctrl entries in stm32mp25-pinctrl.dtsi
>>> arm64: dts: st: Add SPI NOR flash support on stm32mp257f-ev1 board
>>> arm64: defconfig: Enable STM32 Octo Memory Manager and OcstoSPI driver
>>>
>>> .../memory-controllers/st,stm32mp25-omm.yaml | 226 ++++++++++
>>> MAINTAINERS | 6 +
>>> arch/arm64/boot/dts/st/stm32mp25-pinctrl.dtsi | 51 +++
>>> arch/arm64/boot/dts/st/stm32mp251.dtsi | 54 +++
>>> arch/arm64/boot/dts/st/stm32mp257f-ev1.dts | 32 ++
>>> arch/arm64/configs/defconfig | 2 +
>>> drivers/memory/Kconfig | 17 +
>>> drivers/memory/Makefile | 1 +
>>> drivers/memory/stm32_omm.c | 474 +++++++++++++++++++++
>>> 9 files changed, 863 insertions(+)
>>> ---
>>> base-commit: 88424abd55ab36c3565898a656589a0a25ecd92f
>>
>> That's unknown commit.
>>
>> b4 diff '20250407-upstream_ospi_v6-v8-0-7b7716c1c1f6 at foss.st.com'
>> Using cached copy of the lookup
>> ---
>> Analyzing 81 messages in the thread
>> Preparing fake-am for v7: MAINTAINERS: add entry for STM32 OCTO MEMORY MANAGER driver
>> ERROR: Could not write fake-am tree
>> ---
>> Could not create fake-am range for lower series v7
>>
>> I tried on latest next, on some March next, on latest mainline. It seems
>> you use some weird base here, so anyway I won't be able to apply it.
>
> It was based on next-20250317 plus the 2 ospi patches already merged
> by Mark Brown, that's why.
>
>>
>> Please split the patchset per subsystem and send something based on
>> maintainer tree (so for me my for-next branch), mainline (which is the
>> same as for-next currently) or linux-next.... which would be the same as
>> my for-next branch currently.
>
> ok
For memory-controller subsystem i will include:
_ memory controller dt-bindings
_ memory controller driver
_ defconfig update
_ Maintainers file update
Are you ok with this proposal ?
Patrice
>
> Thanks
> Patrice
>
>>
>> Best regards,
>> Krzysztof
>>
> _______________________________________________
> Linux-stm32 mailing list
> Linux-stm32 at st-md-mailman.stormreply.com
> https://st-md-mailman.stormreply.com/mailman/listinfo/linux-stm32
More information about the linux-arm-kernel
mailing list