From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
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>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Abel Vesa <abel.vesa@linaro.org>
Subject: Re: [PATCH v2 2/2] arm64: dts: qcom: x1e78100-t14s: Add audio playback over DisplayPort
Date: Wed, 17 Dec 2025 14:00:05 +0100 [thread overview]
Message-ID: <487ff592-e67c-41c8-a398-f79aa6e5f69c@kernel.org> (raw)
In-Reply-To: <47758ce9-5ec6-4ed6-9f84-13cbdd444d75@oss.qualcomm.com>
On 17/12/2025 13:51, Konrad Dybcio wrote:
> On 12/17/25 1:38 PM, Krzysztof Kozlowski wrote:
>> On 17/12/2025 13:33, Konrad Dybcio wrote:
>>> On 12/17/25 1:00 PM, Krzysztof Kozlowski wrote:
>>>> Add necessary DAI links and DAI name prefixes to enable audio playback
>>>> over USB/DisplayPort and HDMI. The HDMI port is not yet enabled, but it
>>>> should carry respective DAI name prefix regardless.
>>>>
>>>> Reviewed-by: Abel Vesa <abel.vesa@linaro.org>
>>>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
>>>>
>>>> ---
>>>
>>> (something's inserting a \n before --- in your latest patches but I
>>
>> No, it is not. It was always like that and only recently git started
>> dropping it, but it is irrelevant.
>>
>>> don't know if this is a problem)
>>>
>>> [...]
>>>
>>>> + displayport-2-dai-link {
>>>> + link-name = "DisplayPort2 Playback";
>>>> +
>>>> + codec {
>>>> + sound-dai = <&mdss_dp2>;
>>>
>>> How does this work out with fw_devlink?
>>
>> How is this related to this patchset? Please stop nit-picking irrelevant
>> things.
>
> I'm asking whether this is going to break sync_state because you're not
> enabling mdss_dp2 - I believe that's a fair question..
DTS description is independent of driver, thus this is correct code
regardless whether there is interconnect involved anywhere or not. I
don't have the answer how this affects interconnect, but I see no reason
anyone would create such ICC path - between hardware and fake SW construct.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-12-17 13:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 12:00 [PATCH v2 1/2] arm64: dts: qcom: hamoa: Add sound DAI prefixes for DP Krzysztof Kozlowski
2025-12-17 12:00 ` [PATCH v2 2/2] arm64: dts: qcom: x1e78100-t14s: Add audio playback over DisplayPort Krzysztof Kozlowski
2025-12-17 12:33 ` Konrad Dybcio
2025-12-17 12:38 ` Krzysztof Kozlowski
2025-12-17 12:51 ` Konrad Dybcio
2025-12-17 13:00 ` Krzysztof Kozlowski [this message]
2025-12-19 12:53 ` Konrad Dybcio
2025-12-19 12:57 ` Krzysztof Kozlowski
2025-12-19 12:59 ` Konrad Dybcio
2025-12-17 12:33 ` [PATCH v2 1/2] arm64: dts: qcom: hamoa: Add sound DAI prefixes for DP Konrad Dybcio
2025-12-17 14:49 ` Dmitry Baryshkov
2026-01-05 14:07 ` (subset) " 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=487ff592-e67c-41c8-a398-f79aa6e5f69c@kernel.org \
--to=krzk@kernel.org \
--cc=abel.vesa@linaro.org \
--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=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