linux-kernel - Re: [PATCH v4 1/2] dt-bindings: clock: add QCOM SM8150 and SM8250 display clock bindings

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200928190104.GA3082359@bogus>
Date:   Mon, 28 Sep 2020 14:01:04 -0500
From:   Rob Herring <robh@...nel.org>
To:     Jonathan Marek <jonathan@...ek.ca>
Cc:     Rob Herring <robh+dt@...nel.org>, Andy Gross <agross@...nel.org>,
        Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
        linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
        devicetree@...r.kernel.org,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        linux-clk@...r.kernel.org,
        Michael Turquette <mturquette@...libre.com>,
        Stephen Boyd <sboyd@...nel.org>
Subject: Re: [PATCH v4 1/2] dt-bindings: clock: add QCOM SM8150 and SM8250
 display clock bindings

On Sun, 27 Sep 2020 15:06:50 -0400, Jonathan Marek wrote:
> Add device tree bindings for display clock controller for
> Qualcomm Technology Inc's SM8150 and SM8250 SoCs.
> 
> Signed-off-by: Jonathan Marek <jonathan@...ek.ca>
> Tested-by: Dmitry Baryshkov <dmitry.baryshkov@...aro.org> (SM8250)
> ---
>  .../bindings/clock/qcom,dispcc-sm8x50.yaml    | 93 +++++++++++++++++++
>  .../dt-bindings/clock/qcom,dispcc-sm8150.h    |  1 +
>  .../dt-bindings/clock/qcom,dispcc-sm8250.h    | 66 +++++++++++++
>  3 files changed, 160 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/clock/qcom,dispcc-sm8x50.yaml
>  create mode 120000 include/dt-bindings/clock/qcom,dispcc-sm8150.h
>  create mode 100644 include/dt-bindings/clock/qcom,dispcc-sm8250.h
> 

Reviewed-by: Rob Herring <robh@...nel.org>