From: Tero Kristo <t-kristo@ti.com>
To: Philipp Zabel <p.zabel@pengutronix.de>,
ssantosh@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org, robh+dt@kernel.org
Cc: tony@atomide.com, devicetree@vger.kernel.org
Subject: Re: [PATCHv2 03/11] soc: ti: omap-prm: poll for reset complete during de-assert
Date: Fri, 30 Aug 2019 12:07:07 +0300 [thread overview]
Message-ID: <ceed701f-481c-4905-727e-ba3af2cf8ff2@ti.com> (raw)
In-Reply-To: <1567084467.5345.9.camel@pengutronix.de>
On 29/08/2019 16:14, Philipp Zabel wrote:
> Hi Tero,
>
> On Wed, 2019-08-28 at 10:19 +0300, Tero Kristo wrote:
>> Poll for reset completion status during de-assertion of reset, otherwise
>> the IP in question might be accessed before it has left reset properly.
>>
>> Signed-off-by: Tero Kristo <t-kristo@ti.com>
>> ---
>> drivers/soc/ti/omap_prm.c | 20 ++++++++++++++++++++
>> 1 file changed, 20 insertions(+)
>>
>> diff --git a/drivers/soc/ti/omap_prm.c b/drivers/soc/ti/omap_prm.c
>> index fd5c431f8736..afeb70761b27 100644
>> --- a/drivers/soc/ti/omap_prm.c
>> +++ b/drivers/soc/ti/omap_prm.c
>> @@ -127,6 +127,7 @@ static int omap_reset_deassert(struct reset_controller_dev *rcdev,
>> u32 v;
>> int st_bit;
>> bool has_rstst;
>> + int timeout = 0;
>>
>> if (!_is_valid_reset(reset, id))
>> return -EINVAL;
>> @@ -153,6 +154,25 @@ static int omap_reset_deassert(struct reset_controller_dev *rcdev,
>> v &= ~(1 << id);
>> writel_relaxed(v, reset->prm->base + reset->prm->data->rstctrl);
>>
>> + if (!has_rstst)
>> + return 0;
>> +
>> + /* wait for the status to be set */
>> + while (1) {
>> + v = readl_relaxed(reset->prm->base + reset->prm->data->rstst);
>> + v &= 1 << st_bit;
>> + if (v)
>> + break;
>> + timeout++;
>> + if (timeout > OMAP_RESET_MAX_WAIT) {
>> + pr_err("%s: timedout waiting for %s:%lu\n", __func__,
>> + dev_name(rcdev->dev), id);
>> + return -EBUSY;
>> + }
>> +
>> + udelay(1);
>> + }
>
> This looks like you could use
>
> readl_relaxed_poll_timeout(_atomic)
Yeah true, let me change that.
-Tero
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next prev parent reply other threads:[~2019-08-30 9:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 7:19 [PATCHv2 00/11] soc: ti: add OMAP PRM driver (for reset) Tero Kristo
2019-08-28 7:19 ` [PATCHv2 01/11] dt-bindings: omap: add new binding for PRM instances Tero Kristo
2019-08-30 9:18 ` Tero Kristo
2019-08-28 7:19 ` [PATCHv2 02/11] soc: ti: add initial PRM driver with reset control support Tero Kristo
2019-08-29 13:12 ` Philipp Zabel
2019-08-30 7:28 ` Tero Kristo
2019-08-30 9:02 ` Philipp Zabel
2019-08-30 9:11 ` Tero Kristo
2019-08-28 7:19 ` [PATCHv2 03/11] soc: ti: omap-prm: poll for reset complete during de-assert Tero Kristo
2019-08-29 13:14 ` Philipp Zabel
2019-08-30 9:07 ` Tero Kristo [this message]
2019-08-28 7:19 ` [PATCHv2 04/11] soc: ti: omap-prm: add support for denying idle for reset clockdomain Tero Kristo
2019-08-28 7:19 ` [PATCHv2 05/11] soc: ti: omap-prm: sync func clock status with resets Tero Kristo
2019-08-29 13:25 ` Philipp Zabel
2019-08-30 7:03 ` Tero Kristo
2019-08-28 7:19 ` [PATCHv2 06/11] soc: ti: omap-prm: support resets with no associated clockdomain Tero Kristo
2019-08-28 7:19 ` [PATCHv2 07/11] soc: ti: omap-prm: add omap4 PRM data Tero Kristo
2019-08-28 7:19 ` [PATCHv2 08/11] soc: ti: omap-prm: add data for am33xx Tero Kristo
2019-08-28 7:19 ` [PATCHv2 09/11] soc: ti: omap-prm: add dra7 PRM data Tero Kristo
2019-08-28 7:19 ` [PATCHv2 10/11] soc: ti: omap-prm: add am4 " Tero Kristo
2019-08-28 7:19 ` [PATCHv2 11/11] soc: ti: omap-prm: add omap5 " Tero Kristo
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=ceed701f-481c-4905-727e-ba3af2cf8ff2@ti.com \
--to=t-kristo@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=tony@atomide.com \
/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