From: Judith Mendez <jm@ti.com>
To: Adrian Hunter <adrian.hunter@intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: Josua Mayer <josua@solid-run.com>, <linux-mmc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Nishanth Menon <nm@ti.com>,
Francesco Dolcini <francesco@dolcini.it>,
Hiago De Franco <hiagofranco@gmail.com>,
Moteen Shah <m-shah@ti.com>
Subject: Re: [PATCH v5] mmc: sdhci_am654: Add SDHCI_QUIRK2_SUPPRESS_V1P8_ENA quirk to am62 compatible
Date: Wed, 14 May 2025 13:44:17 -0500 [thread overview]
Message-ID: <483c7c41-4dd4-4ab8-ab09-bd301de2e540@ti.com> (raw)
In-Reply-To: <d3222aeb-4920-41a2-a8d7-2551115ab776@intel.com>
Hi Adrian,
On 5/14/25 4:10 AM, Adrian Hunter wrote:
> On 14/05/2025 03:25, Judith Mendez wrote:
>> Add a new struct for platform data for the ti,am62-sdhci compatible to
>> apply additional quirks, namely "SDHCI_QUIRK2_SUPPRESS_V1P8_ENA", to
>> host controllers with am62 compatible.
>
> Could add:
>
> Note, the fix was originally introduced by commit 941a7abd4666
> ("mmc: sdhci_am654: Add sdhci_am654_start_signal_voltage_switch") but was
> found to be applied too broadly and had to be reverted.
Sure I can add for v6
...
>>
>> +static const struct sdhci_pltfm_data sdhci_am62_4bit_pdata = {
>> + .ops = &sdhci_j721e_4bit_ops,
>> + .quirks = SDHCI_QUIRK_MULTIBLOCK_READ_ACMD12,
>> + .quirks2 = SDHCI_QUIRK2_PRESET_VALUE_BROKEN,
>> +};
>
> sdhci_am62_4bit_pdata is the same as sdhci_j721e_4bit_pdata
oh right sdhci_am62_4bit_pdata can be removed. thanks. will fix for v6
Judith
>
>> +
>> +static const struct sdhci_am654_driver_data sdhci_am62_4bit_drvdata = {
>> + .pdata = &sdhci_am62_4bit_pdata,
>> + .flags = IOMUX_PRESENT,
>> + .quirks = SDHCI_AM654_QUIRK_SUPPRESS_V1P8_ENA,
>> +};
>> +
...
prev parent reply other threads:[~2025-05-14 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 0:25 [PATCH v5] mmc: sdhci_am654: Add SDHCI_QUIRK2_SUPPRESS_V1P8_ENA quirk to am62 compatible Judith Mendez
2025-05-14 9:10 ` Adrian Hunter
2025-05-14 18:44 ` Judith Mendez [this message]
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=483c7c41-4dd4-4ab8-ab09-bd301de2e540@ti.com \
--to=jm@ti.com \
--cc=adrian.hunter@intel.com \
--cc=francesco@dolcini.it \
--cc=hiagofranco@gmail.com \
--cc=josua@solid-run.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=m-shah@ti.com \
--cc=nm@ti.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