linux-kernel - Re: [PATCH v8 2/2] Documentation/ABI: Add ABI information for QCOM socinfo driver

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 17 Feb 2017 14:36:39 -0800
From:   Stephen Boyd <sboyd@...eaurora.org>
To:     Imran Khan <kimran@...eaurora.org>
Cc:     andy.gross@...aro.org, david.brown@...aro.org,
        linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
        linux-soc@...r.kernel.org
Subject: Re: [PATCH v8 2/2] Documentation/ABI: Add ABI information for QCOM
 socinfo driver

On 01/10, Imran Khan wrote:
> The socinfo ABI document describes the information provided
> by socinfo driver and the corresponding attributes to access
> that information.
> 
> Signed-off-by: Imran Khan <kimran@...eaurora.org>
> ---
>  Documentation/ABI/stable/sysfs-driver-qcom_socinfo | 147 +++++++++++++++++++++

Perhaps move it to testing instead of stable too?

>  1 file changed, 147 insertions(+)
>  create mode 100644 Documentation/ABI/stable/sysfs-driver-qcom_socinfo
> 
> diff --git a/Documentation/ABI/stable/sysfs-driver-qcom_socinfo b/Documentation/ABI/stable/sysfs-driver-qcom_socinfo
> new file mode 100644
> index 0000000..f90c142
> --- /dev/null
> +++ b/Documentation/ABI/stable/sysfs-driver-qcom_socinfo
> @@ -0,0 +1,147 @@
> +What:		/sys/devices/soc0/accessory_chip
> +Date:		January 2017
> +Description:
> +		This file shows the id of the accessory chip.

Please add a contact, linux-arm-msm@...r.kernel.org perhaps?

> +
> +What:		/sys/devices/soc0/adsp_image_crm
> +What:		/sys/devices/soc0/adsp_image_variant
> +What:		/sys/devices/soc0/adsp_image_version
> +Date:		January 2017
> +Description:
> +		These files respectively show the crm version, variant and
> +		version of the ADSP image.
> +
> +What:		/sys/devices/soc0/apps_image_crm
> +What:		/sys/devices/soc0/apps_image_variant
> +What:		/sys/devices/soc0/apps_image_version
> +Date:		January 2017
> +Description:
> +		These files respectively show the crm version, variant and
> +		version of the APPS(Linux kernel, rootfs) image.
> +
> +What:		/sys/devices/soc0/boot_image_crm
> +What:		/sys/devices/soc0/boot_image_variant
> +What:		/sys/devices/soc0/boot_image_version
> +Date:		January 2017
> +Description:
> +		These files respectively show the crm version, variant and
> +		version of the Boot(bootloader) image.
> +
> +What:		/sys/devices/soc0/build_id
> +Date:		January 2017
> +Description:
> +		This file shows the unique id of current build being used on
> +		the system.
> +
> +What:		/sys/devices/soc0/cnss_image_crm
> +What:		/sys/devices/soc0/cnss_image_variant
> +What:		/sys/devices/soc0/cnss_image_version
> +Date:		January 2017
> +Description:
> +		These files respectively show the crm version, variant and
> +		version of the CNSS image.
> +
> +What:		/sys/devices/soc0/family
> +Date:		January 2017
> +Description:
> +		This file shows the family(e.g Snapdragon) of the SoC.
> +
> +What:		/sys/devices/soc0/foundry_id
> +Date:		January 2017
> +Description:
> +		This file shows the id of the foundry, where soc was
> +		manufactured.
> +
> +What:		/sys/devices/soc0/hw_platform
> +Date:		January 2017
> +Description:
> +		This file shows the type of hardware platform
> +		(e.g MTP, QRD etc) where SoC is being used.
> +
> +What:		/sys/devices/soc0/machine
> +Date:		January 2017
> +Description:
> +		This file shows the machine name as given in the DT.
> +
> +What:		/sys/devices/soc0/mpss_image_crm
> +What:		/sys/devices/soc0/mpss_image_variant
> +What:		/sys/devices/soc0/mpss_image_version
> +Date:		January 2017
> +Description:
> +		These files respectively show the crm version, variant and
> +		version of the MPSS image.
> +
> +What:		/sys/devices/soc0/platform_subtype
> +Date:		January 2017
> +Description:
> +		This file shows the sub-type of hardware platform
> +		(SKUAA, SKUF etc.) where SoC is being used.
> +
> +What:		/sys/devices/soc0/platform_version
> +Date:		January 2017
> +Description:
> +		This file show the version of the hardware platform.
> +
> +What:		/sys/devices/soc0/pmic_die_revision
> +Date:		January 2017
> +Description:
> +		This file shows revision of PMIC die.
> +
> +What:		/sys/devices/soc0/pmic_model
> +Date:		January 2017
> +Description:
> +		This file shows name of PMIC model.

This doesn't seem very future proof when there's more than on
pmic, and really pmic isn't part of the SoC so it's sort of odd
to have that here in the first place. Any chance we can drop this
for now?

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project