From: Vinod Koul <vinod.koul@intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: ALSA <alsa-devel@alsa-project.org>,
tiwai@suse.de, Greg KH <gregkh@linuxfoundation.org>,
liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
broonie@kernel.org, Shreyas NC <shreyas.nc@intel.com>
Subject: Re: [PATCH v4 08/13] ASoC: Add SoundWire stream programming interface
Date: Sat, 21 Apr 2018 21:28:04 +0530 [thread overview]
Message-ID: <20180421155804.GN6014@localhost> (raw)
In-Reply-To: <79c978d0-0ded-ddcb-5405-18b657c062d7@linux.intel.com>
On Sat, Apr 21, 2018 at 06:59:49AM -0700, Pierre-Louis Bossart wrote:
>
> >+/**
> >+ * snd_soc_dai_set_sdw_stream() - Configures a DAI for SDW stream operation
> >+ * @dai: DAI
> >+ * @stream: STREAM
> >+ * @direction: Stream direction(Playback/Capture)
> >+ * SoundWire subsystem doesn't have a notion of direction and we reuse
> >+ * the ASoC stream direction to configure sink/source ports.
> >+ * Playback maps to source on the TX and sink on Rx. Vice-versa for Capture.
>
> this is just confusing...
>
> This should be something like
> "use Playback for source ports and Capture for sink ports".
Source port on ...? This is also confusing to me!
For playback there are two ports, one on transmitter aka
TX and one on receiver aka RX. For Tx we use source port, and Rx uses sink
ports. I should probably add port to make people really figure out we are
talking about ports!
So:
Playback maps to source port on the TX and sink port on Rx. Vice-versa for Capture.
Do you agree to above statement?
--
~Vinod
next prev parent reply other threads:[~2018-04-21 15:53 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 10:58 [PATCH v4 00/13] soundwire: Add stream support Vinod Koul
2018-04-18 10:58 ` [PATCH v4 01/13] Documentation: soundwire: Add more documentation Vinod Koul
2018-04-18 10:58 ` [PATCH v4 02/13] soundwire: Add support for SoundWire stream management Vinod Koul
2018-04-21 13:02 ` Pierre-Louis Bossart
2018-04-21 16:17 ` Vinod Koul
2018-04-23 13:25 ` Pierre-Louis Bossart
2018-04-24 9:02 ` Vinod Koul
2018-04-24 9:25 ` Vinod Koul
2018-04-18 10:58 ` [PATCH v4 03/13] soundwire: Add support for port management Vinod Koul
2018-04-18 10:58 ` [PATCH v4 04/13] soundwire: Add Master and Slave port programming Vinod Koul
2018-04-18 10:58 ` [PATCH v4 05/13] soundwire: Add helpers for ports operations Vinod Koul
2018-04-21 13:39 ` Pierre-Louis Bossart
2018-04-21 15:54 ` Vinod Koul
2018-04-21 13:47 ` Pierre-Louis Bossart
2018-04-21 15:53 ` Vinod Koul
2018-04-23 13:27 ` Pierre-Louis Bossart
2018-04-24 9:03 ` Vinod Koul
2018-04-18 10:58 ` [PATCH v4 06/13] soundwire: Add bank switch routine Vinod Koul
2018-04-18 10:59 ` [PATCH v4 07/13] soundwire: Add stream configuration APIs Vinod Koul
2018-04-21 13:56 ` Pierre-Louis Bossart
2018-04-21 16:13 ` Vinod Koul
2018-04-23 3:45 ` Sanyog Kale
2018-04-24 9:09 ` Vinod Koul
2018-04-23 13:30 ` Pierre-Louis Bossart
2018-04-18 10:59 ` [PATCH v4 08/13] ASoC: Add SoundWire stream programming interface Vinod Koul
2018-04-21 13:59 ` Pierre-Louis Bossart
2018-04-21 15:58 ` Vinod Koul [this message]
2018-04-23 13:33 ` Pierre-Louis Bossart
2018-04-24 9:06 ` Vinod Koul
2018-04-24 23:40 ` Pierre-Louis Bossart
2018-04-25 2:49 ` Vinod Koul
2018-04-25 15:08 ` Pierre-Louis Bossart
2018-04-18 10:59 ` [PATCH v4 09/13] soundwire: Remove cdns_master_ops Vinod Koul
2018-04-18 10:59 ` [PATCH v4 10/13] soundwire: cdns: Add port routines Vinod Koul
2018-04-18 10:59 ` [PATCH v4 11/13] soundwire: cdns: Add stream routines Vinod Koul
2018-04-18 10:59 ` [PATCH v4 12/13] soundwire: intel: Add stream initialization Vinod Koul
2018-04-18 10:59 ` [PATCH v4 13/13] soundwire: intel: Add audio DAI ops Vinod Koul
2018-04-21 14:08 ` [PATCH v4 00/13] soundwire: Add stream support Pierre-Louis Bossart
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=20180421155804.GN6014@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=shreyas.nc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox