[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dcdc51bb-fc8d-04e5-2edb-903f7a531cb8@amd.com>
Date: Wed, 31 Aug 2022 22:49:19 +0000
From: "Larson, Bradley" <Bradley.Larson@....com>
To: Philipp Zabel <p.zabel@...gutronix.de>,
Brad Larson <brad@...sando.io>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
"adrian.hunter@...el.com" <adrian.hunter@...el.com>,
"alcooperx@...il.com" <alcooperx@...il.com>,
"andy.shevchenko@...il.com" <andy.shevchenko@...il.com>,
"arnd@...db.de" <arnd@...db.de>,
"brijeshkumar.singh@....com" <brijeshkumar.singh@....com>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"gsomlo@...il.com" <gsomlo@...il.com>,
"gerg@...ux-m68k.org" <gerg@...ux-m68k.org>,
"krzk@...nel.org" <krzk@...nel.org>,
"krzysztof.kozlowski+dt@...aro.org"
<krzysztof.kozlowski+dt@...aro.org>,
"lee.jones@...aro.org" <lee.jones@...aro.org>,
"broonie@...nel.org" <broonie@...nel.org>,
"yamada.masahiro@...ionext.com" <yamada.masahiro@...ionext.com>,
"piotrs@...ence.com" <piotrs@...ence.com>,
"p.yadav@...com" <p.yadav@...com>,
"rdunlap@...radead.org" <rdunlap@...radead.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"samuel@...lland.org" <samuel@...lland.org>,
"fancer.lancer@...il.com" <fancer.lancer@...il.com>,
"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@....com>,
"Lendacky, Thomas" <Thomas.Lendacky@....com>,
"ulf.hansson@...aro.org" <ulf.hansson@...aro.org>,
"will@...nel.org" <will@...nel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH v6 17/17] mmc: sdhci-cadence: Support mmc hardware reset
On 8/22/22 12:03 AM, Philipp Zabel wrote:
> Hi Brad,
>
> On Sa, 2022-08-20 at 12:57 -0700, Brad Larson wrote:
> [...]
>> +static void sdhci_mmc_hw_reset(struct mmc_host *mmc)
>> +{
>> + struct sdhci_host *host = mmc_priv(mmc);
>> + struct sdhci_cdns_priv *priv = sdhci_cdns_priv(host);
>> +
>> + dev_info(mmc_dev(host->mmc), "emmc hardware reset\n");
>> +
>> + reset_control_assert(priv->rst_hw);
>> + /* For eMMC, minimum is 1us but give it 9us for good measure */
>> + udelay(9);
> At a glance, this seems excessive. Is there a reason 9 us is better
> than, say, 2 or 3?
Yes, 3x the minimum should be fine. Changed to 3 usec.
> [...]
>> @@ -520,6 +538,17 @@ static int sdhci_cdns_probe(struct platform_device *pdev)
>> if (ret)
>> goto free;
>>
>>
>>
>>
>> + if (host->mmc->caps & MMC_CAP_HW_RESET) {
>> + priv->rst_hw = devm_reset_control_get_optional_exclusive(dev, "hw");
> This should be described in cdns,sdhci.yaml first.
Adding this to cdns,sdhci.yaml and running through schema checker.
--- a/Documentation/devicetree/bindings/mmc/cdns,sdhci.yaml
+++ b/Documentation/devicetree/bindings/mmc/cdns,sdhci.yaml
@@ -114,6 +114,16 @@ properties:
minimum: 0
maximum: 0x7f
+ reset-names:
+ items:
+ - const: hw
+
+ resets:
+ description:
+ optional. phandle to the system reset controller with line index
+ for mmc hw reset line if exists.
+ maxItems: 1
+
required:
- compatible
Regards,
Brad
Powered by blists - more mailing lists