From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jhon Wilker Rodrigues Aquino <jhonwilker0112@gmail.com>,
Richard Leitner <richard.leitner@linux.dev>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jhon Wilker Rodrigues Aquino <jhon.aquino@autotrac.com.br>
Subject: Re: [PATCH v2 1/2] dt-bindings: usb: microchip,usb251xb: add battery-charging-enable property
Date: Tue, 3 Nov 2026 21:52:54 +0100 [thread overview]
Message-ID: <ef4145a5-5732-4f1b-9d72-586e75d5e2cd@kernel.org> (raw)
In-Reply-To: <20261103200154.125681-2-jhonwilker0112@gmail.com>
On 03/11/2026 21:01, Jhon Wilker Rodrigues Aquino wrote:
> From: Jhon Wilker Rodrigues Aquino <jhon.aquino@autotrac.com.br>
Do not attach (thread) your patchsets to some other threads (unrelated
or older versions). This buries them deep in the mailbox and might
interfere with applying entire sets. See also:
https://elixir.bootlin.com/linux/v6.16-rc2/source/Documentation/process/submitting-patches.rst#L830
>
> Describe the battery-charging-enable property as a list of downstream ports in the USB251x device tree binding.
Please wrap commit message according to Linux coding style / submission
process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
Please run scripts/checkpatch.pl on the patches and fix reported
warnings. After that, run also 'scripts/checkpatch.pl --strict' on the
patches and (probably) fix more warnings. Some warnings can be ignored,
especially from --strict run, but the code here looks like it needs a
fix. Feel free to get in touch if the warning is not clear.
>
> Add an example that enables charging on ports 1 and 2.
>
> Signed-off-by: Jhon Wilker Rodrigues Aquino <jhon.aquino@autotrac.com.br>
> ---
> Documentation/devicetree/bindings/usb/usb251xb.yaml | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/usb/usb251xb.yaml b/Documentation/devicetree/bindings/usb/usb251xb.yaml
> index 0329a6aaaa928..0eb3035553c37 100644
> --- a/Documentation/devicetree/bindings/usb/usb251xb.yaml
> +++ b/Documentation/devicetree/bindings/usb/usb251xb.yaml
> @@ -230,6 +230,12 @@ properties:
> Specifies the time it takes from the time the host initiates the
> power-on sequence to a port until the port has adequate power.
>
> + battery-charging-enable:
Custom properties needs prefix, see writing bindings.
> + $ref: /schemas/types.yaml#/definitions/uint32-array
> + description: |
Do not need '|' unless you need to preserve formatting.
> + Specifies the downstream ports which will have battery charging enabled.
> + Battery charging is disabled on all ports by default.
Why wouldn't you enable charging on all ports? You have entire
description (and/or commit msg) to explain why you are doing this and
why this is exactly hardware property.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-11-03 20:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 18:55 [PATCH 0/2] usb: misc: usb251xb: add DT battery charging configuration Jhon Wilker Rodrigues Aquino
2026-11-03 18:55 ` [PATCH 1/2] dt-bindings: usb: microchip,usb251xb: add battery-charging-enable property Jhon Wilker Rodrigues Aquino
2026-11-03 18:55 ` [PATCH 2/2] usb: misc: usb251xb: configure battery charging from DT Jhon Wilker Rodrigues Aquino
2026-11-03 19:03 ` sashiko-bot
2026-11-03 20:01 ` [PATCH v2 0/2] usb: misc: usb251xb: add DT battery charging configuration Jhon Wilker Rodrigues Aquino
2026-11-03 20:01 ` [PATCH v2 1/2] dt-bindings: usb: microchip,usb251xb: add battery-charging-enable property Jhon Wilker Rodrigues Aquino
2026-11-03 20:52 ` Krzysztof Kozlowski [this message]
2026-11-03 20:01 ` [PATCH v2 2/2] usb: misc: usb251xb: configure battery charging from DT Jhon Wilker Rodrigues Aquino
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=ef4145a5-5732-4f1b-9d72-586e75d5e2cd@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jhon.aquino@autotrac.com.br \
--cc=jhonwilker0112@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=richard.leitner@linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox