public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Chintan Vankar <c-vankar@ti.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, 30 Sep 2025 16:01:27 +0100	[thread overview]
Message-ID: <d619df1f-813d-4be5-8d24-295455f956de@nvidia.com> (raw)
In-Reply-To: <0784441c-9859-4418-a4a7-85ffe3ecf860@ti.com>

Hi Chintan,

On 29/09/2025 05:39, Chintan Vankar wrote:

...

> Following your series, I would like to bring to your attention that
> Texas Instruments SoCs also have a component which requires similar kind
> of configuration, named Timesync Router(TSR). It enables the
> multiplexing of M inputs to N outputs, where inputs can be selectively
> driven based on N output configuration. A detailed explanation of the
> TSR and our attempts we tried to implement TSR can be found in following
> RFC series:
> https://lore.kernel.org/all/20250605063422.3813260-1-c-vankar@ti.com/
> https://lore.kernel.org/all/20250205160119.136639-1-c-vankar@ti.com/
> 
> To implement TSR, the relevant registers must be configured via the
> device tree. We initially assumed that the device could be handled as a
> mux-controller and could be extended in the same subsystem, but it was
> ineffective. Having explored both the approaches, we now plan to
> implement TSR within misc subsystem, which aligns with the dt-bindings
> that you have proposed in this series.
> 
> The purpose to replying over this series is to inform you that we also
> have a component requiring configuration as outlined in this series. Let
> us know if you have any suggestions for this.

That's great! Thanks for the feedback.

Rob, Krzysztof, Conor, have you guys had chance to look at this series 
some more? We are open to re-working it as necessary to address any 
concerns/comments you have. However, this appears to be stalled at the 
moment and I am not sure what we should do next to push this forward.

Thanks!
Jon

-- 
nvpublic


  reply	other threads:[~2025-09-30 15:01 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 [this message]
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=d619df1f-813d-4be5-8d24-295455f956de@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=andersson@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=c-vankar@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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