Devicetree
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-renesas-soc@vger.kernel.org,
	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 09:58:29 +0200	[thread overview]
Message-ID: <aOi8pQuHfduf6-FX@shikoro> (raw)
In-Reply-To: <08b7a21a-72f7-47e4-9dc9-37a7316f94d5@kernel.org>

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

Hi Krzysztof,

thanks for the review!

On Fri, Oct 10, 2025 at 04:37:14AM +0200, Krzysztof Kozlowski wrote:
> 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.

It is not? I found this mail[1] saying that enabling spi-cpol et al.
will disable sanity checks for other trivial devices.

Adding this PMIC to trivial devices would be my fav solution, actually.

[1] https://www.spinics.net/lists//devicetree/msg731369.html

> > Change since RFC [1]:
> 
> Please start using b4. This is v2. Your wrong numbering makes any
> comparisons broken. Try yourself with b4.

I checked the link [1] I gave last mail and the mail said "[RFC PATCH]".
Looks correct to me, am I overlooking something? I am open to switching
to b4, but I need a time slot for that.

> > * 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.

I can see that.

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

I would agree if it does not build. But it does build. So, the proper
comparison for me is a limited driver which probes and gives access to
the device. Features can be implemented incrementally. This bindings
works/builds with the few information we have. It even removes a
warning.

My reasoning is that DT describes HW. And on the Renesas Lager board,
this PMIC *is* connected to the SPI controller. I am open to removing
this node because we don't have a driver. That would mean, though,
otherwise rare to find information is lost.

All the best,

   Wolfram


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

  reply	other threads:[~2025-10-10  7:58 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
2025-10-10  7:58   ` Wolfram Sang [this message]
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=aOi8pQuHfduf6-FX@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --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