From: Rob Herring <robh@kernel.org>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: lee@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
mazziesaccount@gmail.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, sre@kernel.org
Subject: Re: [PATCH] dt-bindings: mfd: bd71828: Use charger resistor in mOhm instead of MOhm
Date: Fri, 1 Nov 2024 14:27:05 -0500 [thread overview]
Message-ID: <20241101192705.GA4062121-robh@kernel.org> (raw)
In-Reply-To: <20241029111112.33386-1-andreas@kemnade.info>
On Tue, Oct 29, 2024 at 12:11:12PM +0100, Andreas Kemnade wrote:
> Apparently there was some confusion regarding milliohm vs. megaohm.
> (m/M). Use microohms to be able to properly specify the charger
> resistor like other drivers do. This is not used yet by mainline code
> yet. Specify a current sense resistor in milliohms range rathes then
> megaohms range in the examples.
milliohms?
rathes?
>
> CC: sre@kernel.org
> Reported-by: Matti Vaittinen <mazziesaccount@gmail.com>
> Closes: https://lore.kernel.org/imx/6dcd724a-a55c-4cba-a45b-21e76b1973b0@gmail.com/T/#mf590875a9f4d3955cd1041d7196ff0c65c0a7e9d
> Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
> ---
> .../devicetree/bindings/mfd/rohm,bd71828-pmic.yaml | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
Looks like rohm,bd71815-pmic.yaml has the same problem.
>
> diff --git a/Documentation/devicetree/bindings/mfd/rohm,bd71828-pmic.yaml b/Documentation/devicetree/bindings/mfd/rohm,bd71828-pmic.yaml
> index fa17686a64f7..09e7d68e92bf 100644
> --- a/Documentation/devicetree/bindings/mfd/rohm,bd71828-pmic.yaml
> +++ b/Documentation/devicetree/bindings/mfd/rohm,bd71828-pmic.yaml
> @@ -55,14 +55,15 @@ properties:
> minimum: 0
> maximum: 1
>
> - rohm,charger-sense-resistor-ohms:
> - minimum: 10000000
> - maximum: 50000000
> + rohm,charger-sense-resistor-micro-ohms:
> + minimum: 10000
> + maximum: 50000
> + default: 30000
> description: |
> BD71827 and BD71828 have SAR ADC for measuring charging currents.
> External sense resistor (RSENSE in data sheet) should be used. If some
> - other but 30MOhm resistor is used the resistance value should be given
> - here in Ohms.
> + other but 30mOhm resistor is used the resistance value should be given
> + here in microohms.
>
> regulators:
> $ref: /schemas/regulator/rohm,bd71828-regulator.yaml
> @@ -114,7 +115,7 @@ examples:
> #gpio-cells = <2>;
> gpio-reserved-ranges = <0 1>, <2 1>;
>
> - rohm,charger-sense-resistor-ohms = <10000000>;
> + rohm,charger-sense-resistor-micro-ohms = <10000>;
>
> regulators {
> buck1: BUCK1 {
> --
> 2.39.5
>
next prev parent reply other threads:[~2024-11-01 19:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 11:11 [PATCH] dt-bindings: mfd: bd71828: Use charger resistor in mOhm instead of MOhm Andreas Kemnade
2024-10-29 13:00 ` Matti Vaittinen
2024-11-01 19:27 ` Rob Herring [this message]
2024-11-04 6:06 ` Matti Vaittinen
2024-11-11 10:31 ` Andreas Kemnade
2024-11-12 5:42 ` Matti Vaittinen
2024-11-04 9:00 ` Andreas Kemnade
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=20241101192705.GA4062121-robh@kernel.org \
--to=robh@kernel.org \
--cc=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.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;
as well as URLs for NNTP newsgroup(s).