From: Krzysztof Kozlowski <krzk@kernel.org>
To: Stefan Raufhake <raufhakestefan@gmail.com>,
sebastian.reichel@collabora.com
Cc: sre@kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
s.raufhake@beckhoff.com, s.dirkwinkel@beckhoff.com,
s.raufhake@beckhoff.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Subject: Re: [PATCH v2 1/1] power: supply: gpio-charger: Support to disable charger
Date: Fri, 3 Jan 2025 10:08:51 +0100 [thread overview]
Message-ID: <dd4a1d34-4266-43de-9a41-4b7b247d3226@kernel.org> (raw)
In-Reply-To: <20250103081836.4499-1-raufhakestefan@gmail.com>
On 03/01/2025 09:18, Stefan Raufhake wrote:
>>> to be bad. Please suggest better wording :)
>
> Which part of the documentation is being referred to: the binding, the commit message, or another section?
> Once clarified, I can suggest a better wording in this part of the documentation.
>
>>> P.S.: binding and driver should be send in separate patches.
>>
>
> In the next version, I will split the binding and driver into two separate patches.
>
>> Yeah, still all my comments should be addressed.
>>
>
> Krzysztof, in the bindings for 'gpio-charger.yaml' (Documentation/devicetree/bindings/power/supply/gpio-charger.yaml),
> is the property name 'enable-gpios' suitable for you, or should I rename it?
> If a rename is needed, which name makes the most sense to you for this function?
enable-gpios is correct, assuming these is a different GPIO than one
used for "charge-current-limit-gpios" for value of 0, as pointed out by
Sebastian.
Existing example DTS in the binding clearly defines A.11 as
enable-gpios. Maybe that's just coincidence, but I wonder how it would
work for three gpios?
Anyway the example should be then fixed to reflect real intention, e.g.
add enable-gpios and change "<0 0x02>; // 0 mA => GPIO A.11 high" into
some value like 300 mA.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-01-03 9:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 9:23 [PATCH v2 0/1] " Stefan Raufhake
2024-12-10 9:23 ` [PATCH v2 1/1] " Stefan Raufhake
2024-12-11 9:30 ` Krzysztof Kozlowski
2024-12-13 10:28 ` Stefan Raufhake
2024-12-16 7:30 ` Krzysztof Kozlowski
2024-12-19 0:58 ` Sebastian Reichel
2024-12-19 8:13 ` Krzysztof Kozlowski
2025-01-03 8:18 ` Stefan Raufhake
2025-01-03 9:08 ` Krzysztof Kozlowski [this message]
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=dd4a1d34-4266-43de-9a41-4b7b247d3226@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=raufhakestefan@gmail.com \
--cc=robh@kernel.org \
--cc=s.dirkwinkel@beckhoff.com \
--cc=s.raufhake@beckhoff.com \
--cc=s.raufhake@beckhoff.de \
--cc=sebastian.reichel@collabora.com \
--cc=sre@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®