From: andy.shevchenko@gmail.com
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
Marek Vasut <marex@denx.de>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH v1 0/3] gpio: Add gpio-delay support
Date: Fri, 7 Apr 2023 21:57:32 +0300 [thread overview]
Message-ID: <ZDBnnKy7QF0KZuZd@surfacebook> (raw)
In-Reply-To: <20230406093344.917259-1-alexander.stein@ew.tq-group.com>
Thu, Apr 06, 2023 at 11:33:41AM +0200, Alexander Stein kirjoitti:
> Hello everyone,
>
> thanks for the feedback I've received. This is the first non-RFC series for
> adressing a platform specific ramp-up/ramp-down delay on GPIO outputs.
>
> Changes compared to RFC v2 are mentioned in each patch.
Reading the (poor?) documentation does not clarify the use case.
Looking at them I think that this is can be implemented as debounce.
Also I have no clue why it's so important that we _need_ to have a
driver for this. We have plenty of consumer drivers that implement
delays on ramping up or down or whatever if they need.
Which part(s) did I got wrong?
P.S. Are we going to have a _driver_ per each subtle feature like this?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-04-07 19:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 9:33 [PATCH v1 0/3] gpio: Add gpio-delay support Alexander Stein
2023-04-06 9:33 ` [PATCH v1 1/3] dt-bindings: gpio: Add gpio-delay binding document Alexander Stein
2023-05-31 16:37 ` Krzysztof Kozlowski
2023-06-02 16:29 ` Bartosz Golaszewski
2023-04-06 9:33 ` [PATCH v1 2/3] gpio: Add gpio delay driver Alexander Stein
2023-06-02 16:31 ` Bartosz Golaszewski
2023-04-06 9:33 ` [PATCH v1 3/3] [DNI] arm64: dts: mba8mx: Use gpio-delay for LVDS bridge Alexander Stein
2023-04-07 18:57 ` andy.shevchenko [this message]
2023-04-11 7:19 ` [PATCH v1 0/3] gpio: Add gpio-delay support Alexander Stein
2023-04-11 9:34 ` Andy Shevchenko
2023-04-14 6:37 ` Alexander Stein
2023-04-15 15:06 ` Andy Shevchenko
2023-04-16 7:42 ` Krzysztof Kozlowski
2023-04-16 9:36 ` Andy Shevchenko
2023-04-16 11:04 ` Krzysztof Kozlowski
2023-04-16 11:14 ` Andy Shevchenko
2023-04-16 11:21 ` Krzysztof Kozlowski
2023-04-16 11:33 ` Andy Shevchenko
2023-04-16 11:42 ` Krzysztof Kozlowski
2023-04-16 18:46 ` Andy Shevchenko
2023-05-31 6:53 ` Alexander Stein
2023-05-31 12:02 ` Andy Shevchenko
2023-05-31 13:44 ` Linus Walleij
2023-05-31 14:37 ` Andy Shevchenko
2023-05-31 16:37 ` Krzysztof Kozlowski
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=ZDBnnKy7QF0KZuZd@surfacebook \
--to=andy.shevchenko@gmail.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=marex@denx.de \
--cc=robh+dt@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.