From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] ARM: vf610: Add SoC bus support for Vybrid
Date: Wed, 20 May 2015 09:12:08 +0200 [thread overview]
Message-ID: <9691074.oWRy1bscbz@wuerfel> (raw)
In-Reply-To: <27733a88b73adb7000205e020bafdb6f7ebe1843.1432099651.git.maitysanchayan@gmail.com>
On Wednesday 20 May 2015 11:06:52 Sanchayan Maity wrote:
> Implements SoC bus support to export SoC specific information. Read
> the unique SoC ID from the Vybrid On Chip One Time Programmable
> (OCOTP) controller, SoC specific information from the Miscellaneous
> System Control Module (MSCM), revision from the ROM revision register
> and expose it via the SoC bus infrastructure.
>
> Sample Output:
>
> root at vf:/sys/devices/soc0# cat soc_id
> df63c12a2e2161d4
> root at vf:/sys/devices/soc0# cat family
> Freescale Vybrid VF500
> root at vf:/sys/devices/soc0# cat revision
> 00000013
> root at vf:/sys/devices/soc0# cat machine
> Freescale Vybrid
>
I would prefer to see this as a driver in drivers/soc that registers
to a platform device. Is there any DT node that would be a reasonable
device to bind to?
Arnd
next prev parent reply other threads:[~2015-05-20 7:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 5:36 [PATCH v2 0/2] Implement SoC bus support for Vybrid Sanchayan Maity
2015-05-20 5:36 ` [PATCH v2 1/2] ARM: dts: vfxxx: Add OCOTP and OCROM nodes Sanchayan Maity
2015-05-20 5:36 ` [PATCH v2 2/2] ARM: vf610: Add SoC bus support for Vybrid Sanchayan Maity
2015-05-20 7:12 ` Arnd Bergmann [this message]
2015-05-20 7:36 ` Stefan Agner
2015-05-20 8:18 ` Arnd Bergmann
2015-05-20 6:08 ` [PATCH v2 0/2] Implement " Stefan Agner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9691074.oWRy1bscbz@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox