Re: [PATCHv5 0/3] Introduce the /proc/socinfo and use it to exportOMAP data
From: Saravana Kannan
Date: Mon Feb 28 2011 - 23:51:42 EST
On 02/28/2011 02:28 AM, Maxime Coquelin wrote:
On 02/16/2011 12:57 PM, Eduardo Valentin wrote:
I propose to refactor your patchset, moving from procfs to sysfs.
Eduardo, what has happened to this patchset?
Got forgotten :-(. Unfortunately I didn't pushed it hard enough.
>> to something under sysfs. Perhaps /sys/devices/soc or so?
Do you want help in picking it up and try to polish it up?
Yeah, but it would need a refactoring. IIRC, result of last discussion
was that we should not mess with /proc. So, maybe moving back
About the location of this new sysfs entry, where do you think it should
I propose to create a new directory named "soc" in /sys/devices/system/.
As platform vendors have several/different kind of IDs to export to
sysfs, I propose each vendor to create file entries related to their IDs
(eg. /sys/devices/system/soc/idcode for OMAP platforms).
I think the path /sys/devices/system/soc/ will work for the MSM too. I
would have ideally liked it to be /sys/devices/system/soc/msm,
/sys/devices/system/soc/omap, etc, but we can't get to pick names for
devices under a class. So, we can make do with /sys/devices/system/soc/.
However, I think we should have a common file entry to export the unique
ID of the platforms. Indeed, user-space applications should have a
unified way to get this kind of ID, regardless of the platform (eg.
I like the idea of have a common file across all implementations that
will let user space identify what implementation is exporting the other
files and how to interpret them.
I would like to propose an "arch" file to identify the arch the soc info
file are for. I'm guessing within an arch, the soc files would mostly be
the same? If there are other minor differences, we can let the arch
specific code deal with how the files are interpreted.
Does "arch" work for everyone?
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/