Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Luca Weiss <luca.weiss@fairphone.com>
Subject: Re: [PATCH v3 1/9] dt-bindings: clk: qcom,dispcc-sm8x50: describe additional DP clocks
Date: Tue, 2 Apr 2024 08:20:13 +0200	[thread overview]
Message-ID: <681fb7a1-dbae-4b25-bd3a-27ecc9c7dac0@linaro.org> (raw)
In-Reply-To: <20240401-typec-fix-sm8250-v3-1-604dce3ad103@linaro.org>

On 01/04/2024 22:33, Dmitry Baryshkov wrote:
> On the affected Qualcomm platforms the display clock controller has
> additional DP input clocks, describe them in DT schema.
> 
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
>  .../bindings/clock/qcom,dispcc-sm8x50.yaml         | 28 ++++++++++++++++++++++
>  1 file changed, 28 insertions(+)
> 

Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Best regards,
Krzysztof


  reply	other threads:[~2024-04-02  6:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 20:33 [PATCH v3 0/9] arm64: dts: qcom: fix description of the Type-C signals Dmitry Baryshkov
2024-04-01 20:33 ` [PATCH v3 1/9] dt-bindings: clk: qcom,dispcc-sm8x50: describe additional DP clocks Dmitry Baryshkov
2024-04-02  6:20   ` Krzysztof Kozlowski [this message]
2024-04-01 20:33 ` [PATCH v3 2/9] arm64: dts: qcom: sc8180x: correct dispcc clocks Dmitry Baryshkov
2024-04-10 12:31   ` Konrad Dybcio
2024-04-01 20:33 ` [PATCH v3 3/9] arm64: dts: qcom: sm8250: describe HS signals properly Dmitry Baryshkov
2024-04-02  9:42   ` Bryan O'Donoghue
2024-04-02 10:33     ` Dmitry Baryshkov
2024-04-02 14:39   ` Konrad Dybcio
2024-04-01 20:33 ` [PATCH v3 4/9] arm64: dts: qcom: sm8250: add a link between DWC3 and QMP PHY Dmitry Baryshkov
2024-04-02 14:39   ` Konrad Dybcio
2024-04-01 20:33 ` [PATCH v3 5/9] arm64: dts: qcom: sc8180x: switch USB+DP QMP PHYs to new bindings Dmitry Baryshkov
2024-04-10 12:33   ` Konrad Dybcio
2024-04-01 20:33 ` [PATCH v3 6/9] arm64: dts: qcom: sc8180x: describe USB signals properly Dmitry Baryshkov
2024-04-02 14:39   ` Konrad Dybcio
2024-04-01 20:33 ` [PATCH v3 7/9] arm64: dts: qcom: sc8280xp: " Dmitry Baryshkov
2024-04-02 14:40   ` Konrad Dybcio
2024-04-01 20:33 ` [PATCH v3 8/9] arm64: dts: qcom: x1e80100: " Dmitry Baryshkov
2024-04-02 14:41   ` Konrad Dybcio
2024-04-24 12:46     ` Dmitry Baryshkov
2024-04-01 20:33 ` [PATCH v3 9/9] arm64: dts: qcom: sm8150-hdk: rename Type-C HS endpoints Dmitry Baryshkov
2024-04-02 14:41   ` Konrad Dybcio

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=681fb7a1-dbae-4b25-bd3a-27ecc9c7dac0@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=andersson@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.weiss@fairphone.com \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox