public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Reidel <adrian@travitia.xyz>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Charles Keepax <ckeepax@opensource.cirrus.com>,
	Richard Fitzgerald <rf@opensource.cirrus.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Srinivasa Rao Mandadapu <quic_srivasam@quicinc.com>,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux@mainlining.org, ~postmarketos/upstreaming@lists.sr.ht
Subject: Missing documentation for Audioreach topology files
Date: Mon, 19 Aug 2024 22:53:00 +0200	[thread overview]
Message-ID: <7721158.EvYhyI6sBW@ceres> (raw)

Hi everyone,

I am currently bringing up Xiaomi SM8450/SM8475 mobile phones and have a few 
working well enough to try and get the WCD and audio in general working. All 
is fine, until this:

[   35.366229] qcom-apm gprsvc:service:2:1: Direct firmware load for qcom/
sm8450/Xiaomi 12-tplg.bin failed with error -2
[   35.366244] qcom-apm gprsvc:service:2:1: tplg firmware loading qcom/sm8450/
Xiaomi 12-tplg.bin failed -2
[   35.366250] qcom-apm gprsvc:service:2:1: ASoC: error at 
snd_soc_component_probe on gprsvc:service:2:1: -2

After searching around a bit, I stumbled across this Linaro repository: 
https://git.codelinaro.org/linaro/qcomlt/audioreach-topology
Apparently you're supposed to write the topology in a M4-preprocessed file that 
gets turned into an ALSA UCM topology config and then compiled with alsatplg.
However, there is zero documentation on the preprocessor macros and how you're 
actually supposed to write the topology file. Am I missing something or is 
there no public documentation and tooling for how to use this kernel 
interface?

Best regards,
Jens



             reply	other threads:[~2024-08-19 21:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19 20:53 Jens Reidel [this message]
2024-08-19 20:58 ` Missing documentation for Audioreach topology files Krzysztof Kozlowski
2024-08-19 21:13   ` Jens Reidel

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=7721158.EvYhyI6sBW@ceres \
    --to=adrian@travitia.xyz \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=linux@mainlining.org \
    --cc=perex@perex.cz \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=quic_srivasam@quicinc.com \
    --cc=rf@opensource.cirrus.com \
    --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