> Usually we don't add soc_device_match quirks for unknown future revisions.
I was just following...
>
> > --- a/drivers/mmc/host/renesas_sdhi_core.c
> > +++ b/drivers/mmc/host/renesas_sdhi_core.c
> > @@ -711,11 +711,17 @@ static const struct renesas_sdhi_quirks sdhi_quirks_nohs400 = {
> > .hs400_disabled = true,
> > };
> >
> > +/*
> > + * Note for r8a7796 / r8a774a1: we can't distinguish ES1.1 and 1.2 as of now.
> > + * So, we want to treat them equally and only have a match for ES1.2 to enforce
> > + * this if there ever will be a way to distinguish ES1.2.
> > + */
> > static const struct soc_device_attribute sdhi_quirks_match[] = {
> > { .soc_id = "r8a774a1", .revision = "ES1.[012]", .data = &sdhi_quirks_4tap_nohs400 },
> > { .soc_id = "r8a7795", .revision = "ES1.*", .data = &sdhi_quirks_4tap_nohs400 },
... this example here. This also applies to all future versions (not
that there will be any), no?
> > { .soc_id = "r8a7795", .revision = "ES2.0", .data = &sdhi_quirks_4tap },
> > { .soc_id = "r8a7796", .revision = "ES1.[012]", .data = &sdhi_quirks_4tap_nohs400 },
> > + { .soc_id = "r8a7796", .revision = "ES1.*", .data = &sdhi_quirks_4tap },
>
> R-Car M3-N is r8a77965, not r8a7796?
Right. $subject should be M3-W :(
Attachment:
signature.asc
Description: PGP signature
