From: Rajesh Gumasta <rgumasta@nvidia.com>
To: <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>,
Rajesh Gumasta <rgumasta@nvidia.com>
Subject: [PATCH V3 3/3] dt-binding: mmc: tegra: Add register-setting support
Date: Fri, 25 Jul 2025 10:52:25 +0530 [thread overview]
Message-ID: <20250725052225.23510-4-rgumasta@nvidia.com> (raw)
In-Reply-To: <20250725052225.23510-1-rgumasta@nvidia.com>
Add register setting support for the NVIDIA Tegra20 MMC controllers. The
top-level 'reg-settings' node and child nodes for each MMC operating mode
supported are defined in the mmc-controller-common.yaml binding. The
NVIDIA specific register setting property is defined in the
nvidia,tegra20-sdhci.yaml.
Signed-off-by: Rajesh Gumasta <rgumasta@nvidia.com>
---
.../bindings/mmc/mmc-controller-common.yaml | 24 ++++++++++
.../bindings/mmc/nvidia,tegra20-sdhci.yaml | 48 +++++++++++++++++++
2 files changed, 72 insertions(+)
diff --git a/Documentation/devicetree/bindings/mmc/mmc-controller-common.yaml b/Documentation/devicetree/bindings/mmc/mmc-controller-common.yaml
index 9a7235439759..0bdebc6454d8 100644
--- a/Documentation/devicetree/bindings/mmc/mmc-controller-common.yaml
+++ b/Documentation/devicetree/bindings/mmc/mmc-controller-common.yaml
@@ -308,6 +308,30 @@ properties:
sequence. To successfully detect an (e)MMC/SD/SDIO card, that
power sequence must be maintained while initializing the card.
+ reg-settings:
+ $ref: /schemas/regset/register-settings.yaml
+
+ properties:
+ default-settings:
+ type: object
+ description:
+ Default MMC register settings.
+
+ sdr50:
+ type: object
+ description:
+ Register settings for MMC sdr50 operating mode.
+
+ sdr104:
+ type: object
+ description:
+ Register settings for MMC sdr104 operating mode.
+
+ hs200:
+ type: object
+ description:
+ Register settings for MMC hs200 operating mode.
+
patternProperties:
"^.*@[0-9]+$":
type: object
diff --git a/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.yaml b/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.yaml
index 72987f0326a1..a78b2bd92b18 100644
--- a/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.yaml
+++ b/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.yaml
@@ -17,6 +17,15 @@ description: |
This file documents differences between the core properties described by
mmc-controller.yaml and the properties for the Tegra SDHCI controller.
+definitions:
+ reg-settings:
+ properties:
+ nvidia,num-tuning-iterations:
+ description: The number of tuning iterations to be used by tuning circuit.
+ $ref: /schemas/types.yaml#/definitions/uint8
+ minimum: 0
+ maximum: 4
+
properties:
compatible:
oneOf:
@@ -177,6 +186,27 @@ properties:
operates at a 1.8 V fixed I/O voltage.
$ref: /schemas/types.yaml#/definitions/flag
+ reg-settings:
+ $ref: /schemas/mmc/mmc-controller-common.yaml#/properties/reg-settings
+
+ properties:
+ default-settings:
+ $ref: "#/definitions/reg-settings"
+ unevaluatedProperties: false
+
+ sdr50:
+ $ref: "#/definitions/reg-settings"
+ unevaluatedProperties: false
+
+ sdr104:
+ $ref: "#/definitions/reg-settings"
+ unevaluatedProperties: false
+
+ hs200:
+ $ref: "#/definitions/reg-settings"
+ unevaluatedProperties: false
+ unevaluatedProperties: false
+
required:
- compatible
- reg
@@ -310,4 +340,22 @@ examples:
<&tegra_car TEGRA210_CLK_PLL_C4>;
assigned-clock-parents = <&tegra_car TEGRA210_CLK_PLL_C4_OUT0>;
assigned-clock-rates = <200000000>, <1000000000>, <1000000000>;
+
+ reg-settings {
+ default-settings {
+ nvidia,num-tuning-iterations = /bits/ 8 <0>;
+ };
+
+ sdr50 {
+ nvidia,num-tuning-iterations = /bits/ 8 <4>;
+ };
+
+ sdr104 {
+ nvidia,num-tuning-iterations = /bits/ 8 <2>;
+ };
+
+ hs200 {
+ nvidia,num-tuning-iterations = /bits/ 8 <2>;
+ };
+ };
};
--
2.50.1
next prev parent reply other threads:[~2025-07-25 5:23 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 ` Rajesh Gumasta [this message]
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=20250725052225.23510-4-rgumasta@nvidia.com \
--to=rgumasta@nvidia.com \
--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=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