public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Kumar Anurag Singh <kumar.singh@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@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
Subject: Re: [PATCH v1] arm64: dts: qcom: lemans: Enable DISPLAY-PORT
Date: Tue, 14 Apr 2026 11:11:50 +0530	[thread overview]
Message-ID: <ce8ca265-24df-41e5-a763-f9475de2fa9b@oss.qualcomm.com> (raw)
In-Reply-To: <579913ed-4fc9-4eee-9093-13b1f701e018@oss.qualcomm.com>

On 4/13/2026 2:14 PM, Konrad Dybcio wrote:
> On 4/13/26 6:37 AM, Kumar Anurag wrote:
>> Add dailinks for DISPLAY-PORT to enable audio functionality
>> on edp0.
> "DisplayPort"
> 
> The commit title is misleading.
> 
We will change the commit title :
From: arm64: dts: qcom: lemans: Enable DISPLAY-PORT
to : arm64: dts: qcom: lemans: Enable audio playback over DisplayPort
> [...]
> 
>> +		dp0-dai-link {
>> +			link-name = "DisplayPort0 Playback";
>> +
>> +			cpu {
>> +				sound-dai = <&q6apmbedai DISPLAY_PORT_RX_0>;
>> +			};
>> +
>> +			codec {
>> +				sound-dai = <&mdss0_dp0>;
>> +			};
> 'co'dec < 'cp'u, please re-sort
> 
> Konrad

In the other Dai links the cpu is before codec and hence we maintain the 
same order in dp0 dai link too.

Same pattern is observed in DTS of all qcom platforms.

Thanks & Regards
Anurag

      reply	other threads:[~2026-04-14  5:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13  4:37 [PATCH v1] arm64: dts: qcom: lemans: Enable DISPLAY-PORT Kumar Anurag
2026-04-13  8:44 ` Konrad Dybcio
2026-04-14  5:41   ` Kumar Anurag Singh [this message]

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=ce8ca265-24df-41e5-a763-f9475de2fa9b@oss.qualcomm.com \
    --to=kumar.singh@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --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