From: Krzysztof Kozlowski <krzk@kernel.org>
To: Patrice Chotard <patrice.chotard@foss.st.com>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Gatien Chevallier <gatien.chevallier@foss.st.com>
Cc: christophe.kerello@foss.st.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, stable@vger.kernel.org
Subject: Re: [PATCH v13 0/4] Add STM32MP25 SPI NOR support
Date: Wed, 7 May 2025 10:35:04 +0200 [thread overview]
Message-ID: <6d2c1b03-6046-4a8a-8858-47f9bc9dbb7b@kernel.org> (raw)
In-Reply-To: <1f7760c6-0fdf-48b0-9c13-85fa5e01cddd@kernel.org>
On 07/05/2025 10:28, Krzysztof Kozlowski wrote:
> On 07/05/2025 09:25, Patrice Chotard 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.
>>
>> The device tree files adds Octo Memory Manager and its 2 associated Octo
>> SPI chidren in stm32mp251.dtsi and adds SPI NOR support in stm32mp257f-ev1
>> board.
>>
>> Signed-off-by: Patrice Chotard <patrice.chotard@foss.st.com>
>>
>> Changes in v13:
>> - Make firewall prototypes always exposed.
>
>
> I do not see any changes here.
>
> b4 diff suggests this is the same as v11 so I expect the same failures.
My bad, I missed patch #1 here, so it seems fine on the first glance.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-05-07 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 7:25 [PATCH v13 0/4] Add STM32MP25 SPI NOR support Patrice Chotard
2025-05-07 7:25 ` [PATCH v13 1/4] firewall: Always expose firewall prototype Patrice Chotard
2025-05-07 9:22 ` Krzysztof Kozlowski
2025-05-07 7:25 ` [PATCH v13 2/4] dt-bindings: memory-controllers: Add STM32 Octo Memory Manager controller Patrice Chotard
2025-05-07 7:25 ` [PATCH v13 3/4] memory: Add STM32 Octo Memory Manager driver Patrice Chotard
2025-05-07 7:25 ` [PATCH v13 4/4] MAINTAINERS: add entry for STM32 OCTO MEMORY MANAGER driver Patrice Chotard
2025-05-07 8:28 ` [PATCH v13 0/4] Add STM32MP25 SPI NOR support Krzysztof Kozlowski
2025-05-07 8:31 ` Patrice CHOTARD
2025-05-07 8:35 ` Krzysztof Kozlowski [this message]
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=6d2c1b03-6046-4a8a-8858-47f9bc9dbb7b@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=catalin.marinas@arm.com \
--cc=christophe.kerello@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gatien.chevallier@foss.st.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=patrice.chotard@foss.st.com \
--cc=robh@kernel.org \
--cc=stable@vger.kernel.org \
--cc=will@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