From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Cezary Rojewski <cezary.rojewski@intel.com>
Cc: broonie@kernel.org, vkoul@kernel.org, robh+dt@kernel.org,
devicetree@vger.kernel.org, mark.rutland@arm.com,
pierre-louis.bossart@linux.intel.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/6] ASoC: core: add support to snd_soc_dai_get_sdw_stream()
Date: Sun, 9 Jun 2019 13:16:23 +0100 [thread overview]
Message-ID: <eef7ecf8-330f-c7e8-7d5e-f21d9771f037@linaro.org> (raw)
In-Reply-To: <13bfb632-f743-c416-2224-c7acb5b28604@intel.com>
Thanks for taking time to review,
On 08/06/2019 20:22, Cezary Rojewski wrote:
> On 2019-06-07 10:56, Srinivas Kandagatla wrote:
>> On platforms which have smart speaker amplifiers connected via
>> soundwire and modeled as aux devices in ASoC, in such usecases machine
>> driver should be able to get sdw master stream from dai so that it can
>> use the runtime stream to setup slave streams.
>>
>> soundwire already as a set function, get function would provide more
>> flexibility to above configurations.
>>
>> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
>> ---
>> include/sound/soc-dai.h | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>>
>> diff --git a/include/sound/soc-dai.h b/include/sound/soc-dai.h
>> index f5d70041108f..9f90b936fd9a 100644
>> --- a/include/sound/soc-dai.h
>> +++ b/include/sound/soc-dai.h
>> @@ -177,6 +177,7 @@ struct snd_soc_dai_ops {
>> int (*set_sdw_stream)(struct snd_soc_dai *dai,
>> void *stream, int direction);
>> + void *(*get_sdw_stream)(struct snd_soc_dai *dai, int direction);
>> /*
>> * DAI digital mute - optional.
>> * Called by soc-core to minimise any pops.
>> @@ -385,4 +386,13 @@ static inline int
>> snd_soc_dai_set_sdw_stream(struct snd_soc_dai *dai,
>> return -ENOTSUPP;
>> }
>> +static inline void *snd_soc_dai_get_sdw_stream(struct snd_soc_dai
>> *dai, int direction)
>
> Exceeds character limit?
>
>> +{
>> + if (dai->driver->ops->get_sdw_stream)
>> + return dai->driver->ops->get_sdw_stream(dai, direction);
>> + else
>> + return NULL;
>
> set_ equivalent returns -ENOTSUPP instead.
> ERR_PTR seems to make more sense here.
>
>> +
>
> Unnecessary newline.
I agree with all the comment, will fix this in next version.
thanks,
srini
>
>> +}
>> +
>> #endif
>>
next prev parent reply other threads:[~2019-06-09 12:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 8:56 [RFC PATCH 0/6] soundwire: Add support to Qualcomm SoundWire master Srinivas Kandagatla
2019-06-07 8:56 ` [RFC PATCH 1/6] ASoC: core: add support to snd_soc_dai_get_sdw_stream() Srinivas Kandagatla
2019-06-08 19:22 ` Cezary Rojewski
2019-06-09 12:16 ` Srinivas Kandagatla [this message]
2019-06-10 4:34 ` Vinod Koul
2019-06-10 7:58 ` Srinivas Kandagatla
2019-06-07 8:56 ` [RFC PATCH 2/6] soundwire: Add compute_params callback Srinivas Kandagatla
2019-06-07 8:56 ` [RFC PATCH 3/6] soundwire: core: define SDW_MAX_PORT Srinivas Kandagatla
2019-06-07 12:31 ` [alsa-devel] " Pierre-Louis Bossart
2019-06-08 20:04 ` Cezary Rojewski
2019-06-07 8:56 ` [RFC PATCH 4/6] soundwire: stream: make stream name a const pointer Srinivas Kandagatla
2019-06-07 8:56 ` [RFC PATCH 5/6] dt-bindings: soundwire: add bindings for Qcom controller Srinivas Kandagatla
2019-06-07 12:50 ` [alsa-devel] " Pierre-Louis Bossart
2019-06-09 12:16 ` Srinivas Kandagatla
2019-06-10 4:51 ` Vinod Koul
2019-06-10 8:14 ` Srinivas Kandagatla
2019-06-10 13:58 ` [alsa-devel] " Pierre-Louis Bossart
2019-06-07 8:56 ` [RFC PATCH 6/6] soundwire: qcom: add support for SoundWire controller Srinivas Kandagatla
2019-06-07 13:36 ` [alsa-devel] " Pierre-Louis Bossart
2019-06-09 12:15 ` Srinivas Kandagatla
2019-06-10 14:12 ` Pierre-Louis Bossart
2019-06-11 10:29 ` Srinivas Kandagatla
2019-06-11 12:21 ` Pierre-Louis Bossart
2019-06-15 13:24 ` Srinivas Kandagatla
2019-06-08 21:53 ` Cezary Rojewski
2019-06-09 12:15 ` Srinivas Kandagatla
2019-06-10 6:40 ` Vinod Koul
2019-06-10 8:27 ` 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=eef7ecf8-330f-c7e8-7d5e-f21d9771f037@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=robh+dt@kernel.org \
--cc=vkoul@kernel.org \
/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).