2012/1/4 Eric W. Biederman <[email protected]>:
> Hopefully I have added some relevant Cc's. The sdhci driver attempting
> to abuse sysfs and sysfs is refusing to put up with it.
>
> Can someone who understands the sdhci driver take a look at this?
>
> Eric
I forgot to add lspci output. Sorry for this. I added the relevant
device that is being pointed in warning.
lspci:
06:09.4 SD Host controller [0805]: Texas Instruments
PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller
[104c:8034]
Subsystem: Wistron Corp. Device [17c0:3007]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 57 (1750ns min, 1000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 22
Region 0: Memory at b8009400 (32-bit, non-prefetchable) [size=256]
Region 1: Memory at b8009000 (32-bit, non-prefetchable) [size=256]
Region 2: Memory at b8007400 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: sdhci-pci
Kernel modules: sdhci-pci
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
