From: Rob Herring <robh@kernel.org>
To: Krishna Yarlagadda <kyarlagadda@nvidia.com>
Cc: linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
thierry.reding@gmail.com, jonathanh@nvidia.com,
krzk+dt@kernel.org, conor+dt@kernel.org, corbet@lwn.net,
andi.shyti@kernel.org, wsa+renesas@sang-engineering.com,
ulf.hansson@linaro.org, adrian.hunter@intel.com,
digetx@gmail.com, ldewangan@nvidia.com, mkumard@nvidia.com
Subject: Re: [RFC PATCH V2 04/12] dt-bindings: misc: tegra-i2c: config settings
Date: Mon, 1 Jul 2024 11:42:27 -0600 [thread overview]
Message-ID: <20240701174227.GA148633-robh@kernel.org> (raw)
In-Reply-To: <20240701151231.29425-5-kyarlagadda@nvidia.com>
On Mon, Jul 01, 2024 at 08:42:22PM +0530, Krishna Yarlagadda wrote:
> I2C interface timing registers are configured using config setting
> framework. List available field properties for Tegra I2C controllers.
How is I2C bus timing parameters specific to NVIDIA? Just because you
have more controls? No. That's no reason to invent a whole new way to
specify parameters. Extend what's already there and make it work for
anyone.
Rob
next prev parent reply other threads:[~2024-07-01 17:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 15:12 [RFC PATCH V2 00/12] Introduce Tegra register config settings Krishna Yarlagadda
2024-07-01 15:12 ` [RFC PATCH V2 01/12] Documentation: Introduce config settings framework Krishna Yarlagadda
2024-07-01 15:12 ` [RFC PATCH V2 02/12] dt-bindings: misc: Tegra configuration settings Krishna Yarlagadda
2024-07-01 16:58 ` Rob Herring (Arm)
2024-07-01 15:12 ` [RFC PATCH V2 03/12] soc: tegra: Add config setting framework Krishna Yarlagadda
2024-07-01 15:12 ` [RFC PATCH V2 04/12] dt-bindings: misc: tegra-i2c: config settings Krishna Yarlagadda
2024-07-01 16:58 ` Rob Herring (Arm)
2024-07-01 17:42 ` Rob Herring [this message]
2024-07-02 10:29 ` Thierry Reding
2024-07-03 20:21 ` Rob Herring
2024-07-05 10:51 ` Thierry Reding
2024-07-01 15:12 ` [RFC PATCH V2 05/12] dt-bindings: i2c: tegra-i2c: reference to config Krishna Yarlagadda
2024-07-01 16:58 ` Rob Herring (Arm)
2024-07-01 15:12 ` [RFC PATCH V2 06/12] i2c: tegra: split clock initialization code Krishna Yarlagadda
2024-07-01 15:12 ` [RFC PATCH V2 07/12] i2c: tegra: config settings for interface timings Krishna Yarlagadda
2024-07-01 15:12 ` [RFC PATCH V2 08/12] arm64: tegra: I2C " Krishna Yarlagadda
2024-07-01 15:12 ` [RFC PATCH V2 09/12] dt-bindings: misc: tegra-sdhci: config settings Krishna Yarlagadda
2024-07-01 15:12 ` [RFC PATCH V2 10/12] dt-bindings: mmc: tegra-sdhci: reference to config Krishna Yarlagadda
2024-07-01 15:12 ` [RFC PATCH V2 11/12] mmc: host: tegra: config settings for timing Krishna Yarlagadda
2024-07-01 15:12 ` [RFC PATCH V2 12/12] arm64: tegra: SDHCI timing settings Krishna Yarlagadda
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=20240701174227.GA148633-robh@kernel.org \
--to=robh@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=kyarlagadda@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mkumard@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=ulf.hansson@linaro.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).