From: Srinivas Kandagatla <srini@kernel.org>
To: Jorijn van der Graaf <jorijnvdgraaf@catcrafts.net>,
Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>,
Srinivas Kandagatla <srini@kernel.org>,
Mark Brown <broonie@kernel.org>,
Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Val Packett <val@packett.cool>,
Luca Weiss <luca.weiss@fairphone.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Jianfeng Liu <liujianfeng1994@gmail.com>,
linux-sound@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] ASoC: qcom: q6apm-lpass-dais: start the graph at prepare
Date: Thu, 23 Jul 2026 00:02:59 +0100 [thread overview]
Message-ID: <2545fdff-7bfc-4897-9185-34c45ee01bdc@kernel.org> (raw)
In-Reply-To: <20260715211919.49462-1-jorijnvdgraaf@catcrafts.net>
On 7/15/26 10:19 PM, Jorijn van der Graaf wrote:
>
>> This week, I will try to pull some wires out and check that on my
>> hardware too.
> That comparison should tell us which side to look at. If your board
> does drive the bit clock from the vote alone, I am happy to dig on
sorry for the delay,
I see same results as yours on my VENTUNO Q board too.
As per DSP team it should work, let me dig bit more and see if I can
find what it takes to enable it.
--srini
> the milos side; any pointer on what to check next would be welcome.
next prev parent reply other threads:[~2026-07-22 23:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 3:38 [RFC PATCH] ASoC: qcom: q6apm-lpass-dais: start the graph at prepare Jorijn van der Graaf
2026-07-08 14:05 ` Mark Brown
2026-07-08 21:55 ` Jorijn van der Graaf
2026-07-08 22:18 ` Srinivas Kandagatla
2026-07-10 14:32 ` Jorijn van der Graaf
2026-07-14 16:22 ` Srinivas Kandagatla
2026-07-15 21:19 ` Jorijn van der Graaf
2026-07-22 23:02 ` Srinivas Kandagatla [this message]
2026-07-08 22:13 ` Srinivas Kandagatla
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=2545fdff-7bfc-4897-9185-34c45ee01bdc@kernel.org \
--to=srini@kernel.org \
--cc=broonie@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=jorijnvdgraaf@catcrafts.net \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=liujianfeng1994@gmail.com \
--cc=luca.weiss@fairphone.com \
--cc=mohammad.rafi.shaik@oss.qualcomm.com \
--cc=perex@perex.cz \
--cc=srinivas.kandagatla@oss.qualcomm.com \
--cc=tiwai@suse.com \
--cc=val@packett.cool \
/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.