From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: "Agrawal, Akshu" <Akshu.Agrawal@amd.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
"moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER
MANAGEM..." <alsa-devel@alsa-project.org>,
Alexander.Deucher@amd.com, djkurtz@chromium.org,
Liam Girdwood <lgirdwood@gmail.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [alsa-devel] [PATCH] ASoC: soc-pcm: Use delay set in pointer function
Date: Tue, 31 Jul 2018 11:03:15 +0100 [thread overview]
Message-ID: <20180731100315.GA5719@sirena.org.uk> (raw)
In-Reply-To: <s5hwotc0y6v.wl-tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
On Tue, Jul 31, 2018 at 07:30:16AM +0200, Takashi Iwai wrote:
> OTOH, if the CPU dai can really provide a dynamic value that is
> strictly tied with pointer, CPU dai itself should provide the pointer
> callback that covers both the pointer and the base delay, and it
> should be used instead of component pointer callback.
Probably anything in the SoC would be potentially able to get a dynamic
value out - the main issue for off SoC devices is the cost of getting to
the data but that's not an issue when you're memory mapped.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: "moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER
MANAGEM..." <alsa-devel@alsa-project.org>,
open list <linux-kernel@vger.kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
djkurtz@chromium.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Alexander.Deucher@amd.com, "Agrawal,
Akshu" <Akshu.Agrawal@amd.com>
Subject: Re: [PATCH] ASoC: soc-pcm: Use delay set in pointer function
Date: Tue, 31 Jul 2018 11:03:15 +0100 [thread overview]
Message-ID: <20180731100315.GA5719@sirena.org.uk> (raw)
In-Reply-To: <s5hwotc0y6v.wl-tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 530 bytes --]
On Tue, Jul 31, 2018 at 07:30:16AM +0200, Takashi Iwai wrote:
> OTOH, if the CPU dai can really provide a dynamic value that is
> strictly tied with pointer, CPU dai itself should provide the pointer
> callback that covers both the pointer and the base delay, and it
> should be used instead of component pointer callback.
Probably anything in the SoC would be potentially able to get a dynamic
value out - the main issue for off SoC devices is the cost of getting to
the data but that's not an issue when you're memory mapped.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2018-07-31 10:03 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 10:13 [PATCH] ASoC: soc-pcm: Use delay set in pointer function Akshu Agrawal
2018-07-27 10:13 ` Akshu Agrawal
2018-07-27 15:09 ` [alsa-devel] " Pierre-Louis Bossart
2018-07-27 15:09 ` Pierre-Louis Bossart
2018-07-28 4:28 ` Agrawal, Akshu
2018-07-28 4:28 ` Agrawal, Akshu
2018-07-30 15:15 ` [alsa-devel] " Pierre-Louis Bossart
2018-07-30 15:15 ` Pierre-Louis Bossart
2018-07-30 15:32 ` Takashi Iwai
2018-07-30 15:32 ` Takashi Iwai
2018-07-30 15:50 ` Mark Brown
2018-07-30 15:50 ` Mark Brown
2018-07-31 1:25 ` [alsa-devel] " Agrawal, Akshu
2018-07-31 1:25 ` Agrawal, Akshu
2018-07-31 5:30 ` [alsa-devel] " Takashi Iwai
2018-07-31 5:30 ` Takashi Iwai
2018-07-31 9:06 ` Agrawal, Akshu
2018-07-31 9:06 ` Agrawal, Akshu
2018-07-31 9:25 ` [alsa-devel] " Takashi Iwai
2018-07-31 9:25 ` Takashi Iwai
2018-07-31 10:19 ` Mark Brown
2018-07-31 10:19 ` Mark Brown
2018-07-31 10:32 ` [alsa-devel] " Takashi Iwai
2018-07-31 10:32 ` Takashi Iwai
2018-07-31 13:12 ` Mark Brown
2018-07-31 13:12 ` Mark Brown
2018-07-31 13:29 ` [alsa-devel] " Takashi Iwai
2018-07-31 13:29 ` Takashi Iwai
2018-07-31 13:51 ` Mark Brown
2018-07-31 13:51 ` Mark Brown
2018-07-31 13:56 ` [alsa-devel] " Takashi Iwai
2018-07-31 13:56 ` Takashi Iwai
2018-07-31 14:40 ` Mark Brown
2018-07-31 14:40 ` Mark Brown
2018-08-01 4:01 ` [alsa-devel] " Agrawal, Akshu
2018-08-01 4:01 ` Agrawal, Akshu
2018-07-31 10:03 ` Mark Brown [this message]
2018-07-31 10:03 ` Mark Brown
2018-07-30 10:54 ` Mark Brown
2018-07-30 10:54 ` Mark Brown
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=20180731100315.GA5719@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Akshu.Agrawal@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=djkurtz@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.de \
/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.