public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: linux-mmc@vger.kernel.org
Subject: sdhci-pci fails on 3.0.0-rc1 on Dell E6510
Date: Sun, 05 Jun 2011 20:26:07 +0200	[thread overview]
Message-ID: <4DEBCA3F.8050205@hartkopp.net> (raw)

Hi all,

in 3.0.0-rc1 (and if i remember correctly earlier in the merge window before
the tag too) my built-in SD/MMC slot does not work as it did with 2.6.39.

Any ideas/patches? Does it help to enable mmc-debugging?

Regards,
Oliver


Linux version 2.6.39

Jun  5 13:40:28 mybox kernel: [    6.209758] sdhci: Secure Digital Host Controller Interface driver
Jun  5 13:40:28 mybox kernel: [    6.209761] sdhci: Copyright(c) Pierre Ossman
(..)
Jun  5 13:40:28 mybox kernel: [    6.366993] sdhci-pci 0000:03:00.1: SDHCI controller found [1180:e822] (rev 3)
Jun  5 13:40:28 mybox kernel: [    6.367017] sdhci-pci 0000:03:00.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
Jun  5 13:40:28 mybox kernel: [    6.367847] mmc0: SDHCI controller on PCI [0000:03:00.1] using DMA


Linux version 3.0.0-rc1-00180-g0792644 (the very latest from Linus' linux-2.6 git tree) 

Jun  5 13:58:16 mybox kernel: [    6.119533] sdhci: Secure Digital Host Controller Interface driver
Jun  5 13:58:16 mybox kernel: [    6.121400] sdhci: Copyright(c) Pierre Ossman
(..)
Jun  5 13:58:16 mybox kernel: [    6.242510] sdhci-pci 0000:03:00.1: SDHCI controller found [1180:e822] (rev 3)
Jun  5 13:58:16 mybox kernel: [    6.244168] sdhci-pci 0000:03:00.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
Jun  5 13:58:16 mybox kernel: [    6.247609] sdhci-pci 0000:03:00.1: PCI INT B disabled

dmesg is a bit more detailed:
[    6.242510] sdhci-pci 0000:03:00.1: SDHCI controller found [1180:e822] (rev 3)
[    6.244168] sdhci-pci 0000:03:00.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[    6.245788] sdhci-pci 0000:03:00.1: BAR 0 is not iomem. Aborting.
[    6.247609] sdhci-pci 0000:03:00.1: PCI INT B disabled

lspci says:

03:00.0 CardBus bridge: Ricoh Co Ltd Device e476 (rev 02)
03:00.1 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller (rev 03)
03:00.4 FireWire (IEEE 1394): Ricoh Co Ltd FireWire Host Controller (rev 03)

Used config:

#
# MMC/SD/SDIO Host Controller Drivers
#
CONFIG_MMC_SDHCI=m
CONFIG_MMC_SDHCI_PCI=m
# CONFIG_MMC_RICOH_MMC is not set <<-- was set in the 2.6.39 mmc config (see below)
# CONFIG_MMC_SDHCI_PLTFM is not set
# CONFIG_MMC_WBSD is not set
# CONFIG_MMC_TIFM_SD is not set
# CONFIG_MMC_SDRICOH_CS is not set
# CONFIG_MMC_CB710 is not set
# CONFIG_MMC_VIA_SDMMC is not set
# CONFIG_MMC_VUB300 is not set <<-- the only difference to 2.6.39 mmc config
# CONFIG_MMC_USHC is not set
# CONFIG_MEMSTICK is not set
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y

Enabling/disabling CONFIG_MMC_RICOH_MMC does not have any effect.


             reply	other threads:[~2011-06-05 18:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-05 18:26 Oliver Hartkopp [this message]
2011-06-06  6:13 ` sdhci-pci fails on 3.0.0-rc1 on Dell E6510 S, Venkatraman
2011-06-06 16:52   ` Oliver Hartkopp
2011-06-06 19:56     ` Chris Ball
2011-06-07 18:36       ` Oliver Hartkopp
2011-06-07 20:06         ` Oliver Hartkopp
2011-06-07 22:18           ` Yinghai Lu
2011-06-08  6:26             ` Oliver Hartkopp
2011-06-12 20:44               ` Ram Pai
2011-06-15 18:31                 ` Bjorn Helgaas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DEBCA3F.8050205@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=linux-mmc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox