Hi Fabio, Yes, the bug exists on mainline. We just haven't gotten around to submitting the patch. If you're curious for more details, here's the description of our internal PR:
Our "no-1-8-v" flag in the device tree is supposed to disable 1.8V mmc, but > commit 8cb851a4da64aa838c3cb4fa76ad130ace2b5a98 > <http://stash-prod.izotope.int:7990/projects/HDW/repos/linux-imx/commits/8cb851a4da64aa838c3cb4fa76ad130ace2b5a98> > in mainline changed the voltage selection logic. Choice quote: > > Signal voltage support is not a quirk, it is a capability. > > Freescale's sdhci-esdhc-imx.c sets MMC_CAP_1_8V_DDR without regard to this > flag, and with the new voltage selection logic, this MMC_CAP_1_8V_DDR > forces 1.8V to be enabled. So we change the effect of "no-1-8-v" to disable > MMC_CAP_1_8V_DDR. > > John On Sat, Apr 7, 2018 at 12:45 PM, Fabio Estevam <feste...@gmail.com> wrote: > Hi Matt, > > On Mon, Mar 26, 2018 at 8:56 PM, Matt Campbell <mcampb...@izotope.com> > wrote: > > Hi all, > > > > Thanks for the input. I'll check if the bug exists on mainline and submit > > there if it does. > > Just curious: does the esdhc bug exist in mainline or not? >
-- _______________________________________________ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
