Introduce the /proc/socinfo and use it to export OMAP data
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v5 Latest posting 3/30 of 3 patches 0 repliesNew
- v5 posting 2/30 of 3 patches 6 repliesSuperseded
- v5 posting 1/30 of 3 patches 0 repliesSuperseded
Patches in v5 posting 3/3 No applies recorded yet
None of the 3 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v5 yet.
Cover letter [PATCHv5 0/3] Introduce the /proc/socinfo and use it to export OMAP data
Quoted 32 lines · Maxime Coquelin
Quoted 17 lines · Ryan Mallon
Quoted 12 lines · Saravana Kannan
Quoted 6 lines · Ryan Mallon
The only real objection I have to adding the SoC family information is basically to discourage it being abused by userspace. I can see it being
useful in debug situations, but I can also see stupid userspace applications explicitly testing for some particular SoC, rather than more correctly (IMHO) checking for presence of certain drivers etc.True, but so many other things could be misused by stupid userspace programs. When there are legitimate usecases, I think we shouldn't prevent them just because we think a stupid userspace program could misuse it.
Quoted 4 lines
Again, although you might not be gung-ho about this, I think I have at least made you indifferent/mildly supportive to adding socinfo. If you don't mind, I would like to wait for others to chime in before continuing this discussion.
Quoted 7 lines
Agreed.
In general I am in support of having the SoC information exposed somewhere. I think we just want to be careful that it doesn't become a dumping ground for anything and everything SoC related whether the information is useful or not. I think each piece of exposed information should have a genuine use case, not just "because we can".
I definitely agree we should not export every SoC-related information just because we can do it.
The first goal of this interface was to export some SoCs IDs, as we need this kind of information for some user-space tools.
Does someone need to export other information than the mach name and some IDs?
Quoted 2 lines
As proposed in my previous mail, do you agree to have a unified file for all vendors, which exports the unique silicon ID of the chip?
As mentioned earlier, on ep93xx we would like to export the Maverick Crunch ID, which is a unique identifier for the chip.
I think the ABI should specify a minimum set of values which are guaranteed to be provided on all SoCs, but allow individual SoCs to provide additional information as necessary.
~Ryan
Signature · 7 lines
Bluewater Systems Ltd - ARM Technology Solution Centre Ryan Mallon 5 Amuri Park, 404 Barbadoes St ryan at bluewatersys.com PO Box 13 889, Christchurch 8013 http://www.bluewatersys.com New Zealand Phone: +64 3 3779127 Freecall: Australia 1800 148 751 Fax: +64 3 3779135 USA 1800 261 2934