From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Nicolas Pitre <nico@cam.org>
Cc: Pierre Ossman <drzeus@drzeus.cx>,
ARM Linux Mailing List <linux-arm-kernel@lists.arm.linux.org.uk>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: sdio: bad CISTPL_FUNCE error
Date: Mon, 23 Jun 2008 16:12:04 +0200 [thread overview]
Message-ID: <485FAF34.8000609@atmel.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0806211045390.2979@xanadu.home>
Nicolas Pitre :
> On Fri, 20 Jun 2008, Nicolas Ferre wrote:
>
>> Hi Pierre,
>>
>> While trying to setup a GPS SDIO card, I experience the following error:
>> "mmc0: bad CISTPL_FUNCE size 28 type 1"
>
> Could you apply this patch and see what it shows:
>
> diff --git a/drivers/mmc/core/sdio_cis.c b/drivers/mmc/core/sdio_cis.c
> index d5e51b1..60ec4d3 100644
> --- a/drivers/mmc/core/sdio_cis.c
> +++ b/drivers/mmc/core/sdio_cis.c
> @@ -149,8 +149,9 @@ static int cistpl_funce(struct mmc_card *card, struct sdio_func *func,
> ret = cistpl_funce_common(card, buf, size);
>
> if (ret) {
> - printk(KERN_ERR "%s: bad CISTPL_FUNCE size %u "
> - "type %u\n", mmc_hostname(card->host), size, buf[0]);
> + printk(KERN_ERR "%s: bad %s CISTPL_FUNCE size %u type %u\n",
> + mmc_hostname(card->host), func ? "function" : "common",
> + size, buf[0]);
> return ret;
> }
>
>
>> I use a combo card but without mirco sd card inserted.
>> http://www.spectec.com.tw/sdg810.htm
>>
>> Tracing in sdio_cis.c file, I print the tpl_code (line 216).
>> I have 3 successive codes : 0xff, 0x21 & 0x22.
>
> Again that would be good to know if/when func is NULL when those are
> parsed.
Here is the log :
mmc0: bad function CISTPL_FUNCE size 28 type 1
with code 0x22.
Thanks for your help. Regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2008-06-23 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 15:24 sdio: bad CISTPL_FUNCE error Nicolas Ferre
2008-06-21 15:00 ` Nicolas Pitre
2008-06-23 14:12 ` Nicolas Ferre [this message]
2008-06-23 15:09 ` Nicolas Pitre
2008-06-24 9:34 ` Nicolas Ferre
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=485FAF34.8000609@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=drzeus@drzeus.cx \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@cam.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