[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKYAXd9Q99BSrAfLDe+DK4cYyz7K5JLGvcMnSsE6pSrkEpOTjQ@mail.gmail.com>
Date: Tue, 20 Sep 2011 08:51:04 +0900
From: NamJae Jeon <linkinjeon@...il.com>
To: Andrei Warkentin <awarkentin@...are.com>
Cc: linux-kernel@...r.kernel.org, cjb@...top.org,
linux-mmc@...r.kernel.org
Subject: Re: [PATCH] mmc : export hw reset function info to user
2011/9/20 Andrei Warkentin <awarkentin@...are.com>:
> Hi Namjae, others,
>
> ----- Original Message -----
>> From: "Namjae Jeon" <linkinjeon@...il.com>
>> To: cjb@...top.org, linux-mmc@...r.kernel.org
>> Cc: linux-kernel@...r.kernel.org, "Namjae Jeon" <linkinjeon@...il.com>
>> Sent: Sunday, September 18, 2011 11:20:25 AM
>> Subject: [PATCH] mmc : export hw reset function info to user
>>
>> user app should know whether hw reset function is enable to use it.
>> so I try to add sysfs file of hw reset function like enhanced area.
>>
>
> If we're going to be adding a bunch of attributes from ext_csd, why not
> just allow dumping the entire ext_csd in a semi-readable form? Via something like
> hex_dump_to_buffer. This will allow easy human an machine parsing, and be more
> lightweight then adding a sysfs attr for each EXT_CSD byte (of which there are a lot).
>
> I'm basing this on the thought that the only clients of these attrbutes would
> either be developers or engineers involved with MMC media, or very specialized
> software.
>
> Thoughts?
>
> A
>
Hi. Andrei.
We can see all dump of ext_csd by using debugfs like this.
mount -t debugfs /dev/mmcblk0 /mnt/
cat /mnt/mmc0/mmc0\:0001/ext_csd
If user take care of it by showing all dump of ext_csd, we may be
comfortable more without having to worry.
But most of them that they do not know a lot of information.
If we provide some information they need them user friendly, I think
that user can use more easily mmc.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists