Devicetree
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Abel Vesa <abel.vesa@oss.qualcomm.com>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH RFC v2 1/3] arm64: dts: qcom: eliza: Add display (MDSS) with Display CC
Date: Wed, 22 Apr 2026 11:29:05 +0200	[thread overview]
Message-ID: <46c20e58-0e2d-4f91-8254-502e5b962299@oss.qualcomm.com> (raw)
In-Reply-To: <20260421-dts-qcom-eliza-display-v2-1-67f8cf155331@oss.qualcomm.com>

On 4/21/26 3:45 PM, Krzysztof Kozlowski wrote:
> Add device nodes for almost entire display: MDSS, DPU, DSI, DSI PHYs,
> DisplayPort and Display Clock Controller.
> 
> Missing pieces are HDMI PHY and HDMI controller.
> 
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> ---

Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>

Konrad

  reply	other threads:[~2026-04-22  9:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21 13:45 [PATCH RFC v2 0/3] arm64: dts: qcom: eliza: Add display Krzysztof Kozlowski
2026-04-21 13:45 ` [PATCH RFC v2 1/3] arm64: dts: qcom: eliza: Add display (MDSS) with Display CC Krzysztof Kozlowski
2026-04-22  9:29   ` Konrad Dybcio [this message]
2026-04-21 13:45 ` [PATCH RFC v2 2/3] arm64: dts: qcom: eliza-mtp: Enable DSI display panel Krzysztof Kozlowski
2026-04-22  9:29   ` Konrad Dybcio
2026-04-21 13:45 ` [PATCH RFC v2 3/3] arm64: dts: qcom: eliza-mtp: Enable DisplayPort on USB Krzysztof Kozlowski
2026-04-22  0:55   ` Dmitry Baryshkov
2026-04-22  9:30   ` 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=46c20e58-0e2d-4f91-8254-502e5b962299@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=abel.vesa@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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