public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <ext-adrian.hunter@nokia.com>
To: Pierre Ossman <drzeus-mmc@drzeus.cx>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MMC: Add Extended CSD as a device attribute
Date: Mon, 26 Jan 2009 11:16:36 +0200	[thread overview]
Message-ID: <497D7F74.6050409@nokia.com> (raw)
In-Reply-To: <20090124214543.60d7c939@mjolnir.drzeus.cx>

Pierre Ossman wrote:
> On Fri, 16 Jan 2009 12:41:50 +0200
> Adrian Hunter <ext-adrian.hunter@nokia.com> wrote:
> 
>> From: Adrian Hunter <ext-adrian.hunter@nokia.com>
>> Date: Wed, 14 Jan 2009 17:45:53 +0200
>> Subject: [PATCH] MMC: Add Extended CSD as a device attribute
>>
>> Extended CSD is a MMC card register.  The Card Identification
>> (CID) register and the Card-Specific Data (CSD) register are
>> already device attributes.  As increasingly interesting
>> fields are being added to Extended CSD, it seems reasonable to
>> add it too.  Note that SD cards do not have an Extended CSD
>> register, so it is MMC only.
>>
>> Signed-off-by: Adrian Hunter <ext-adrian.hunter@nokia.com>
>> ---
> 
> Well, this might be interesting for debugging, but I don't see anything
> of general interest for user space in there. What's your use case?

Yes it is mainly just debugging.  It was done as a device attribute for
consistency with the other card registers CID and CSD.

Would you prefer #ifdef CONFIG_MMC_DEBUG or debugfs?

  reply	other threads:[~2009-01-26  9:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 16:23 [PATCH] MMC: Add Extended CSD as a device attribute Adrian Hunter
2009-01-16  0:05 ` Andrew Morton
2009-01-16 10:41   ` Adrian Hunter
2009-01-24 20:45     ` Pierre Ossman
2009-01-26  9:16       ` Adrian Hunter [this message]
2009-02-02 19:26         ` Pierre Ossman

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=497D7F74.6050409@nokia.com \
    --to=ext-adrian.hunter@nokia.com \
    --cc=akpm@linux-foundation.org \
    --cc=drzeus-mmc@drzeus.cx \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox