lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-Id: <1478609264-4131-1-git-send-email-kimran@codeaurora.org>
Date:   Tue,  8 Nov 2016 18:17:25 +0530
From:   Imran Khan <kimran@...eaurora.org>
To:     lee.jones@...aro.org
Cc:     arnd@...db.de, bjorn.andersson@...aro.org,
        Imran Khan <kimran@...eaurora.org>,
        linux-kernel@...r.kernel.org (open list)
Subject: [RFC] base: soc: Add few more soc details in soc attribute

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@...eaurora.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ