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
| ||
|
Message-ID: <20220222030337.ijnfrh367illmidr@vireshk-i7> Date: Tue, 22 Feb 2022 08:33:37 +0530 From: Viresh Kumar <viresh.kumar@...aro.org> To: Lukasz Luba <lukasz.luba@....com> Cc: linux-kernel@...r.kernel.org, dietmar.eggemann@....com, rafael@...nel.org, daniel.lezcano@...aro.org, nm@...com, sboyd@...nel.org, mka@...omium.org, dianders@...omium.org, robh+dt@...nel.org, devicetree@...r.kernel.org, linux-pm@...r.kernel.org Subject: Re: [RFC][PATCH 1/2] dt-bindings: power: add Energy Model bindings On 21-02-22, 22:51, Lukasz Luba wrote: > Add DT bindings for the Energy Model information. > > Signed-off-by: Lukasz Luba <lukasz.luba@....com> > --- > .../bindings/power/energy-model.yaml | 51 +++++++++++++++++++ > 1 file changed, 51 insertions(+) > create mode 100644 Documentation/devicetree/bindings/power/energy-model.yaml > > diff --git a/Documentation/devicetree/bindings/power/energy-model.yaml b/Documentation/devicetree/bindings/power/energy-model.yaml > new file mode 100644 > index 000000000000..804a9b324925 > --- /dev/null > +++ b/Documentation/devicetree/bindings/power/energy-model.yaml > @@ -0,0 +1,51 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/power/energy-model.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Energy Model Bindings > + > +maintainers: > + - Lukasz Luba <lukasz.luba@....com> > + > +description: |+ > + Devices work at specific performance states (frequencies). The power which > + is used at a given performance state is an important information. A framework > + which maintains this information is Energy Model. This document defines > + bindings for these Energy Model performance states applicable across wide > + range of devices. For illustration purpose, this document uses GPU as a device. > + > + This binding only supports frequency-power pairs. > + > +select: true > + > +properties: > + operating-points: > + $ref: /schemas/types.yaml#/definitions/uint32-matrix > + items: > + items: > + - description: Frequency in kHz > + - description: Power in uW > + > + > +additionalProperties: true > +examples: > + { > + gpu_energy_model: energy-model { > + compatible = "energy-model"; > + energy-model-entries = < > + 200000 300000 > + 297000 500000 > + 400000 800000 > + 500000 1400000 > + 600000 2000000 > + 800000 2800000 > + >; > + }; > + }; > + > + &gpu { > + energy-model = <&gpu_energy_model>; > + }; What about getting this from the OPP table instead? There is no point adding similar tables for a device. -- viresh
Powered by blists - more mailing lists