Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757983AbYFWOMW (ORCPT ); Mon, 23 Jun 2008 10:12:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753171AbYFWOMP (ORCPT ); Mon, 23 Jun 2008 10:12:15 -0400 Received: from mail.atmel.fr ([81.80.104.162]:36030 "EHLO atmel-es2.atmel.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752705AbYFWOMO (ORCPT ); Mon, 23 Jun 2008 10:12:14 -0400 Message-ID: <485FAF34.8000609@atmel.com> Date: Mon, 23 Jun 2008 16:12:04 +0200 From: Nicolas Ferre Organization: atmel User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Nicolas Pitre CC: Pierre Ossman , ARM Linux Mailing List , Linux Kernel list Subject: Re: sdio: bad CISTPL_FUNCE error References: <485BCBB3.20405@atmel.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1584 Lines: 50 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/