All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: Lee Jones <lee.jones@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Sebastian Reichel <sre@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH v2 3/4] regulator: dt-bindings: maxim,max14577: convert to dtschema
Date: Mon, 14 Feb 2022 16:59:55 +0000	[thread overview]
Message-ID: <YgqKix0h7T9ME/ub@sirena.org.uk> (raw)
In-Reply-To: <79ecad6e-d9c9-c798-0933-43da4dff9dd6@canonical.com>

[-- Attachment #1: Type: text/plain, Size: 608 bytes --]

On Mon, Feb 14, 2022 at 05:54:01PM +0100, Krzysztof Kozlowski wrote:
> On 14/02/2022 17:43, Mark Brown wrote:

> >> +    required:
> >> +      - regulator-name

> > Why is regulator-name required?  While it's a good idea for users to
> > document names for supplies on their boards it shouldn't be a
> > requirement or something that a driver would care about.

> Indeed, there is no need for requiring the name. I guess I copied it
> from other schemas.

Those other schemas should be fixed as well, if this is required for
anything then there's a problem - this is purely diagnostic information
for users.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: Lee Jones <lee.jones@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Sebastian Reichel <sre@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH v2 3/4] regulator: dt-bindings: maxim,max14577: convert to dtschema
Date: Mon, 14 Feb 2022 16:59:55 +0000	[thread overview]
Message-ID: <YgqKix0h7T9ME/ub@sirena.org.uk> (raw)
In-Reply-To: <79ecad6e-d9c9-c798-0933-43da4dff9dd6@canonical.com>


[-- Attachment #1.1: Type: text/plain, Size: 608 bytes --]

On Mon, Feb 14, 2022 at 05:54:01PM +0100, Krzysztof Kozlowski wrote:
> On 14/02/2022 17:43, Mark Brown wrote:

> >> +    required:
> >> +      - regulator-name

> > Why is regulator-name required?  While it's a good idea for users to
> > document names for supplies on their boards it shouldn't be a
> > requirement or something that a driver would care about.

> Indeed, there is no need for requiring the name. I guess I copied it
> from other schemas.

Those other schemas should be fixed as well, if this is required for
anything then there's a problem - this is purely diagnostic information
for users.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-02-14 17:00 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11 17:43 [PATCH v2 0/4] mfd/power/regulators: dt-bindings: max14577: convert to dtschema Krzysztof Kozlowski
2022-01-11 17:43 ` Krzysztof Kozlowski
2022-01-11 17:43 ` [PATCH v2 1/4] ARM: dts: exynos: Align MAX77836 nodes with dtschema on Monk and Rinato Krzysztof Kozlowski
2022-01-11 17:43   ` Krzysztof Kozlowski
2022-01-23 17:10   ` (subset) " Krzysztof Kozlowski
2022-01-23 17:10     ` Krzysztof Kozlowski
2022-01-11 17:43 ` [PATCH v2 2/4] dt-bindings: power: supply: maxim,max14577: convert to dtschema Krzysztof Kozlowski
2022-01-11 17:43   ` [PATCH v2 2/4] dt-bindings: power: supply: maxim, max14577: " Krzysztof Kozlowski
2022-01-12 11:29   ` [PATCH v2 2/4] dt-bindings: power: supply: maxim,max14577: " Sebastian Reichel
2022-01-12 11:29     ` Sebastian Reichel
2022-02-14 14:17     ` Lee Jones
2022-02-14 14:17       ` Lee Jones
2022-02-14 16:37       ` Sebastian Reichel
2022-02-14 16:37         ` Sebastian Reichel
2022-01-11 17:43 ` [PATCH v2 3/4] regulator: dt-bindings: " Krzysztof Kozlowski
2022-01-11 17:43   ` [PATCH v2 3/4] regulator: dt-bindings: maxim, max14577: " Krzysztof Kozlowski
2022-01-11 22:21   ` [PATCH v2 3/4] regulator: dt-bindings: maxim,max14577: " Rob Herring
2022-01-11 22:21     ` Rob Herring
2022-02-14 16:43   ` Mark Brown
2022-02-14 16:43     ` Mark Brown
2022-02-14 16:54     ` Krzysztof Kozlowski
2022-02-14 16:54       ` [PATCH v2 3/4] regulator: dt-bindings: maxim, max14577: " Krzysztof Kozlowski
2022-02-14 16:59       ` Mark Brown [this message]
2022-02-14 16:59         ` [PATCH v2 3/4] regulator: dt-bindings: maxim,max14577: " Mark Brown
2022-01-11 17:43 ` [PATCH v2 4/4] dt-bindings: mfd: " Krzysztof Kozlowski
2022-01-11 17:43   ` Krzysztof Kozlowski
2022-02-06 17:39 ` [PATCH v2 0/4] mfd/power/regulators: dt-bindings: max14577: " Krzysztof Kozlowski
2022-02-06 17:39   ` Krzysztof Kozlowski
2022-02-07  9:34   ` Lee Jones
2022-02-07  9:34     ` Lee Jones
2022-02-07  9:43     ` Krzysztof Kozlowski
2022-02-07  9:43       ` Krzysztof Kozlowski
2022-02-07 10:11       ` Lee Jones
2022-02-07 10:11         ` Lee Jones

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=YgqKix0h7T9ME/ub@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-samsung-soc@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 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.