From: David Brownell <david-b@pacbell.net>
To: Matt Fleming <matt@console-pimps.org>
Cc: "Wolfgang Mües" <wolfgang.mues@auerswald.de>,
"Pierre Ossman" <drzeus@drzeus.cx>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Mike Frysinger" <vapier.adi@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mmc_spi: use EILSEQ for possible transmission errors
Date: Tue, 19 May 2009 21:49:07 -0700 [thread overview]
Message-ID: <200905192149.07778.david-b@pacbell.net> (raw)
In-Reply-To: <20090519112948.GB28564@console-pimps.org>
On Tuesday 19 May 2009, Matt Fleming wrote:
> Hmm, always returning -EILSEQ is devious. What happens if we sent an
> illegal command? The value of "value" is passed up to the callers via
> cmd->error and so may eventually get printed in the pr_debug() call in
> mmc_request_done(), line 86.
True, but a pr_debug from mmc_spi could help that. A patch doing
that would need to be less aggressive about ripping out the current
fault-parsing logic, but it could continue reporting -EILSEQ to
cope with the possible response mangling.
> Whereas before the error would display EINVAL for an illegal command
> now it'll display EILSEQ, which makes no sense. Seeing EILSEQ in my
> log when really the error is EINVAL is gonna really confuse me.
>
> IMHO always assuming that command errors are caused by transmission
> problems is not the right solution.
Do you have a better solution to propose though? If Wolfgang
is actually observing transmission errors there, I'm not sure
a better one is to be had.
Though I wonder what this would do for anyone trying SDIO over
the mmc_spi driver.
- Dave
next prev parent reply other threads:[~2009-05-20 4:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 11:24 [PATCH] mmc_spi: use EILSEQ for possible transmission errors Wolfgang Mües
2009-05-19 11:29 ` Matt Fleming
2009-05-19 11:47 ` Wolfgang Mües
2009-05-20 7:53 ` Matt Fleming
2009-05-20 4:49 ` David Brownell [this message]
2009-05-20 8:35 ` Wolfgang Mües
2009-05-20 9:20 ` David Brownell
2009-05-20 10:08 ` Pierre Ossman
2009-05-21 2:02 ` David Brownell
2009-05-25 9:04 ` Wolfgang Mües
2009-05-25 9:43 ` David Brownell
2009-05-25 10:18 ` Wolfgang Mües
2009-05-25 11:50 ` Pierre Ossman
2009-05-25 14:59 ` Wolfgang Mües
2009-06-09 18:07 ` Pierre Ossman
2009-06-10 7:29 ` Wolfgang Mües
2009-06-10 7:37 ` Matt Fleming
2009-06-13 10:57 ` Pierre Ossman
2009-05-25 11:48 ` Pierre Ossman
2009-05-20 10:31 ` Wolfgang Mües
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=200905192149.07778.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=drzeus@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=vapier.adi@gmail.com \
--cc=wolfgang.mues@auerswald.de \
/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.