From: Wolfram Sang <w.sang@pengutronix.de>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: Chris Ball <cjb@laptop.org>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sdhci: fix undue iomem warning
Date: Mon, 30 May 2011 14:58:22 +0200 [thread overview]
Message-ID: <20110530125822.GD3409@pengutronix.de> (raw)
In-Reply-To: <1306758796-4254-1-git-send-email-daniel.blueman@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
Hi Daniel,
> diff --git a/drivers/mmc/host/sdhci-pci.c b/drivers/mmc/host/sdhci-pci.c
> index 936bbca..ae948b0 100644
> --- a/drivers/mmc/host/sdhci-pci.c
> +++ b/drivers/mmc/host/sdhci-pci.c
> @@ -918,8 +918,9 @@ static struct sdhci_pci_slot * __devinit sdhci_pci_probe_slot(
> return ERR_PTR(-ENODEV);
> }
>
> - if (pci_resource_len(pdev, bar) != 0x100) {
> - dev_err(&pdev->dev, "Invalid iomem size. You may "
> + int len = pci_resource_len(pdev, bar);
> + if (len != 0x100 && len != 0x200) {
Hmmm,
a) SDHC Specs (even v3) only mention 0x100, so this _is_ the standard.
Do the new cards (which ones?) have anything located in the extra
area?
b) your approach won't scale very well
so, I'd say it is better to keep the old way.
> + dev_warn(&pdev->dev, "Invalid iomem size. You may "
> "experience problems.\n");
I second turning the message into a warning, though.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-05-30 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 12:33 [PATCH] sdhci: fix undue iomem warning Daniel J Blueman
2011-05-30 12:58 ` Wolfram Sang [this message]
2011-05-30 13:27 ` Daniel J Blueman
2011-05-30 18:21 ` Wolfram Sang
2011-05-30 18:33 ` Arnd Bergmann
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=20110530125822.GD3409@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=cjb@laptop.org \
--cc=daniel.blueman@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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