From: Ruslan Bilovol <ruslan.bilovol@ti.com>
To: tony@atomide.com, linux@arm.linux.org.uk,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/2] ARM: OMAP2+: Export SoC information to userspace using SoC infrastructure
Date: Thu, 7 Feb 2013 00:50:47 +0200 [thread overview]
Message-ID: <1360191049-24017-1-git-send-email-ruslan.bilovol@ti.com> (raw)
Hi,
This patch series is an attempt to export some OMAP SoC
information (like name, revision etc.) to userspace.
The first patch does some unification of OMAP SoC
information representation in current sources.
Second patch adds exactly needed changes using
exists in Linux kernel SoC infrastructure.
-----------------------------------------
v3:
- reduced number of lines changed in the first patch (reusing
existent code)
-----------------------------------------
v2:
- changed cpu_* -> soc_* variable names
- rebased on top of 'omap-for-v3.9/soc' branch of tmlind/linux-omap tree
Ruslan Bilovol (2):
ARM: OMAP2+: SoC name and revision unification
ARM: OMAP2+: Export SoC information to userspace
arch/arm/mach-omap2/common.h | 8 ++++
arch/arm/mach-omap2/id.c | 95 ++++++++++++++++++++++++++++++++++++++----
arch/arm/mach-omap2/io.c | 1 +
arch/arm/plat-omap/Kconfig | 1 +
4 files changed, 97 insertions(+), 8 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-02-06 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 22:50 Ruslan Bilovol [this message]
2013-02-06 22:50 ` [PATCH v3 1/2] ARM: OMAP2+: SoC name and revision unification Ruslan Bilovol
2013-02-06 22:50 ` [PATCH v3 2/2] ARM: OMAP2+: Export SoC information to userspace Ruslan Bilovol
2013-02-11 17:56 ` Tony Lindgren
2013-02-13 14:17 ` Ruslan Bilovol
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=1360191049-24017-1-git-send-email-ruslan.bilovol@ti.com \
--to=ruslan.bilovol@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tony@atomide.com \
/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