From: Chris Ball <cjb@laptop.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: Report failure reasons for all cases in sdhci_add_host()
Date: Tue, 03 Jul 2012 20:29:55 -0400 [thread overview]
Message-ID: <87d34c74ho.fsf@octavius.laptop.org> (raw)
In-Reply-To: <1341235575-17553-1-git-send-email-broonie@opensource.wolfsonmicro.com> (Mark Brown's message of "Mon, 2 Jul 2012 14:26:15 +0100")
Hi,
On Mon, Jul 02 2012, Mark Brown wrote:
> For most error conditions sdhci_add_host() will print a diagnostic
> message indicating why it failed but there are a few cases where this
> does not happen. Add error messages in these cases to aid diagnosis.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> drivers/mmc/host/sdhci.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
> index caba999..acbc420 100644
> --- a/drivers/mmc/host/sdhci.c
> +++ b/drivers/mmc/host/sdhci.c
> @@ -3031,8 +3031,11 @@ int sdhci_add_host(struct sdhci_host *host)
>
> ret = request_irq(host->irq, sdhci_irq, IRQF_SHARED,
> mmc_hostname(mmc), host);
> - if (ret)
> + if (ret) {
> + pr_err("%s: Failed to request IRQ %d: %d\n",
> + mmc_hostname(mmc), host->irq, ret);
> goto untasklet;
> + }
>
> sdhci_init(host, 0);
>
> @@ -3049,8 +3052,11 @@ int sdhci_add_host(struct sdhci_host *host)
> host->led.brightness_set = sdhci_led_control;
>
> ret = led_classdev_register(mmc_dev(mmc), &host->led);
> - if (ret)
> + if (ret) {
> + pr_err("%s: Failed to register LED device: %d\n",
> + mmc_hostname(mmc), ret);
> goto reset;
> + }
> #endif
>
> mmiowb();
Thanks, pushed to mmc-next for 3.6.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
prev parent reply other threads:[~2012-07-04 0:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 13:26 [PATCH] mmc: Report failure reasons for all cases in sdhci_add_host() Mark Brown
2012-07-04 0:29 ` 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=87d34c74ho.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=broonie@opensource.wolfsonmicro.com \
--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 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.