From: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
To: Linus Walleij <linus.walleij@linaro.org>, Chris Ball <cjb@laptop.org>
Cc: Sebastian Rasmussen <sebras@gmail.com>, linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: debugfs: parse all ext_csd via debug_fs
Date: Mon, 21 Nov 2011 08:39:17 +0100 [thread overview]
Message-ID: <4ECA0025.6030700@st.com> (raw)
In-Reply-To: <CACRpkda0y7cOR4EfuGLoGnD_PS1gTWqN7UA74=s2mWmEHokQhQ@mail.gmail.com>
Hello Linus, Chris,
On 11/12/2011 2:12 AM, Linus Walleij wrote:
> On Tue, Oct 25, 2011 at 1:43 PM, Sebastian Rasmussen<sebras@gmail.com> wrote:
>> [Giuseppe]
>>> This patch enhances the debug information reported
>>> for the mmc card by parsing the extended CSD registers
>>> obviously according to all the current specifications.
>>
>> Does this belong kernel or in userspace? I'm not sure, and
>> I'm hoping that any of the old-timers here chime in on it.
>> Anyway I supply you with a few comments on you patch
>> below...
>
> Since it's in debugfs we can have it as verbose and whatever
> weird structure we wish. Userspace tools usually don't
> depend on debugfs ... except for some :-/ (see recent
> ftrace vs perf debates etc etc)
>
> To implement getting at this data in a future-proof way
> from userspace we should put it in sysfs.
>
> And if it was in sysfs we would have to follow the rule
> "one value per file" with files named after each CSD/etc
> field. Then to make that human-readable you would need
> a userspace tool, and preferrably it should also be
> documented in Documentation/ABI/testing/*
>
> And nothing really prevents us from doing both :-)
Thanks for all advice and review, I've not clear if at this stage the
patch will be added in mmc-next.
Just to summarize: the patch works in debugfs context so the parsing
doesn't break the sys rules. I agree with Chris this has to be
maintained for the next mmc standards but IMO we can pay this waiting
for having both a user-space application (mmc-tool) and the ext_csd in
/sys (after that the ext_csd in debugfs could be completely removed).
Let me know.
Best Regards
Giuseppe
>
> Yours,
> Linus Walleij
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2011-11-21 7:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 15:04 [PATCH] mmc: debugfs: parse all ext_csd via debug_fs Giuseppe CAVALLARO
2011-10-25 11:43 ` Sebastian Rasmussen
2011-10-26 11:27 ` Giuseppe CAVALLARO
2011-10-27 7:20 ` Giuseppe CAVALLARO
2011-10-27 14:19 ` Sebastian Rasmussen
2011-10-28 7:51 ` Giuseppe CAVALLARO
2011-11-12 1:21 ` Chris Ball
2011-11-12 10:25 ` Linus Walleij
2011-11-12 1:12 ` Linus Walleij
2011-11-21 7:39 ` Giuseppe CAVALLARO [this message]
2011-11-21 10:08 ` Linus Walleij
2011-12-06 5:52 ` Giuseppe CAVALLARO
2011-12-13 16:35 ` Chris Ball
2011-12-15 13:08 ` Giuseppe CAVALLARO
2011-10-27 7:16 ` [PATCH] mmc: debugfs: parse ext_csd via debug_fs (v2) Giuseppe CAVALLARO
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=4ECA0025.6030700@st.com \
--to=peppe.cavallaro@st.com \
--cc=cjb@laptop.org \
--cc=linus.walleij@linaro.org \
--cc=linux-mmc@vger.kernel.org \
--cc=sebras@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).