From: Hermes Zhang <chenhuiz@axis.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Sebastian Reichel <sre@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andrew Davis <afd@ti.com>
Cc: <kernel@axis.com>, <linux-pm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: power: supply: bq256xx: Add ts-ignore property
Date: Fri, 10 Mar 2023 11:48:45 +0800 [thread overview]
Message-ID: <b2ac2d1f-3e9b-f96d-3724-020f7140b05f@axis.com> (raw)
In-Reply-To: <49e67fb3-4ef9-5d50-c3e8-3c7857145bbc@linaro.org>
On 2023/3/9 18:12, Krzysztof Kozlowski wrote:
> On 09/03/2023 03:39, Hermes Zhang wrote:
>> Add a new property: ts-ignore to allow user to enable the TS_IGNORE flag
>> in chip. Ignore TS pin will allow user to control the charging
>> parameters instead of the default JEITA profile in chip.
> You miss users of it.
Could you give some more info about what I missed?
> @@ -68,6 +68,12 @@ properties:
> Interrupt sends an active low, 256 μs pulse to host to report the charger
> device status and faults.
>
> + ts-ignore:
> Missing vendor prefix... is this generic property? ts-ignore is very
> cryptic. You should describe here rather desired system characteristic.
> Why anyone would need to use it per-board level?
OK, I will fix it. Will "ti,ignore-ts-pin" be better? Yes, it's a
generic. To disable the TS pin, actually we also could do it from HW,
but from software, it could be more flexble. But if HW already disable
it, then you don't need to do it again from dts.
BTW, I find I may miss some information here: the ts-ignore feature is
not support by all the chips list here, I will add some comment for
which chip support it.
Best Regards,
Hermes
next prev parent reply other threads:[~2023-03-10 3:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 2:39 Hermes Zhang
2023-03-09 10:12 ` Krzysztof Kozlowski
2023-03-10 3:48 ` Hermes Zhang [this message]
2023-03-10 8:06 ` 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=b2ac2d1f-3e9b-f96d-3724-020f7140b05f@axis.com \
--to=chenhuiz@axis.com \
--cc=afd@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@axis.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--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®