[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c4a2ccb6-b052-4cce-8bfc-26bcae2a2e2a@foss.st.com>
Date: Tue, 13 May 2025 11:47:16 +0200
From: Patrice CHOTARD <patrice.chotard@...s.st.com>
To: Mark Brown <broonie@...nel.org>
CC: Philipp Zabel <p.zabel@...gutronix.de>,
Maxime Coquelin
<mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
<linux-kernel@...r.kernel.org>, <linux-spi@...r.kernel.org>,
<linux-stm32@...md-mailman.stormreply.com>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v4] spi: stm32-ospi: Make usage of
reset_control_acquire/release() API
On 5/12/25 14:11, Mark Brown wrote:
> On Mon, May 12, 2025 at 09:01:04AM +0200, Patrice Chotard wrote:
>> As ospi reset is consumed by both OMM and OSPI drivers, use the reset
>> acquire/release mechanism which ensure exclusive reset usage.
>
> This doesn't apply against current code, please check and resend.
Hi Mark
This patch has been submitted on top of reset tag reset-for-v6.16
due to dependency with new reset API devm_reset_control_array_get_exclusive_released().
How do you want to proceed ? Philipp can take it on its reset tree ?
Patrice
Powered by blists - more mailing lists