public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jon Hunter <jonathanh@nvidia.com>,
	Rajesh Gumasta <rgumasta@nvidia.com>,
	krzk+dt@kernel.org, robh@kernel.org, conor+dt@kernel.org,
	andi.shyti@kernel.org, ulf.hansson@linaro.org,
	thierry.reding@gmail.com, kyarlagadda@nvidia.com
Cc: devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-i2c@vger.kernel.org, linux-mmc@vger.kernel.org,
	andersson@kernel.org, sjg@chromium.org, nm@ti.com
Subject: Re: [PATCH V3 1/3] dt-binding: Add register-settings binding
Date: Tue, 29 Jul 2025 11:28:43 +0200	[thread overview]
Message-ID: <a6268cd4-4a7e-498e-9787-bec959bb1475@kernel.org> (raw)
In-Reply-To: <dc4ed9fd-2da1-4d9b-b8f1-446ea0697385@nvidia.com>

On 29/07/2025 11:15, Jon Hunter wrote:
> 
> On 25/07/2025 07:47, Krzysztof Kozlowski wrote:
>> On 25/07/2025 07:22, Rajesh Gumasta wrote:
>>> +description: |
>>> +  Register Settings provides a generic way to specify register configurations
>>> +  for any hardware controllers. Settings are specified under a "reg-settings"
>>> +  sub-node under the controller device tree node. It allows defining both
>>> +  default and operating mode specific register settings in the device tree.
>>> +
>>> +properties:
>>> +  reg-settings:
>>> +    type: object
>>> +    description: |
>>> +      Container node for register settings configurations. Each child node
>>> +      represents a specific configuration mode or operating condition.
>>> +
>>> +    additionalProperties:
>>> +      type: object
>>
>> I don't understand what does this binding bring. It is empty.
> 
> 
> Yes this is very much similar to the pinctrl.yaml that defines a 
> top-level object that can then be used by different devices and those 

No, it is not similar. pinctrl.yaml defines common properties and common
schema for class of devices - pin controllers.

There is nothing common here, nothing defined except that you have
unspecified children nodes.

> devices can then define the properties they need. So the examples for 
> I2C and MMC really demonstrate how this would be used in the subsequent 
> patches. Obviously we are open to any ideas on how if there are better 
> or preferred ways to do this.

I don't see this part addressing comments from Rob - you need more users
of this. Adding fake (empty, no-op) common schema is not solving it.

Best regards,
Krzysztof

  reply	other threads:[~2025-07-29  9:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-25  5:22 [PATCH V3 0/3] Introduce a generic register settings dt-binding Rajesh Gumasta
2025-07-25  5:22 ` [PATCH V3 1/3] dt-binding: Add register-settings binding Rajesh Gumasta
2025-07-25  6:47   ` Krzysztof Kozlowski
2025-07-29  9:15     ` Jon Hunter
2025-07-29  9:28       ` Krzysztof Kozlowski [this message]
2025-07-29 14:05         ` Thierry Reding
2025-09-05 10:36           ` Jon Hunter
2025-09-29  4:39   ` Chintan Vankar
2025-09-30 15:01     ` Jon Hunter
2025-10-09 10:15       ` Jon Hunter
2025-10-09 16:33       ` Rob Herring
2025-10-14 14:30         ` Jon Hunter
2025-07-25  5:22 ` [PATCH V3 2/3] dt-binding: i2c: nvidia,tegra20-i2c: Add register-setting support Rajesh Gumasta
2025-07-25  7:40   ` Rob Herring (Arm)
2025-07-25  9:20     ` Jon Hunter
2025-07-25  5:22 ` [PATCH V3 3/3] dt-binding: mmc: tegra: " Rajesh Gumasta
2025-07-25  6:48 ` [PATCH V3 0/3] Introduce a generic register settings dt-binding Krzysztof Kozlowski
2025-07-25  9:13   ` Jon Hunter

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=a6268cd4-4a7e-498e-9787-bec959bb1475@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=kyarlagadda@nvidia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=rgumasta@nvidia.com \
    --cc=robh@kernel.org \
    --cc=sjg@chromium.org \
    --cc=thierry.reding@gmail.com \
    --cc=ulf.hansson@linaro.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