From: Ulf Hansson <ulf.hansson@linaro.org>
To: Jerome Pouiller <Jerome.Pouiller@silabs.com>
Cc: linux-mmc <linux-mmc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Kalle Valo <kvalo@codeaurora.org>
Subject: Re: [RFC PATCH 2/2] mmc: allow to match the device tree to apply quirks
Date: Wed, 20 Oct 2021 16:29:44 +0200 [thread overview]
Message-ID: <CAPDyKFpr0kpRXoUACNNSwe8pL1S9wJPjnX+GFGS1PNezKCDYzQ@mail.gmail.com> (raw)
In-Reply-To: <20211014143031.1313783-3-Jerome.Pouiller@silabs.com>
On Thu, 14 Oct 2021 at 16:30, Jerome Pouiller
<Jerome.Pouiller@silabs.com> wrote:
>
> From: Jérôme Pouiller <jerome.pouiller@silabs.com>
>
> MMC subsystem provides a way to apply quirks when a device match some
> properties (VID, PID, etc...) Unfortunately, some SDIO devices does not
> comply with the SDIO specification and does not provide reliable VID/PID
> (eg. Silabs WF200).
>
> So, the drivers for these devices rely on device tree to identify the
> device.
>
> This patch allows the MMC to also rely on the device tree to apply a
> quirk.
>
> Signed-off-by: Jérôme Pouiller <jerome.pouiller@silabs.com>
> ---
> drivers/mmc/core/card.h | 3 +++
> drivers/mmc/core/quirks.h | 18 ++++++++++++++++++
> 2 files changed, 21 insertions(+)
>
> diff --git a/drivers/mmc/core/card.h b/drivers/mmc/core/card.h
> index 7bd392d55cfa..2f73f8567e14 100644
> --- a/drivers/mmc/core/card.h
> +++ b/drivers/mmc/core/card.h
> @@ -59,6 +59,9 @@ struct mmc_fixup {
> /* for MMC cards */
> unsigned int ext_csd_rev;
>
> + /* Match against functions declared in device tree */
> + const char *const *of_compatible;
const char is probably sufficient.
> +
> void (*vendor_fixup)(struct mmc_card *card, int data);
> int data;
> };
> diff --git a/drivers/mmc/core/quirks.h b/drivers/mmc/core/quirks.h
> index c7ef2d14b359..ef368386e711 100644
> --- a/drivers/mmc/core/quirks.h
> +++ b/drivers/mmc/core/quirks.h
> @@ -10,6 +10,7 @@
> *
> */
>
> +#include <linux/of.h>
> #include <linux/mmc/sdio_ids.h>
>
> #include "card.h"
> @@ -145,6 +146,20 @@ static const struct mmc_fixup __maybe_unused sdio_fixup_methods[] = {
> END_FIXUP
> };
>
> +static inline bool mmc_fixup_of_compatible_match(struct mmc_card *card,
> + const char *const *compat_list)
> +{
> + struct device_node *of_node;
> + int i;
> +
> + for (i = 0; i < 7; i++) {
We need to iterate up '8', to cover all functional devices.
The function numbers are from 1->7, while we use '0' for the
"mmc-card" compatible.
> + of_node = mmc_of_find_child_device(card->host, i);
> + if (of_node && of_device_compatible_match(of_node, compat_list))
> + return true;
> + }
Another option, which would avoid doing the iteration over and over
again in mmc_of_find_child_device(), would be to simply do the parsing
of the compatible in the child nodes, right here. In other words, just
use for_each_child_of_node().
> + return false;
> +}
> +
> static inline void mmc_fixup_device(struct mmc_card *card,
> const struct mmc_fixup *table)
> {
> @@ -173,6 +188,9 @@ static inline void mmc_fixup_device(struct mmc_card *card,
> continue;
> if (rev < f->rev_start || rev > f->rev_end)
> continue;
> + if (f->of_compatible != NULL &&
> + !mmc_fixup_of_compatible_match(card, f->of_compatible))
> + continue;
>
> dev_dbg(&card->dev, "calling %ps\n", f->vendor_fixup);
> f->vendor_fixup(card, f->data);
Kind regards
Uffe
prev parent reply other threads:[~2021-10-20 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 14:30 [RFC PATCH 0/2] mmc: allow to rely on the DT to apply quirks Jerome Pouiller
2021-10-14 14:30 ` [RFC PATCH 1/2] mmc: rewrite mmc_fixup_device() Jerome Pouiller
2021-10-14 14:30 ` [RFC PATCH 2/2] mmc: allow to match the device tree to apply quirks Jerome Pouiller
2021-10-20 14:29 ` Ulf Hansson [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=CAPDyKFpr0kpRXoUACNNSwe8pL1S9wJPjnX+GFGS1PNezKCDYzQ@mail.gmail.com \
--to=ulf.hansson@linaro.org \
--cc=Jerome.Pouiller@silabs.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).