From: Imran Khan <kimran@codeaurora.org>
To: andy.gross@linaro.org
Cc: lee.jones@linaro.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, Imran Khan <kimran@codeaurora.org>
Subject: [RESEND,PATCH v7 0/2] soc: qcom: Add SoC info driver
Date: Wed, 4 Jan 2017 12:43:12 +0530 [thread overview]
Message-ID: <1483513992-10356-1-git-send-email-kimran@codeaurora.org> (raw)
This is patchset v7 which takes care of review comments
received for patchset v6. Resending the patch set as
the last one had a compilation error.
Major changes with respect to patch v6 are as below:
- Rather than showing string for h/w types, just show the
number obtained from SMEM. The reader of this number
is supposed to parse this into a human readable string
as this information may be different for different ODMs
- Create an attribute 'qcom_odm' depending on the presence
of corresponding property in SMEM DT entry. This information
can be used for ODM specific interpretation of SMEM socinfo
content
- Read machine value from DT, rather than using soc-id as index
in an ever increasing array of machine names
Imran Khan (2):
soc: qcom: Add SoC info driver
Documentation/ABI: Add ABI information for QCOM socinfo driver
Documentation/ABI/stable/sysfs-driver-qcom_socinfo | 147 ++++++
drivers/soc/qcom/Kconfig | 1 +
drivers/soc/qcom/Makefile | 3 +-
drivers/soc/qcom/smem.c | 5 +
drivers/soc/qcom/socinfo.c | 515 +++++++++++++++++++++
5 files changed, 670 insertions(+), 1 deletion(-)
create mode 100644 Documentation/ABI/stable/sysfs-driver-qcom_socinfo
create mode 100644 drivers/soc/qcom/socinfo.c
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2017-01-04 7:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 7:13 Imran Khan [this message]
2017-01-04 8:15 ` [RESEND,PATCH v7 0/2] soc: qcom: Add SoC info driver Lee Jones
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=1483513992-10356-1-git-send-email-kimran@codeaurora.org \
--to=kimran@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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