Hi Greg,
On Mon, Dec 4, 2023 at 2:31 PM Greg Ungerer <gerg@xxxxxxxxxxxxxx> wrote:
A number of the ColdFire SoCs support reading the exact SoC type.
Read that at system startup and report the exact type whenever possible.
The early ColdFire parts had no way to self identify, so it is only the
newer families and their members that support some mechanism for reading
back a chip identifier. Unfortunately there is no consistent way to get
at that identifier. Some chips implement a Chip Identification Register,
though on some parts it is 16bits and on others 32bits. Some implement a
Device ID register, and others implement a JTAG identifier which can be
used to determine exact SoC. So probing of ID is specific to each family.
In many cases if we can read a chip ID we can also get a chip revision.
Read and report that as well when possible.
Signed-off-by: Greg Ungerer <gerg@xxxxxxxxxxxxxx>
Thanks for your series!
Are you aware of struct soc_device_attribute and soc_device_register()?
These can be used to register information about the SoC in the system,
expose it through /sys/devices/soc0/.
Drivers can also match against this using soc_device_match().
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
