public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: 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, jonathanh@nvidia.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 0/3] Introduce a generic register settings dt-binding
Date: Fri, 25 Jul 2025 08:48:30 +0200	[thread overview]
Message-ID: <696774c5-db1c-4fcc-a5f6-139dc22ead87@kernel.org> (raw)
In-Reply-To: <20250725052225.23510-1-rgumasta@nvidia.com>

On 25/07/2025 07:22, Rajesh Gumasta wrote:
> 4. The I2C bindings are known to fail the binding checks if the fix for
>    the I2C schema is not applied [1].
> 5. The file i2c-controller-common.yaml is added as a place-holder for
>    defining the 'reg-settings' nodes for I2C controllers. However, this
>    is very much a place-holder for demostration purposes. Ideally, these
>    nodes would be part of the main I2C schema.
> 
> Changes in V3:
> - Renamed as 'generic register settings' as opposed to 'Tegra register
>   config settings'.
> - Dropped all the associated code to focus on the DT bindings for now.
> - Added a 'register-settings.yaml' as a top level binding.
> - Made I2C register-setting timing properties generic I2C properties.


Where are lore links to previous discussions? There is no v2 nor v1 in
inbox.

Best regards,
Krzysztof

  parent reply	other threads:[~2025-07-25  6:48 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
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 ` Krzysztof Kozlowski [this message]
2025-07-25  9:13   ` [PATCH V3 0/3] Introduce a generic register settings dt-binding 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=696774c5-db1c-4fcc-a5f6-139dc22ead87@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