From: Konrad Dybcio <konradybcio@kernel.org>
To: Luca Weiss <luca.weiss@fairphone.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Banajit Goswami <bgoswami@quicinc.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, alsa-devel@alsa-project.org,
linux-arm-msm@vger.kernel.org, linux-sound@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Add DisplayPort sound support for Fairphone 5 smartphone
Date: Sat, 10 Aug 2024 14:35:00 +0200 [thread overview]
Message-ID: <192e3c22-fd63-4891-86b2-89a3383ab76d@kernel.org> (raw)
In-Reply-To: <20240809-fp5-dp-sound-v1-0-d7ba2c24f6b9@fairphone.com>
On 9.08.2024 10:33 AM, Luca Weiss wrote:
> Add the necessary sound card bits and some dts additions to enable sound
> over DisplayPort-over-USB-C, e.g. to a connected TV or monitor.
>
> The UCM files can be found here:
> https://gitlab.com/postmarketOS/pmaports/-/tree/master/device/testing/device-fairphone-fp5/ucm
>
> Two extra notes:
>
> 1. I don't quite understand whether the sound driver should have
> SoC-specific compatible or device-specific compatible. Some earlier
> patches by another author for a QCM6490 board and a QCS6490 board use
> device-specific compatible - but from what I can tell this is not how
> it's generally done for other sound drivers?
>
> 2. Unfortunately DisplayPort enablement itself for Fairphone 5 is not
> upstream yet. This is blocked by DSI display bringup upstream which
> is blocked by DSC 1:1:1 not being supported upstream yet and just
> working with a hacky patch. Nevertheless, DisplayPort audio was
> validated working with no additional sound-related changes so once
> DisplayPort gets enabled, sound should also just work upstream.
You can enable DP and keep DSI disabled for the time being
Konrad
next prev parent reply other threads:[~2024-08-10 12:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 8:33 [PATCH 0/3] Add DisplayPort sound support for Fairphone 5 smartphone Luca Weiss
2024-08-09 8:33 ` [PATCH 1/3] ASoC: dt-bindings: qcom,sm8250: Add generic QCM6490 sound card Luca Weiss
2024-08-09 9:09 ` Krzysztof Kozlowski
2024-08-09 9:12 ` Luca Weiss
2024-08-09 9:13 ` Krzysztof Kozlowski
2024-08-09 8:33 ` [PATCH 2/3] ASoC: qcom: sc8280xp: Add support for generic QCM6490 Luca Weiss
2024-08-09 8:33 ` [PATCH 3/3] arm64: dts: qcom: qcm6490-fairphone-fp5: Add DisplayPort sound support Luca Weiss
2024-08-09 9:10 ` [PATCH 0/3] Add DisplayPort sound support for Fairphone 5 smartphone Krzysztof Kozlowski
2024-08-10 12:35 ` Konrad Dybcio [this message]
2024-08-10 13:30 ` Luca Weiss
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=192e3c22-fd63-4891-86b2-89a3383ab76d@kernel.org \
--to=konradybcio@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=andersson@kernel.org \
--cc=bgoswami@quicinc.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=perex@perex.cz \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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;
as well as URLs for NNTP newsgroup(s).