linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	linux-renesas-soc@vger.kernel.org
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: mfd: Add Renesas R2A11302FT PMIC
Date: Fri, 10 Oct 2025 04:37:14 +0200	[thread overview]
Message-ID: <08b7a21a-72f7-47e4-9dc9-37a7316f94d5@kernel.org> (raw)
In-Reply-To: <20251009181916.2431-2-wsa+renesas@sang-engineering.com>

On 09/10/2025 20:12, Wolfram Sang wrote:
> This PMIC is referenced in upstream DTs for the Renesas Lager and
> Koelsch boards. Sadly, we don't have documentation for more complete
> bindings, but due to the spi-cpol/cpha it also doesn't belong to trivial

That's not a problem.

> devices. So, start with this minimal binding description with the facts
> that we do know:
> 
> Fixes:
> arch/arm/boot/dts/renesas/r8a7790-lager.dtb: /soc/spi@e6e10000/pmic@0: failed to match any schema with compatible: ['renesas,r2a11302ft']
> arch/arm/boot/dts/renesas/r8a7791-koelsch.dtb: /soc/spi@e6e20000/pmic@0: failed to match any schema with compatible: ['renesas,r2a11302ft']
> 
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
> 
> Change since RFC [1]:

Please start using b4. This is v2. Your wrong numbering makes any
comparisons broken. Try yourself with b4.

> * dropped "unevaluatedProperties" because we know this binding is not
>   complete currently

You cannot. Bindings must be complete (or complete "enough"), otherwise
I see no point in accepting them.

It is like you sent driver code which does not build because you did not
write half of it. Why would we want it?


> * removed 'pmic' label from the example
> * proper patch description
> 
> [1] https://lore.kernel.org/r/20250929083449.14393-1-wsa+renesas@sang-engineering.com
> 
>  .../bindings/mfd/renesas,r2a11302ft.yaml      | 49 +++++++++++++++++++
>  1 file changed, 49 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/mfd/renesas,r2a11302ft.yaml
> 
> diff --git a/Documentation/devicetree/bindings/mfd/renesas,r2a11302ft.yaml b/Documentation/devicetree/bindings/mfd/renesas,r2a11302ft.yaml
> new file mode 100644
> index 000000000000..e978b359b3ec
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mfd/renesas,r2a11302ft.yaml
> @@ -0,0 +1,49 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mfd/renesas,r2a11302ft.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Renesas R2A11302FT Power Supply ICs for R-Car
> +
> +maintainers:
> +  - Wolfram Sang <wsa+renesas@sang-engineering.com>
> +
> +properties:
> +  compatible:
> +    const: renesas,r2a11302ft
> +
> +  reg:
> +    maxItems: 1
> +
> +  spi-max-frequency:
> +    maximum: 6000000
> +
> +  spi-cpol: true
> +
> +  spi-cpha: true
> +
> +required:
> +  - compatible
> +  - reg
> +  - spi-cpol
> +  - spi-cpha
> +
> +allOf:
> +  - $ref: /schemas/spi/spi-peripheral-props.yaml#
> +

Missing unevaluatedProps. See writing schema (and any of my talks).

> +examples:
> +  - |
> +    spi {
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +
> +        pmic@0 {
> +                compatible = "renesas,r2a11302ft";

Messed indentation.


Best regards,
Krzysztof

  reply	other threads:[~2025-10-10  2:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-09 18:12 [PATCH] dt-bindings: mfd: Add Renesas R2A11302FT PMIC Wolfram Sang
2025-10-10  2:37 ` Krzysztof Kozlowski [this message]
2025-10-10  7:58   ` Wolfram Sang
2025-10-10  8:04     ` Krzysztof Kozlowski
2025-10-10  8:19       ` Wolfram Sang
2025-10-10  8:22         ` Krzysztof Kozlowski

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=08b7a21a-72f7-47e4-9dc9-37a7316f94d5@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=robh@kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    /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).