All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Patrice CHOTARD <patrice.chotard@foss.st.com>,
	Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Cc: linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, christophe.kerello@foss.st.com
Subject: Re: [PATCH v5 4/8] memory: Add STM32 Octo Memory Manager driver
Date: Mon, 10 Mar 2025 15:10:53 +0100	[thread overview]
Message-ID: <ebc23aa2-c850-43c3-baa0-922da31208df@kernel.org> (raw)
In-Reply-To: <6e1757ea-3f5e-4cc0-b142-aee52f016c8f@foss.st.com>

On 10/03/2025 14:52, Patrice CHOTARD wrote:
> 
> 
> On 2/19/25 09:00, patrice.chotard@foss.st.com wrote:
>> From: Patrice Chotard <patrice.chotard@foss.st.com>
>>
>> Octo Memory Manager driver (OMM) manages:
>>   - the muxing between 2 OSPI busses and 2 output ports.
>>     There are 4 possible muxing configurations:
>>       - direct mode (no multiplexing): OSPI1 output is on port 1 and OSPI2
>>         output is on port 2
>>       - OSPI1 and OSPI2 are multiplexed over the same output port 1
>>       - swapped mode (no multiplexing), OSPI1 output is on port 2,
>>         OSPI2 output is on port 1
>>       - OSPI1 and OSPI2 are multiplexed over the same output port 2
>>   - the split of the memory area shared between the 2 OSPI instances.
>>   - chip select selection override.
>>   - the time between 2 transactions in multiplexed mode.
>>   - check firewall access.
>>



Please kindly trim the replies from unnecessary context. It makes it
much easier to find new content.

...
> 
> 
> Hi all,
> 
> Anybody alse has additionnal remarks on this driver ?

I am waiting too...

Best regards,
Krzysztof


  reply	other threads:[~2025-03-10 16:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-19  8:00 [PATCH v5 0/8] Add STM32MP25 SPI NOR support patrice.chotard
2025-02-19  8:00 ` [PATCH v5 1/8] dt-bindings: spi: Add STM32 OSPI controller patrice.chotard
2025-02-19  8:00 ` [PATCH v5 2/8] spi: stm32: Add OSPI driver patrice.chotard
2025-02-19  8:00 ` [PATCH v5 3/8] dt-bindings: memory-controllers: Add STM32 Octo Memory Manager controller patrice.chotard
2025-02-19  8:00 ` [PATCH v5 4/8] memory: Add STM32 Octo Memory Manager driver patrice.chotard
2025-03-10 13:52   ` Patrice CHOTARD
2025-03-10 14:10     ` Krzysztof Kozlowski [this message]
2025-03-13  7:30     ` Krzysztof Kozlowski
2025-03-11 16:04   ` Krzysztof Kozlowski
2025-03-12 14:23     ` Patrice CHOTARD
2025-03-13  7:33       ` Krzysztof Kozlowski
2025-03-18 13:40         ` Patrice CHOTARD
2025-03-19  7:37           ` Krzysztof Kozlowski
2025-03-20 13:28             ` Patrice CHOTARD
2025-02-19  8:00 ` [PATCH v5 5/8] arm64: dts: st: Add OMM node on stm32mp251 patrice.chotard
2025-02-19  8:00 ` [PATCH v5 6/8] arm64: dts: st: Add ospi port1 pinctrl entries in stm32mp25-pinctrl.dtsi patrice.chotard
2025-02-19  8:00 ` [PATCH v5 7/8] arm64: dts: st: Add SPI NOR flash support on stm32mp257f-ev1 board patrice.chotard
2025-02-19  8:00 ` [PATCH v5 8/8] arm64: defconfig: Enable STM32 Octo Memory Manager and OcstoSPI driver patrice.chotard
2025-03-04 13:39 ` (subset) [PATCH v5 0/8] Add STM32MP25 SPI NOR support Mark Brown

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=ebc23aa2-c850-43c3-baa0-922da31208df@kernel.org \
    --to=krzk@kernel.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=christophe.kerello@foss.st.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.