All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Manuel Lauss <manuel.lauss@googlemail.com>
Cc: linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: sdhci-pci: shut up BAR size warning
Date: Fri, 11 Nov 2011 22:20:36 -0500	[thread overview]
Message-ID: <87bosihvqz.fsf@laptop.org> (raw)
In-Reply-To: <1320870118-3427-1-git-send-email-manuel.lauss@googlemail.com> (Manuel Lauss's message of "Wed, 9 Nov 2011 21:21:58 +0100")

Hi Manuel,

On Wed, Nov 09 2011, Manuel Lauss wrote:
> kernel complains about invalid SDHCI iomem size on boot.  The BAR on my
> O2-Micro controller is 512 bytes large, twice the size SDHCI-PCI needs.
> This patch changes the warning to only appear when the BAR is smaller
> than expected.
>
> Signed-off-by: Manuel Lauss <manuel.lauss@googlemail.com>
> ---
>  drivers/mmc/host/sdhci-pci.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/mmc/host/sdhci-pci.c b/drivers/mmc/host/sdhci-pci.c
> index d833d9c..0ee5c07 100644
> --- a/drivers/mmc/host/sdhci-pci.c
> +++ b/drivers/mmc/host/sdhci-pci.c
> @@ -1199,7 +1199,7 @@ static struct sdhci_pci_slot * __devinit sdhci_pci_probe_slot(
>  		return ERR_PTR(-ENODEV);
>  	}
>  
> -	if (pci_resource_len(pdev, bar) != 0x100) {
> +	if (pci_resource_len(pdev, bar) < 0x100) {
>  		dev_err(&pdev->dev, "Invalid iomem size. You may "
>  			"experience problems.\n");
>  	}

We discussed this a few months ago -- the thread is at:

   http://thread.gmane.org/gmane.linux.kernel.mmc/8314

Thanks,

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

      reply	other threads:[~2011-11-12  3:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09 20:21 [PATCH] mmc: sdhci-pci: shut up BAR size warning Manuel Lauss
2011-11-12  3:20 ` Chris Ball [this message]

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=87bosihvqz.fsf@laptop.org \
    --to=cjb@laptop.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=manuel.lauss@googlemail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.