[RFC PATCHv2 1/2] Export SoC info through sysfs

Nicolas Pitre nicolas.pitre at linaro.org
Thu Apr 7 18:45:29 EDT 2011


On Fri, 8 Apr 2011, Ryan Mallon wrote:

> On 04/08/2011 10:01 AM, Nicolas Pitre wrote:
> > On Fri, 8 Apr 2011, Ryan Mallon wrote:
> > 
> >> On 04/08/2011 09:29 AM, Arnd Bergmann wrote:
> >>> I'll try to capture the opinions from the other people as well,
> >>> hopefully this represents a consensus. Please correct me otherwise.
> >>>
> >>> I believe the uncontroversial parts are:
> >>>
> >>> * Make it not an entry but a device with certain properties.
> >>> * Make the naming so that you can have more than one of them.
> >>> * Put all devices on an SoC that uses this scheme underneath that
> >>>   device by setting their parents to the SoC device.
> >>>
> >>> For the location of the device, I have not seen a clear consensus yet,
> >>> but I'm fine with eihter of these:
> >>>
> >>> /sys/devices/soc/${NAME}/
> >>> /sys/devices/platform/soc${NUMBER}/
> >>
> >> I prefer the second format here since the path is always the same which
> >> makes it easier to write parsing tools. The name should be an entry in
> >> the directory rather than the name of the directory itself.
> >>
> >> Probably SoC number should match CPU number for SMP machines right?
> > 
> > Not really.  SOC means System On Chip.  you usually have only one SOC on 
> > a board, and within that SOC you may have one or more CPUs.  SMP 
> > machines are still likely to have only one SOC.
> 
> Ok. What is the situation where we have more than one SoC?

That would mean two separate instances of Linux, just like two systems.  
SMP across multiple SOCs doesn't make much sense, and I don't think they 
are likely to be designed for that ability either.


Nicolas



More information about the linux-arm-kernel mailing list