On 20-06-25, 12:24, Akhil P Oommen wrote:
> In some cases, an OPP may have multiple varients to describe the
> differences in the resources between SKUs. As an example, we may
> want to vote different peak bandwidths in different SKUs for the
> same frequency and the OPP node names can have an additional
> integer suffix to denote this difference like below:
>
> opp-666000000-0 {
> opp-hz = /bits/ 64 <666000000>;
> opp-level = <RPMH_REGULATOR_LEVEL_SVS_L1>;
> opp-peak-kBps = <8171875>;
> qcom,opp-acd-level = <0xa82d5ffd>;
> opp-supported-hw = <0xf>;
> };
>
> /* Only applicable for SKUs which has 666Mhz as Fmax */
> opp-666000000-1 {
> opp-hz = /bits/ 64 <666000000>;
> opp-level = <RPMH_REGULATOR_LEVEL_SVS_L1>;
> opp-peak-kBps = <16500000>;
> qcom,opp-acd-level = <0xa82d5ffd>;
> opp-supported-hw = <0x10>;
> };
>
> Update the regex to allow this usecase.
>
> Tested-by: Jens Glathe <[email protected]>
> Signed-off-by: Akhil P Oommen <[email protected]>
> ---
> Documentation/devicetree/bindings/opp/opp-v2-qcom-adreno.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/opp/opp-v2-qcom-adreno.yaml
> b/Documentation/devicetree/bindings/opp/opp-v2-qcom-adreno.yaml
> index
> a27ba7b663d456f964628a91a661b51a684de1be..0bd7d6b69755f5f53a045ba7b5e1d08030d980e6
> 100644
> --- a/Documentation/devicetree/bindings/opp/opp-v2-qcom-adreno.yaml
> +++ b/Documentation/devicetree/bindings/opp/opp-v2-qcom-adreno.yaml
> @@ -23,7 +23,7 @@ properties:
> const: operating-points-v2-adreno
>
> patternProperties:
> - '^opp-[0-9]+$':
> + '^opp(-[0-9]+){1,2}$':
> type: object
> additionalProperties: false
Acked-by: Viresh Kumar <[email protected]>
--
viresh
