[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <34072875.m9Xp8G9xV5@pc-42>
Date: Thu, 28 Oct 2021 11:55:09 +0200
From: Jérôme Pouiller <jerome.pouiller@...abs.com>
To: "H. Nikolaus Schaller" <hns@...delico.com>
Cc: Ulf Hansson <ulf.hansson@...aro.org>,
Avri Altman <avri.altman@....com>,
Shawn Lin <shawn.lin@...k-chips.com>,
Linus Walleij <linus.walleij@...aro.org>,
Bean Huo <beanhuo@...ron.com>, linux-mmc@...r.kernel.org,
linux-kernel <linux-kernel@...r.kernel.org>,
Discussions about the Letux Kernel
<letux-kernel@...nphoenux.org>, kernel@...a-handheld.com,
Tony Lindgren <tony@...mide.com>,
Linux-OMAP <linux-omap@...r.kernel.org>
Subject: Re: [RFC] mmc: core: transplant ti,wl1251 quirks from to be retired omap_hsmmc
On Thursday 28 October 2021 11:40:59 CEST H. Nikolaus Schaller wrote:
> > Am 28.10.2021 um 10:59 schrieb Jérôme Pouiller <jerome.pouiller@...abs.com>:
> > On Thursday 28 October 2021 09:08:50 CEST H. Nikolaus Schaller wrote:
> >
> >>> Let me have a closer look - and for sure, I am willing to help if needed.
> >
> > I confirm it does not have the expected behavior. !mmc_fixup_of_compatible_match()
> > should be mmc_fixup_of_compatible_match(), sorry.
>
> Ok, I see.
>
> One more question: how can I specify "ti,wl1251" in some struct mmc_fixup table?
> Does it need another macro like MMC_FIXUP() or SDIO_FIXUP() to set the .name
> field?
yes, I didn't provide it with my RFC.
--
Jérôme Pouiller
Powered by blists - more mailing lists