mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ayushi Makhija <quic_amakhija@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: <linux-arm-msm@vger.kernel.org>,
	<dri-devel@lists.freedesktop.org>,
	<freedreno@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <robdclark@gmail.com>,
	<sean@poorly.run>, <marijn.suijten@somainline.org>,
	<andersson@kernel.org>, <robh@kernel.org>, <robh+dt@kernel.org>,
	<krzk+dt@kernel.org>, <konradybcio@kernel.org>,
	<conor+dt@kernel.org>, <andrzej.hajda@intel.com>,
	<neil.armstrong@linaro.org>, <rfoss@kernel.org>,
	<Laurent.pinchart@ideasonboard.com>, <jonas@kwiboo.se>,
	<jernej.skrabec@gmail.com>, <quic_rajeevny@quicinc.com>,
	<quic_vproddut@quicinc.com>, <quic_jesszhan@quicinc.com>
Subject: Re: [PATCH 2/3] arm64: dts: qcom: qcs8300: add Display Serial Interface device nodes
Date: Mon, 29 Sep 2025 12:07:58 +0530	[thread overview]
Message-ID: <fba96ad1-9a1f-40a7-981e-3c229439802f@quicinc.com> (raw)
In-Reply-To: <5irzdmwxs2j4ppti35hc5235yxqq576doerrrk6fhcpj7f726a@eh5rl2jwb5kg>



On 9/26/2025 7:35 PM, Dmitry Baryshkov wrote:
> On Fri, Sep 26, 2025 at 02:55:19PM +0530, Ayushi Makhija wrote:
>> On 9/26/2025 3:32 AM, Dmitry Baryshkov wrote:
>>> On Thu, Sep 25, 2025 at 11:06:01AM +0530, Ayushi Makhija wrote:
>>>> Add device tree nodes for the DSI0 controller with their corresponding
>>>> PHY found on Qualcomm QCS8300 SoC.
>>>>
>>>> Signed-off-by: Ayushi Makhija <quic_amakhija@quicinc.com>
>>>> ---
>>>>  arch/arm64/boot/dts/qcom/qcs8300.dtsi | 95 ++++++++++++++++++++++++++-
>>>>  1 file changed, 94 insertions(+), 1 deletion(-)
>>>>
>>>> +
>>>> +			mdss_dsi0_phy: phy@ae94400 {
>>>> +				compatible = "qcom,sa8775p-dsi-phy-5nm";
>>>
>>> Add qcs8300-specific compatible and use sa8775p as a fallback
>>>
>>
>> Hi Dmitry,
>>
>> I have one doubt, even though the ctrl and phy versions for sa8775p(LeMans) and qcs8300(Monaco) are same.
>> Why can't we use the same compatible string that we have used for LeMans ctrl and phy ? what is the need to define a separate
>> compatible string for monaco ctrl and phy ?
> 
> Konrad responded with the reason. But also, this question should have
> been asked when you took a first look at the qcom,qcs8300-mdss.yaml.
> It has two compats for DPU, DP and eDP PHY blocks (for exactly the same
> reason).
> 

Hi Dmitry/Konard,

The previous explanation regarding the use of two compatible strings for DPU/DP was unclear, but it is now well understood. Thanks, for the clarification. 

Thanks,
Ayushi


  reply	other threads:[~2025-09-29  6:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-25  5:35 [PATCH 0/3] Add DSI display support for QCS8300 target Ayushi Makhija
2025-09-25  5:36 ` [PATCH 1/3] dt-bindings: display: msm: document DSI controller and phy on QCS8300 Ayushi Makhija
2025-09-25 21:59   ` Dmitry Baryshkov
2025-09-25  5:36 ` [PATCH 2/3] arm64: dts: qcom: qcs8300: add Display Serial Interface device nodes Ayushi Makhija
2025-09-25 22:02   ` Dmitry Baryshkov
2025-09-26  9:25     ` Ayushi Makhija
2025-09-26 10:45       ` Konrad Dybcio
2025-09-26 14:05       ` Dmitry Baryshkov
2025-09-29  6:37         ` Ayushi Makhija [this message]
2025-10-05 16:48     ` Ayushi Makhija
2025-10-05 22:01       ` Dmitry Baryshkov
2025-10-05 23:53         ` Ayushi Makhija
2025-09-25  5:36 ` [PATCH 3/3] arm64: dts: qcom: qcs8300-ride: add anx7625 DSI to DP bridge node Ayushi Makhija
2025-09-25 22:03   ` Dmitry Baryshkov

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=fba96ad1-9a1f-40a7-981e-3c229439802f@quicinc.com \
    --to=quic_amakhija@quicinc.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=andersson@kernel.org \
    --cc=andrzej.hajda@intel.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=neil.armstrong@linaro.org \
    --cc=quic_jesszhan@quicinc.com \
    --cc=quic_rajeevny@quicinc.com \
    --cc=quic_vproddut@quicinc.com \
    --cc=rfoss@kernel.org \
    --cc=robdclark@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=sean@poorly.run \
    /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

all inboxes | Powered by JetHome®