From: Krzysztof Kozlowski <krzk@kernel.org>
To: Gregory Fuchedgi <gfuchedgi@gmail.com>
Cc: Robert Marko <robert.marko@sartura.hr>,
Luka Perkov <luka.perkov@sartura.hr>,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Jonathan Corbet <corbet@lwn.net>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-hwmon@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/2] dt-bindings: hwmon: update TI TPS23861 bindings with per-port schema
Date: Sun, 17 Aug 2025 09:23:09 +0200 [thread overview]
Message-ID: <ff167728-a4a7-4f7d-a809-d0e482ab7dd6@kernel.org> (raw)
In-Reply-To: <CAAcybusHjAR67N0rumb6M_uG1ct3aa=zv2XkpUjhSSxv0NdzFA@mail.gmail.com>
On 13/08/2025 05:00, Gregory Fuchedgi wrote:
> On Tue, Aug 12, 2025 at 12:20 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>> + shutdown-gpios:
>> powerdown-gpios, see gpio-consumer-common.yaml
> It is called shutdown in the datasheet, but seems like neither powerdown nor
> shutdown truly reflects its purpose. This pin doesn't power down the controller
> itself. It shuts down the ports while keeping the controller available for
> configuration over i2c. Should I call it ti,ports-shutdown-gpios or maybe
> ti,shutdown-gpios? Any other suggestions?
Feels more like enable-gpios.
>
>>> +patternProperties:
>>> + "^port@[0-3]$":
>> This goes to ports property.
> Do you mean I should add another DT node that groups all ports? such as:
> compatible = "ti,tps23861"; ports { port@0 {...} port@1 {...} }
Yes.
>
> If that's the case would it make sense to use "^.*$" pattern to allow any name
> and drop the port label? Is patternProperties even needed in this case?
You should use standard graph bindings, so:
git grep 'ref' -- Documentation/devicetree/bindings/ | grep ports
>
>>> + tps23861@28 {
>> Node names should be generic. See also an explanation and list of
> Ack. Should I also fix the existing example in this patch?
You can, up to you.
>
>>> + label = "my_poe_controller";
>> Use useful names or just drop it.
> I thought this is good as an example? A useful name would be board specific.
Then it should be board specific. You add here real and the most
complete example.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-17 7:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 16:13 [PATCH v2 0/2] hwmon: (tps23861) add class restrictions and semi-auto mode support Gregory Fuchedgi
2025-08-11 16:13 ` Gregory Fuchedgi via B4 Relay
2025-08-11 16:13 ` [PATCH v2 1/2] " Gregory Fuchedgi
2025-08-11 16:13 ` Gregory Fuchedgi via B4 Relay
2025-08-11 16:13 ` [PATCH v2 2/2] dt-bindings: hwmon: update TI TPS23861 bindings with per-port schema Gregory Fuchedgi
2025-08-11 16:13 ` Gregory Fuchedgi via B4 Relay
2025-08-12 7:20 ` Krzysztof Kozlowski
2025-08-13 3:00 ` Gregory Fuchedgi
2025-08-17 7:23 ` Krzysztof Kozlowski [this message]
2025-08-18 17:31 ` Rob Herring
2025-08-19 17:50 ` Gregory Fuchedgi
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=ff167728-a4a7-4f7d-a809-d0e482ab7dd6@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=gfuchedgi@gmail.com \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=luka.perkov@sartura.hr \
--cc=robert.marko@sartura.hr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.