From: Francesco Dolcini <francesco@dolcini.it>
To: Judith Mendez <jm@ti.com>
Cc: Hiago De Franco <hiagofranco@gmail.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Josua Mayer <josua@solid-run.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Moteen Shah <m-shah@ti.com>,
Hiago De Franco <hiago.franco@toradex.com>
Subject: Re: [PATCH 0/2] Fix V1P8_SIGNAL_ENA and HIGH_SPEED_ENA
Date: Mon, 14 Apr 2025 08:51:19 +0200 [thread overview]
Message-ID: <20250414065119.GA6309@francesco-nb> (raw)
In-Reply-To: <5f36ec5d-bb31-4b6c-aa4e-4ec48cb1d067@ti.com>
Hello Judith
On Fri, Apr 11, 2025 at 04:55:39PM -0500, Judith Mendez wrote:
> My understanding was that we do not like adding new DT properties if
> we can find a way to apply the quirk in the driver.
...
> If this implementation flies with the maintainers, then we can go back to DT
> property implementation.
Not sure if this is clear, but this patch is NOT working according to
our tests, we would need to fix it in a different way.
Francesco
>
>
>
>
>
>
next prev parent reply other threads:[~2025-04-14 6:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 22:27 [PATCH 0/2] Fix V1P8_SIGNAL_ENA and HIGH_SPEED_ENA Judith Mendez
2025-04-07 22:27 ` [PATCH 1/2] PENDING: mmc: sdhci*: Add set_hs_ena to sdhci_ops Judith Mendez
2025-04-09 12:48 ` Ulf Hansson
2025-04-09 17:11 ` Judith Mendez
2025-04-07 22:27 ` [PATCH 2/2] mmc: sdhci_am654: Add sdhci_am654_start_signal_voltage_switch Judith Mendez
2025-04-11 13:03 ` [PATCH 0/2] Fix V1P8_SIGNAL_ENA and HIGH_SPEED_ENA Hiago De Franco
2025-04-11 16:37 ` Judith Mendez
2025-04-11 19:48 ` Hiago De Franco
2025-04-11 21:55 ` Judith Mendez
2025-04-12 13:20 ` Hiago De Franco
2025-04-14 14:31 ` Judith Mendez
2025-04-14 6:51 ` Francesco Dolcini [this message]
2025-04-14 14:37 ` Judith Mendez
2025-04-14 14:57 ` Francesco Dolcini
2025-04-14 22:56 ` Judith Mendez
2025-04-16 16:59 ` Judith Mendez
2025-04-16 19:11 ` Adrian Hunter
2025-04-17 12:03 ` Adrian Hunter
2025-04-17 15:05 ` Judith Mendez
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=20250414065119.GA6309@francesco-nb \
--to=francesco@dolcini.it \
--cc=adrian.hunter@intel.com \
--cc=hiago.franco@toradex.com \
--cc=hiagofranco@gmail.com \
--cc=jm@ti.com \
--cc=josua@solid-run.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=m-shah@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