From: Esben Haabendal <esben@geanix.com>
To: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
Cc: "Krzysztof Kozlowski" <krzk@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Hans de Goede" <hdegoede@redhat.com>,
<linux-input@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: input: touchscreen: goodix: Add no-reset-pull-up property
Date: Tue, 29 Apr 2025 16:11:48 +0200 [thread overview]
Message-ID: <87wmb3t5uj.fsf@geanix.com> (raw)
In-Reply-To: <23onpttl3w2wo3625c7flbljahojipsb4xznrx6xynr7rrzofr@2bcvjji7dpu6> (Dmitry Torokhov's message of "Mon, 28 Apr 2025 12:30:47 -0700")
"Dmitry Torokhov" <dmitry.torokhov@gmail.com> writes:
> On Mon, Apr 28, 2025 at 07:58:55AM +0000, Esben Haabendal wrote:
>> On Monday, April 28th, 2025 at 09:48, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>> > On Tue, Apr 22, 2025 at 05:15:02PM GMT, Esben Haabendal wrote:
>> >
>> > > This should be added for boards where there is no pull-up on the reset pin,
>> > > as the driver will otherwise switch the reset signal to high-impedance to
>> > > save power, which obviously not safe without pull-up.
>> > >
>> > > Signed-off-by: Esben Haabendal esben@geanix.com
>> > > ---
>> > > Documentation/devicetree/bindings/input/touchscreen/goodix.yaml | 4 ++++
>> > > 1 file changed, 4 insertions(+)
>> > >
>> > > diff --git a/Documentation/devicetree/bindings/input/touchscreen/goodix.yaml b/Documentation/devicetree/bindings/input/touchscreen/goodix.yaml
>> > > index eb4992f708b70fef93bd4b59b9565123f7c6ad5d..7e5c4b98f2cb1ef61798252ea5c573068a46d4aa 100644
>> > > --- a/Documentation/devicetree/bindings/input/touchscreen/goodix.yaml
>> > > +++ b/Documentation/devicetree/bindings/input/touchscreen/goodix.yaml
>> > > @@ -45,6 +45,10 @@ properties:
>> > > reset-gpios:
>> > > maxItems: 1
>> > >
>> > > + no-reset-pull-up:
>> >
>> > Is this common property? Where is it defined? Otherwise missing vendor
>> > prefix.
>>
>> Good question. When is something a common property?
>>
>> The idea of marking something as not having a pull-up on the reset pin could be considered a common thing I guess.
>> But for now, I am defining it for the goodix driver only, as I am only aware of these devices needing to handle it in a special way.
>>
>> Should I rename it to goodix,no-reset-pull-up?
>
> We already have GPIO_PULL_UP/GPIO_PULL_DOWN flags available in GPIO
> bindings. So maybe the correct way is to have the driver rely on them
> and only leave the reset line in high-impedance mode if GPIO tells it
> that there is a pull-up?
As I understand GPIO_PULL_UP/GPIO_PULL_DOWN flags in bindings, they
indicate that pull-up/pull-down is to be configured for the gpio.
This is different to what I am expressing with goodix,no-reset-pull-up,
as I am expressing the lack of external pull-up on the signal. Without
that, the goodix driver assumes that an external pull-up is mounted, and
that the gpio pin can be set to high impedance, and the external pull-up
will ensure that it stays high.
How do you propose that we can use GPIO_PULL_UP/GPIO_PULL_DOWN flags for
this purpose?
/Esben
next prev parent reply other threads:[~2025-04-29 14:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 15:15 [PATCH 0/2] input: touch: goodix: Extend reset pull-up fix to DT platforms Esben Haabendal
2025-04-22 15:15 ` [PATCH 1/2] dt-bindings: input: touchscreen: goodix: Add no-reset-pull-up property Esben Haabendal
2025-04-28 7:45 ` Krzysztof Kozlowski
2025-04-28 7:58 ` Esben Haabendal
2025-04-28 19:30 ` Dmitry Torokhov
2025-04-29 14:11 ` Esben Haabendal [this message]
2025-04-29 6:11 ` Krzysztof Kozlowski
2025-04-29 9:18 ` Esben Haabendal
2025-04-22 15:15 ` [PATCH 2/2] Input: goodix - Allow DT specification of missing reset pull-up Esben Haabendal
2025-04-28 8:33 ` Hans de Goede
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=87wmb3t5uj.fsf@geanix.com \
--to=esben@geanix.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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.