From: Krzysztof Kozlowski <krzk@kernel.org>
To: Shenwei Wang <shenwei.wang@nxp.com>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: "imx@lists.linux.dev" <imx@lists.linux.dev>,
dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH] reset: gpio: Add self-deasserting reset callback
Date: Fri, 31 Jan 2025 16:10:26 +0100 [thread overview]
Message-ID: <40676b09-82bf-48b5-9a06-3057cd595815@kernel.org> (raw)
In-Reply-To: <PAXPR04MB91858A6F0917109DFF33110B89E82@PAXPR04MB9185.eurprd04.prod.outlook.com>
On 31/01/2025 15:58, Shenwei Wang wrote:
>>> +#include <linux/delay.h>
>>> #include <linux/gpio/consumer.h>
>>> #include <linux/mod_devicetable.h>
>>> #include <linux/module.h>
>>> @@ -37,6 +38,17 @@ static int reset_gpio_deassert(struct
>> reset_controller_dev *rc,
>>> return 0;
>>> }
>>>
>>> +static int reset_gpio_reset(struct reset_controller_dev *rc, unsigned
>>> +long id) {
>>> + struct reset_gpio_priv *priv = rc_to_reset_gpio(rc);
>>> +
>>> + gpiod_set_value_cansleep(priv->reset, 1);
>>> + usleep_range(10, 20);
>>
>>
>> No, because this is some arbitrary value which might or might not work.
>> If this gets accepted, next person will change it to their own need.
>> Then next person will revert previous change... and so on.
>>
>
> If the arbitrary value is a concern, would moving it to the DTS be an appropriate solution?
> This may give the user more flexible.
Sure, as discussed when this series were upstreamed and as discussed
with Sean's patchset. BTW, Sean's mentioned need to revive his work, but
I think it did not materialize.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-31 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 21:53 [PATCH] reset: gpio: Add self-deasserting reset callback Shenwei Wang
2025-01-31 7:17 ` Krzysztof Kozlowski
2025-01-31 14:58 ` Shenwei Wang
2025-01-31 15:10 ` Krzysztof Kozlowski [this message]
2025-01-31 15:23 ` Shenwei Wang
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=40676b09-82bf-48b5-9a06-3057cd595815@kernel.org \
--to=krzk@kernel.org \
--cc=imx@lists.linux.dev \
--cc=linux-imx@nxp.com \
--cc=p.zabel@pengutronix.de \
--cc=shenwei.wang@nxp.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