On 24/08/2020 20:15, Sowjanya Komatineni wrote:
Tegra210 and later uses separate SDMMC_LEGACY_TM clock for data timeout.
So, this patch adds "tmclk" to Tegra sdhci clock property in the device tree binding.
Signed-off-by: Sowjanya Komatineni skomatineni@nvidia.com
.../bindings/mmc/nvidia,tegra20-sdhci.txt | 23 +++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt b/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt index 2cf3aff..9603d05 100644 --- a/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt +++ b/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt @@ -17,6 +17,8 @@ Required properties:
- "nvidia,tegra194-sdhci": for Tegra194
- clocks : Must contain one entry, for the module clock. See ../clocks/clock-bindings.txt for details.
- Must also contain "tmclk" entry for Tegra210, Tegra186, and Tegra194.
- Tegra210 and later uses separate SDMMC_LEGACY_TM clock for data timeout.
Maybe we should make this a bit clearer ...
- clocks : For Tegra210, Tegra186 and Tegra194 must contain two entries; one for the module clock and one for the timeout clock. For all other Tegra devices, must contain a single entry for the module clock. See ../clocks/clock-bindings.txt for details. - clock-names: For Tegra210, Tegra186 and Tegra194 must contain the strings 'sdhci' and 'tmclk' to represent the module and timeout clocks, respectively. For all other Tegra devices must contain the string 'sdhci' to represent the module clock.
Cheers Jon