http://bugzilla.opensuse.org/show_bug.cgi?id=998440 http://bugzilla.opensuse.org/show_bug.cgi?id=998440#c2 Giacomo Comes changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(comes@naic.edu) | --- Comment #2 from Giacomo Comes --- I have done more testing. Finally on this laptop the minimum requirement in order to have the mmc card reader working is to simply add the module pinctrl-cherryview in the initrd. If I want that the mmc card is accessible also while the initrd is mounted as the root filesystem, then I need to add the module sdhci-pci too. To achieve that I created a file in /etc/dracut.conf.d containing: add_drivers+=" pinctrl-cherryview" or add_drivers+=" pinctrl-cherryview sdhci-pci" There is no need to force the loading of the module or to add softdep in modprobe.d. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=998440 http://bugzilla.opensuse.org/show_bug.cgi?id=998440#c6 --- Comment #6 from Takashi Iwai --- (In reply to Giacomo Comes from comment #5)

I have tested your dracut module script on three cherryview PC. Acer Aspire R11, Intel compute stick STK1AW32SC, Dell Inspiron 11-3168 In every PC /sys/bus/acpi/devices/INT33FF:00 is present so the module pinctrl-cherryview is inserted in the initrd and the sd card is working. However, the Dell Inspiron 11-3168 does not need such module. The SD card is not accessed as /dev/mmcblk0 but as /dev/sdb. Actually on such laptop the sd card reader has always worked and because of that I was not aware that it was a cherryview system.

I have tested a modified version of the module script. This one checks the presence of /sys/bus/mmc/drivers/mmcblk which does exist if the card is accessed as /dev/mmcmlk0 and is missing if the sd card is accessed as /dev/sdb

Here is the modified check function I have tested.

check() { test -d /sys/bus/acpi/devices/INT33FF:00 && test -d /sys/bus/mmc/drivers/mmcblk }

With this modified check, the pinctrl-cherryview module is inserted in the initrd only for the PC that really needs it.

This won't work because mmcblk appears only after binding with mmc driver, and the binding happens only *after* pinctrl driver is initialized. So it's a chicken-and-egg problem. You have to load pinctrl at first so that mmcblk appears. Putting pinctrl-cherryview in initrd itself should be harmless except for a unused memory footprint. And INT33FF is the only matching criteria the pinctrl-cherryview driver exposes. So in principle, it's correct to have only this check in dracut. Of course, we may add yet more fine check (e.g. checking DMI). If your Dell machine, check again the initrd without this hack, and see whether pinctrl-cherryview is loaded even without it or not. The module should be picked up due to ACPI INT33FF match. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=998440 http://bugzilla.opensuse.org/show_bug.cgi?id=998440#c8 --- Comment #8 from Takashi Iwai --- The pinctrl-cherryview driver isn't needed only for mmc but for other things, too. Judging only from the mmcblk doesn't work reliably in that sense. That said, basically it's correct to include this module when INT33FF is present. The driver shall be always loaded by every system that has INT33FF. It bails out when no corresponding component is found, so it's not visible in lsmod at later point. So it's just a matter of the timing and a slight increase of initrd size, after all. -- You are receiving this mail because: You are on the CC list for the bug.