From: "Subhransu S. Prusty" <subhransu.s.prusty@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de,
Hardik T Shah <hardik.t.shah@intel.com>,
lgirdwood@gmail.com, patches.audio@intel.com,
Vinod Koul <vinod.koul@intel.com>
Subject: Re: [RFC 02/11] ASoC: Add dai_ops to set the stream tag.
Date: Fri, 8 Jul 2016 10:57:56 +0530 [thread overview]
Message-ID: <20160708052750.GA15209@subhransu-desktop> (raw)
In-Reply-To: <20160705125403.GS6247@sirena.org.uk>
On Tue, Jul 05, 2016 at 02:54:03PM +0200, Mark Brown wrote:
> On Thu, Jun 30, 2016 at 02:29:07PM +0530, Subhransu S. Prusty wrote:
>
> > Each DMA channel can be mapped to a stream in HDA. Each stream is mapped
> > uniquely with a stream tag. The stream is programmed in both host and
> > codec. In host the DMA is programmed with this stream tag and based on this
> > DMA picks data from host buffer and puts it onto the link. Similarly the
> > codec converter is programmed with the same stream tag and codec receives
> > packet from the link associated with the stream tag.
>
> Are these arbatrary tags? If so why not just pick tags that look like
> normal TDM timeslots?
If I understand correctly, the tag will be programmed in the tx_mask and
all other arguments will not be used.
Regards,
Subhransu
--
next prev parent reply other threads:[~2016-07-08 5:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 3:47 [RFC 00/11] ASoC: hdac: Add hdac generic driver Subhransu S. Prusty
2016-06-27 3:47 ` [RFC 01/11] ALSA: hdac: Add codec helper library Subhransu S. Prusty
2016-06-27 3:47 ` [RFC 02/11] ASoC: Add dai_ops to set the stream tag Subhransu S. Prusty
2016-06-27 17:30 ` Mark Brown
2016-06-28 5:21 ` Subhransu S. Prusty
2016-06-28 11:15 ` Mark Brown
2016-06-29 4:08 ` Subhransu S. Prusty
2016-06-29 18:50 ` Mark Brown
2016-06-30 8:59 ` Subhransu S. Prusty
2016-07-05 12:54 ` Mark Brown
2016-07-08 5:27 ` Subhransu S. Prusty [this message]
2016-06-27 3:47 ` [RFC 03/11] ALSA: hda - Add macro to test pin widget's input capability Subhransu S. Prusty
2016-06-27 3:47 ` [RFC 04/11] ASoC: hdac: Add a generic hdac driver framework Subhransu S. Prusty
2016-06-27 3:47 ` [RFC 05/11] ASoC: hdac: Create DAPM model for HDA widgets Subhransu S. Prusty
2016-06-27 3:47 ` [RFC 06/11] ASoC: dapm: Create API to add a single route element Subhransu S. Prusty
2016-06-27 18:02 ` Mark Brown
2016-06-28 5:22 ` Subhransu S. Prusty
2016-06-27 3:48 ` [RFC 07/11] ASoC: hdac: Build DAPM graph by querying through widget connection list Subhransu S. Prusty
2016-06-27 3:48 ` [RFC 08/11] ASoC: hdac: Register widget event handlers Subhransu S. Prusty
2016-06-27 3:48 ` [RFC 09/11] ALSA: hda - macro to get default config device of pin widgets Subhransu S. Prusty
2016-06-27 3:48 ` [RFC 10/11] ASoC: dapm: Export snd_soc_dapm_new_control Subhransu S. Prusty
2016-07-05 14:57 ` Applied "ASoC: dapm: Export snd_soc_dapm_new_control" to the asoc tree Mark Brown
2016-06-27 3:48 ` [RFC 11/11] ASoC: hdac: Export API to create machine controls Subhransu S. Prusty
2016-06-27 7:05 ` [RFC 00/11] ASoC: hdac: Add hdac generic driver Takashi Iwai
2016-06-28 5:13 ` Subhransu S. Prusty
2016-07-08 7:33 ` Subhransu S. Prusty
2016-07-08 7:53 ` Takashi Iwai
2016-07-08 8:21 ` Subhransu S. Prusty
2016-07-08 8:37 ` Takashi Iwai
2016-07-08 8:49 ` Subhransu S. Prusty
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=20160708052750.GA15209@subhransu-desktop \
--to=subhransu.s.prusty@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=hardik.t.shah@intel.com \
--cc=lgirdwood@gmail.com \
--cc=patches.audio@intel.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@intel.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;
as well as URLs for NNTP newsgroup(s).