Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Jeffrey Hugo <quic_jhugo@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	"Stephen Boyd" <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Taniya Das <quic_tdas@quicinc.com>
Cc: Rob Clark <robdclark@gmail.com>, <linux-arm-msm@vger.kernel.org>,
	<linux-clk@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] dt-bindings: clock: qcom,mmcc: support LVDS PLL input for apq8064
Date: Sun, 12 Jan 2025 10:48:35 -0700	[thread overview]
Message-ID: <9bf72460-48d0-e83f-9ef5-bb6bbd95828e@quicinc.com> (raw)
In-Reply-To: <20241224-apq8064-fix-mmcc-v1-1-c95d2e2bf143@linaro.org>

On 12/24/2024 3:12 AM, Dmitry Baryshkov wrote:
> APQ8064 / MSM8960 have separate LVDS PLL driving the LVDS / LCDC clock.
> Add corresponding input to clock controller bindings.
> 
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>

Acked-by: Jeffrey Hugo <quic_jhugo@quicinc.com>

  parent reply	other threads:[~2025-01-12 17:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-24 10:12 [PATCH 0/4] clk: qcom: mmcc-msm8960: add support for the LVDS clock Dmitry Baryshkov
2024-12-24 10:12 ` [PATCH 1/4] dt-bindings: clock: qcom,mmcc: support LVDS PLL input for apq8064 Dmitry Baryshkov
2024-12-28 10:31   ` Krzysztof Kozlowski
2025-01-12 17:48   ` Jeffrey Hugo [this message]
2024-12-24 10:12 ` [PATCH 2/4] dt-bindings: clock: qcom,mmcc-msm8960: add LCDC-related clocks Dmitry Baryshkov
2024-12-28 10:31   ` Krzysztof Kozlowski
2024-12-24 10:12 ` [PATCH 3/4] clk: qcom: rcg: add 1/1 pixel clock ratio Dmitry Baryshkov
2024-12-24 10:12 ` [PATCH 4/4] clk: qcom: mmcc-msm8960: handle LVDS clock Dmitry Baryshkov
2025-01-07 16:38 ` [PATCH 0/4] clk: qcom: mmcc-msm8960: add support for the " Bjorn Andersson

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=9bf72460-48d0-e83f-9ef5-bb6bbd95828e@quicinc.com \
    --to=quic_jhugo@quicinc.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=quic_tdas@quicinc.com \
    --cc=robdclark@gmail.com \
    --cc=robh@kernel.org \
    --cc=sboyd@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