From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Raghu Ballappa Bankapur <quic_rbankapu@quicinc.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org
Cc: Rander Wang <rander.wang@linux.intel.com>
Subject: Re: Query on get_time_info
Date: Fri, 27 Jan 2023 08:36:55 -0600 [thread overview]
Message-ID: <923c4ca3-bf79-bd34-279a-54c817dbf413@linux.intel.com> (raw)
In-Reply-To: <271019c5-cfba-fa77-12e0-df97034f25b3@quicinc.com>
On 1/27/23 08:03, Raghu Ballappa Bankapur wrote:
> HI All,
>
>
> We see get_time_info is not enabled from ALSA core. ay reason behind?
I think you meant ASoC core?
> we enabled like below with some more code, we are able to get_time_info
> to lower driver.
>
> static int dpcm_be_connect(struct snd_soc_pcm_runtime *fe,
> struct snd_soc_pcm_runtime *be, int stream)
> @@ -2907,6 +2927,7 @@ int soc_new_pcm(struct snd_soc_pcm_runtime *rtd,
> int num)
> rtd->ops.hw_free = dpcm_fe_dai_hw_free;
> rtd->ops.close = dpcm_fe_dai_close;
> rtd->ops.pointer = soc_pcm_pointer;
> + rtd->ops.get_time_info = soc_pcm_get_time_info;
> } else {
> rtd->ops.open = soc_pcm_open;
> rtd->ops.hw_params = soc_pcm_hw_params;
> @@ -2915,6 +2936,7 @@ int soc_new_pcm(struct snd_soc_pcm_runtime *rtd,
> int num)
> rtd->ops.hw_free = soc_pcm_hw_free;
> rtd->ops.close = soc_pcm_close;
> rtd->ops.pointer = soc_pcm_pointer;
> + rtd->ops.get_time_info = soc_pcm_get_time_info;
> }
>
> Is this ALSA limitation or any other approach is followed to enable this
> implementation.
No, it's a miss.
I had a patch to fix this in
https://github.com/thesofproject/linux/pull/3792, but somehow it never
made its path upstream. I don't fully recall the details, only vaguely
that we first added support for the .delay(), but the get_time_info part
was tested back in August 2022.
Would that patch work for you?
next prev parent reply other threads:[~2023-01-27 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 14:03 Query on get_time_info Raghu Ballappa Bankapur
2023-01-27 14:36 ` Pierre-Louis Bossart [this message]
2023-01-30 4:16 ` Raghu Ballappa Bankapur
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=923c4ca3-bf79-bd34-279a-54c817dbf413@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=perex@perex.cz \
--cc=quic_rbankapu@quicinc.com \
--cc=rander.wang@linux.intel.com \
--cc=tiwai@suse.com \
/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