From: Patrice CHOTARD <patrice.chotard@foss.st.com>
To: Philipp Zabel <p.zabel@pengutronix.de>,
Mark Brown <broonie@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-spi@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 2/2] spi: stm32-ospi: Make usage of reset_control_acquire/release() API
Date: Wed, 7 May 2025 18:04:32 +0200 [thread overview]
Message-ID: <721ec8c6-ceb5-4e6c-91f6-2e234f12ff2b@foss.st.com> (raw)
In-Reply-To: <3685c6351d8b940abe70ccf22d783e71ced6f6da.camel@pengutronix.de>
On 5/5/25 15:12, Philipp Zabel wrote:
> Hi Patrice,
>
> On Fr, 2025-04-11 at 14:41 +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 avoid to call reset_control_get/put() in OMM driver each time
>> we need to reset OSPI children and guarantee the reset line stays
>> deasserted.
>>
>> Signed-off-by: Patrice Chotard <patrice.chotard@foss.st.com>
>> ---
>> drivers/spi/spi-stm32-ospi.c | 15 +++++++++------
>> 1 file changed, 9 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/spi/spi-stm32-ospi.c b/drivers/spi/spi-stm32-ospi.c
>> index d002b9c16714684e4e4623f9255a7f2660c46fd1..ef840f377459891b559be6d6c0435408fb58a1e9 100644
>> --- a/drivers/spi/spi-stm32-ospi.c
>> +++ b/drivers/spi/spi-stm32-ospi.c
>> @@ -804,7 +804,7 @@ static int stm32_ospi_get_resources(struct platform_device *pdev)
>> return ret;
>> }
>>
>> - ospi->rstc = devm_reset_control_array_get_exclusive(dev);
>> + ospi->rstc = devm_reset_control_array_get_exclusive_released(dev);
>> if (IS_ERR(ospi->rstc))
>> return dev_err_probe(dev, PTR_ERR(ospi->rstc),
>> "Can't get reset\n");
>> @@ -936,11 +936,14 @@ static int stm32_ospi_probe(struct platform_device *pdev)
>> if (ret < 0)
>> goto err_pm_enable;
>>
>> - if (ospi->rstc) {
>> - reset_control_assert(ospi->rstc);
>> - udelay(2);
>> - reset_control_deassert(ospi->rstc);
>> - }
>> + ret = reset_control_acquire(ospi->rstc);
>> + if (ret)
>> + return dev_err_probe(dev, ret, "Can not acquire reset %d\n", ret);
>> +
>> + reset_control_assert(ospi->rstc);
>> + udelay(2);
>> + reset_control_deassert(ospi->rstc);
>> + reset_control_release(ospi->rstc);
>
> Could you keep the reset control (mostly) acquired from probe() to
> remove()? The reset control would have to be released/acquired in OSPI
> suspend/resume so that OMM can temporarily acquire control during OMM
> resume.
Ok
Thanks
Patrice
>
> regards
> Philipp
next prev parent reply other threads:[~2025-05-07 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 12:41 [PATCH v2 0/2] reset: Add devm_reset_control_array_get_exclusive_released() Patrice Chotard
2025-04-11 12:41 ` [PATCH v2 1/2] " Patrice Chotard
2025-05-05 13:28 ` Philipp Zabel
2025-04-11 12:41 ` [PATCH v2 2/2] spi: stm32-ospi: Make usage of reset_control_acquire/release() API Patrice Chotard
2025-05-05 13:12 ` Philipp Zabel
2025-05-07 16:04 ` Patrice CHOTARD [this message]
2025-06-09 19:33 ` [PATCH v2 0/2] reset: Add devm_reset_control_array_get_exclusive_released() 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=721ec8c6-ceb5-4e6c-91f6-2e234f12ff2b@foss.st.com \
--to=patrice.chotard@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=broonie@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 \
/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;
as well as URLs for NNTP newsgroup(s).