| 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
| ||
|
Date: Fri, 28 Oct 2022 12:58:11 -0400
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Bhupesh Sharma <bhupesh.sharma@...aro.org>,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org
Cc: agross@...nel.org, linux-arm-msm@...r.kernel.org,
daniel.lezcano@...aro.org, robh@...nel.org, andersson@...nel.org,
rafael@...nel.org, bhupesh.linux@...il.com
Subject: Re: [PATCH 3/4] dt-bindings: thermal: Add qcom,qmi-tmd-device and
qcom,tmd-device yaml bindings
On 12/09/2022 04:50, Bhupesh Sharma wrote:
> Add qcom,qmi-tmd-device and qcom,tmd-device yaml bindings.
>
> Qualcomm QMI based TMD cooling device(s) are used for various
> mitigations for remote subsystem(s) including remote processor
> mitigation, rail voltage restriction etc.
>
> Each child node represents one remote subsystem and each child
> of this subsystem in-turn represents separate TMD cooling device.
>
> Cc: daniel.lezcano@...aro.org
> Cc: rafael@...nel.org
> Cc: andersson@...nel.org
> Cc: robh@...nel.org
> Signed-off-by: Bhupesh Sharma <bhupesh.sharma@...aro.org>
> ---
> .../bindings/thermal/qcom,qmi-tmd-device.yaml | 78 +++++++++++
> .../bindings/thermal/qcom,tmd-device.yaml | 122 ++++++++++++++++++
> include/dt-bindings/thermal/qcom,tmd.h | 14 ++
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.
> 3 files changed, 214 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/thermal/qcom,qmi-tmd-device.yaml
> create mode 100644 Documentation/devicetree/bindings/thermal/qcom,tmd-device.yaml
> create mode 100644 include/dt-bindings/thermal/qcom,tmd.h
>
> diff --git a/Documentation/devicetree/bindings/thermal/qcom,qmi-tmd-device.yaml b/Documentation/devicetree/bindings/thermal/qcom,qmi-tmd-device.yaml
> new file mode 100644
> index 000000000000..dfda5b611a93
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/thermal/qcom,qmi-tmd-device.yaml
> @@ -0,0 +1,78 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/thermal/qcom,qmi-tmd-device.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
Drop quotes.
> +
> +title: Qualcomm QMI based thermal mitigation (TMD) cooling devices.
> +
> +maintainers:
> + - Bhupesh Sharma <bhupesh.sharma@...aro.org>
> +
> +description:
> + Qualcomm QMI based TMD cooling device(s) are used for various
> + mitigations for remote subsystem(s) including remote processor
> + mitigation, rail voltage restriction etc.
> +
> +properties:
> + $nodename:
> + const: qmi-tmd-devices
Why enforcing node name?
> +
> + compatible:
> + items:
> + - const: qcom,qmi-tmd-devices
> +
> + modem0:
Why 0? Do you think it will grow for more devices?
> + $ref: /schemas/thermal/qcom,tmd-device.yaml#
> +
> + adsp:
> + $ref: /schemas/thermal/qcom,tmd-device.yaml#
> +
> + cdsp:
> + $ref: /schemas/thermal/qcom,tmd-device.yaml#
> +
> + slpi:
> + $ref: /schemas/thermal/qcom,tmd-device.yaml#
> +
> +required:
> + - compatible
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/thermal/qcom,tmd.h>
> + qmi-tmd-devices {
> + compatible = "qcom,qmi-tmd-devices";
> +
> + modem0 {
> + qcom,instance-id = <MODEM0_INSTANCE_ID>;
> +
> + modem0_pa: tmd-device0 {
> + label = "pa";
> + #cooling-cells = <2>;
> + };
> +
> + modem0_proc: tmd-device1 {
> + label = "modem";
> + #cooling-cells = <2>;
> + };
> +
> + modem0_current: tmd-device2 {
> + label = "modem_current";
> + #cooling-cells = <2>;
> + };
> +
> + modem0_skin: tmd-device3 {
> + label = "modem_skin";
> + #cooling-cells = <2>;
> + };
> +
> + modem0_vdd: tmd-device4 {
> + label = "cpuv_restriction_cold";
> + #cooling-cells = <2>;
> + };
> + };
> + };
> +...
> diff --git a/Documentation/devicetree/bindings/thermal/qcom,tmd-device.yaml b/Documentation/devicetree/bindings/thermal/qcom,tmd-device.yaml
> new file mode 100644
> index 000000000000..38ac62f03376
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/thermal/qcom,tmd-device.yaml
> @@ -0,0 +1,122 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/thermal/qcom,tmd-device.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: Qualcomm thermal mitigation (TMD) cooling devices
> +
> +maintainers:
> + - Bhupesh Sharma <bhupesh.sharma@...aro.org>
> +
> +description:
> + Qualcomm thermal mitigation (TMD) cooling devices. Each child node
> + represents one remote subsystem and each child of this subsystem in-turn
> + represents separate cooling devices.
> +
> +properties:
> + $nodename:
> + pattern: "^(modem|adsp|cdsp|slpi[0-9])?$"
No need to enforce node name.
> +
> + qcom,instance-id:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description:
> + Remote subsystem QMI server instance id to be used for communicating with QMI.
> +
> +patternProperties:
> + "^tmd-device[0-9]?$":
> + type: object
> + description:
> + Subnodes indicating tmd cooling device of a specific category.
> + properties:
> + label:
> + maxItems: 1
> + description: |
> + Remote subsystem device identifier. Acceptable device names -
> + "pa" -> for pa cooling device,
> + "cpuv_restriction_cold" -> for vdd restriction,
> + "cx_vdd_limit" -> for vdd limit,
> + "modem" -> for processor passive cooling device,
> + "modem_current" -> for current limiting device,
> + "modem_bw" -> for bus bandwidth limiting device,
> + "cpr_cold" -> for cpr restriction.
Why these are acceptable and others are not? What does it mean here the
"acceptable"?
Best regards,
Krzysztof
Powered by blists - more mailing lists