From: Imran Khan <kimran@codeaurora.org>
To: lee.jones@linaro.org
Cc: arnd@arndb.de, bjorn.andersson@linaro.org,
Imran Khan <kimran@codeaurora.org>,
linux-kernel@vger.kernel.org (open list)
Subject: [RFC] base: soc: Add few more soc details in soc attribute
Date: Tue, 8 Nov 2016 18:17:25 +0530 [thread overview]
Message-ID: <1478609264-4131-1-git-send-email-kimran@codeaurora.org> (raw)
The commit adds three more fields in the generic soc attribute structure.
The vendor field provides information about SoC vendor, it may be argued
that vendor is more or less conveying the same information as family but
nonetheless there is nothing preventing two vendors from having similar
family names for their socs. Also family and vendor fields combined
together provide a more thorough information.
The serial_num field would contain serial number of the soc.
Lastly as the same soc can come from multiple foundries, involving
different processes, having a foundry_id field to convey this information
can be useful.
Signed-off-by: Imran Khan <kimran@codeaurora.org>
---
include/linux/sys_soc.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/linux/sys_soc.h b/include/linux/sys_soc.h
index 2739ccb..e2eadd8 100644
--- a/include/linux/sys_soc.h
+++ b/include/linux/sys_soc.h
@@ -13,6 +13,9 @@ struct soc_device_attribute {
const char *family;
const char *revision;
const char *soc_id;
+ const char *vendor;
+ const char *serial_num;
+ const char *foundry_id;
};
/**
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
reply other threads:[~2016-11-08 12:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1478609264-4131-1-git-send-email-kimran@codeaurora.org \
--to=kimran@codeaurora.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=lee.jones@linaro.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
Powered by JetHome