All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Gerhold <stephan.gerhold@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Abel Vesa <abel.vesa@linaro.org>,
	Johan Hovold <johan@kernel.org>
Subject: Re: [PATCH 0/9] arm64: dts: qcom: x1: Disable audio codecs by default
Date: Thu, 14 Aug 2025 10:50:24 +0200	[thread overview]
Message-ID: <aJ2jUDaBAgeRcYfz@linaro.org> (raw)
In-Reply-To: <c4a63197-9fef-4261-a0e0-9d57e009263a@linaro.org>

On Thu, Aug 14, 2025 at 08:07:17AM +0200, Krzysztof Kozlowski wrote:
> On 14/08/2025 01:09, Konrad Dybcio wrote:
> > On 8/13/25 5:58 PM, Stephan Gerhold wrote:
> >> Currently, the macro audio codecs are enabled by default in x1e80100.dtsi.
> >> However, they do not probe without the ADSP remoteproc, which is disabled
> >> by default.
> > 
> > FWIW if the ADSP doesn't start, you can't really consider the platform
> > working.. It just does oversees too much of the SoC to even seriously
> > consider using the device without it
> 
> 
> I agree. ADSP is supposed to come up for every or almost every platform,
> because it is crucial for USB and charging.
> 

I agree with that as well, especially because I have an upcoming patch
series that allows reusing the "lite" ADSP firmware from UEFI for USB
and charging, so you don't even need to have firmware present for that.

The question for this patch series is separate though: Should we enable
the SoC audio codecs by default? What happens if a board does not make
use of them?

> It's true that LPASS macro codec nodes need resources from ADSP, but
> still these are resources internal to the SoC. We disable nodes in DTI
> which need an external resource. That's not really the case for LPASS.

The reason that triggered this patch series is that I was seeing an
error from the va_macro when testing on x1e001de-devkit. That board does
not have DMICs defined, so it doesn't make direct use of the va_macro:

 va_macro 6d44000.codec: qcom,dmic-sample-rate dt entry missing

We should fix this in the lpass-va-macro driver. You could take this
case one step further though: What if a board uses none of the audio
functionality? Apparently, X1E is also going to be an IoT platform. It's
very well possible we will end up with a board that doesn't have any
audio functionality. I would argue it's valid to use a minimal kernel
config in that case that has all of the audio subsystem disabled. That
won't work though, since we need to probe all the enabled audio codecs
to reach sync_state().

This might be a Linux issue unrelated to the device tree, but in my
opinion an audio codec without audio inputs/outputs is not
"operational", it should not be status = "okay". That's quite subjective
though.

At the end, I realized that x1e001de-devkit actually does have DMICs and
I just need to enable them properly to get rid of the error. I only sent
this series because I believe it fits better to our conventions. Given
that I don't need it anymore, I'm also happy to just drop it. Let me
know what you prefer.

Thanks,
Stephan

  reply	other threads:[~2025-08-14  8:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-13 15:58 [PATCH 0/9] arm64: dts: qcom: x1: Disable audio codecs by default Stephan Gerhold
2025-08-13 15:58 ` [PATCH 1/9] arm64: dts: qcom: x1-asus-zenbook-a14: Explicitly enable used audio codecs Stephan Gerhold
2025-08-13 15:58 ` [PATCH 2/9] arm64: dts: qcom: x1-crd: " Stephan Gerhold
2025-08-13 15:59 ` [PATCH 3/9] arm64: dts: qcom: x1e001de-devkit: " Stephan Gerhold
2025-08-13 15:59 ` [PATCH 4/9] arm64: dts: qcom: x1e78100-lenovo-thinkpad-t14s: " Stephan Gerhold
2025-08-13 15:59 ` [PATCH 5/9] arm64: dts: qcom: x1e80100-hp-omnibook-x14: " Stephan Gerhold
2025-08-13 15:59 ` [PATCH 6/9] arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: " Stephan Gerhold
2025-08-13 15:59 ` [PATCH 7/9] arm64: dts: qcom: x1e80100-microsoft-romulus: " Stephan Gerhold
2025-08-13 15:59 ` [PATCH 8/9] arm64: dts: qcom: x1e80100-qcp: " Stephan Gerhold
2025-08-13 15:59 ` [PATCH 9/9] arm64: dts: qcom: x1e80100: Disable audio codecs by default Stephan Gerhold
2025-08-13 23:09 ` [PATCH 0/9] arm64: dts: qcom: x1: " Konrad Dybcio
2025-08-14  6:07   ` Krzysztof Kozlowski
2025-08-14  8:50     ` Stephan Gerhold [this message]
2025-08-14  9:22       ` Konrad Dybcio
2025-08-14  0:10 ` Alexey Klimov

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=aJ2jUDaBAgeRcYfz@linaro.org \
    --to=stephan.gerhold@linaro.org \
    --cc=abel.vesa@linaro.org \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=johan@kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.