Devicetree
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Herman van Hazendonk <github.com@herrie.org>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	devicetree@vger.kernel.org,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Sebastian Reichel <sre@kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: power: supply: maxim,max8903: add DC and USB input current-limit controls
Date: Fri, 12 Jun 2026 11:15:04 -0500	[thread overview]
Message-ID: <178128090443.1145552.3235840430356467114.robh@kernel.org> (raw)
In-Reply-To: <20260605-submit-power-max8903-dc-limit-v2-1-0c5396e98f14@herrie.org>


On Fri, 05 Jun 2026 11:18:12 +0200, Herman van Hazendonk wrote:
> Add three optional properties to the MAX8903 charger binding to
> describe board-level GPIO control of the DC and USB input current
> limits:
> 
> DC input (TA / DOK pin):
>   - dc-current-limit-gpios (1..4 GPIOs): mux control lines feeding
>     the MAX8903 IDC resistor mux;
>   - dc-current-limit-mapping (uint32-matrix of {microamps,
>     gpio_bit_pattern} pairs): the available current levels and the
>     GPIO bit pattern that selects each level.
> 
> USB input (USB / UOK pin):
>   - usb-current-limit-gpios: a single GPIO driving the IUSB pin.
>     The IUSB pin is silicon-fixed by the MAX8903 datasheet (Pin
>     Description): low selects 100 mA, high selects 500 mA. Only
>     the GPIO mapping is board-specific; the current values are
>     not exposed in DT.
> 
> A dependentRequired block ties dc-current-limit-gpios and
> dc-current-limit-mapping together so an incomplete DT cannot pass
> validation with only one half of the pair.
> 
> These let userspace clamp the input draw via the standard
> POWER_SUPPLY_PROP_INPUT_CURRENT_LIMIT power_supply attribute. The HP
> TouchPad uses both: two TLMM lines select between 0.5 A, 1.0 A,
> 1.5 A and 2.0 A DC input current limits behind the MAX8903B
> charger, and a third TLMM line picks the IUSB 100 mA / 500 mA
> limit.
> 
> These are purely additive; existing platforms remain unaffected.
> 
> Signed-off-by: Herman van Hazendonk <github.com@herrie.org>
> ---
>  .../bindings/power/supply/maxim,max8903.yaml       | 53 ++++++++++++++++++++++
>  1 file changed, 53 insertions(+)
> 

Reviewed-by: Rob Herring (Arm) <robh@kernel.org>


  reply	other threads:[~2026-06-12 16:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-05  9:18 [PATCH v2 0/2] power: supply: max8903: add DC and USB input current-limit GPIO controls Herman van Hazendonk via B4 Relay
2026-06-05  9:18 ` [PATCH v2 1/2] dt-bindings: power: supply: maxim,max8903: add DC and USB input current-limit controls Herman van Hazendonk via B4 Relay
2026-06-12 16:15   ` Rob Herring (Arm) [this message]
2026-06-05  9:18 ` [PATCH v2 2/2] power: supply: max8903: add DC and USB input current-limit GPIO controls Herman van Hazendonk via B4 Relay

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=178128090443.1145552.3235840430356467114.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=github.com@herrie.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.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