Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Keyon Jie <yang.jie@linux.intel.com>
To: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
	alsa-devel@alsa-project.org
Cc: marcin.rajwa@intel.com, "Lin, Mengdong" <mengdong.lin@intel.com>,
	pierre-louis.bossart@linux.intel.com,
	Marcin Rajwa <marcin.rajwa@linux.intel.com>
Subject: Re: [PATCH 1/2] ASoC: SOF: ipc: update sof_ipc_stream_params
Date: Wed, 3 Jul 2019 09:52:39 +0800	[thread overview]
Message-ID: <8e81bbac-8b5a-9bc0-60ed-115429b07e82@linux.intel.com> (raw)
In-Reply-To: <a233dfdbb973251d439197d13b69c867667d3f76.camel@linux.intel.com>



On 2019/7/3 上午7:29, Ranjani Sridharan wrote:
> On Tue, 2019-07-02 at 20:11 +0800, Keyon Jie wrote:
>> From: Marcin Rajwa <marcin.rajwa@linux.intel.com>
>>
>> The host period bytes needs to be passed to firmware.
>> Currently this field is used as notification for host
>> about period copy completion. Therefore we need to split these
>> two informations.
> Keyon/Marcin,
> 
> Could you please add a bit more context in the commit message on the
> need to split these two fields ie.. what usecases need this?

Sure, previously I wrote the commit message like this:

ASoC: SOF: add flag for position update ipc

In some cases, FW might need use the host_period_bytes even no position
update ipc reqiured from driver, here add another flag for position update,
and preserve host_period_bytes for FW to use.

This might require corresponding FW change and ABI alignment.

Thanks,
~Keyon

> 
> Thanks,
> Ranjani
>>
>> Signed-off-by: Marcin Rajwa <marcin.rajwa@linux.intel.com>
>> Signed-off-by: Keyon Jie <yang.jie@linux.intel.com>
>> ---
>>   include/sound/sof/stream.h | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/include/sound/sof/stream.h b/include/sound/sof/stream.h
>> index 643f175cb479..44acfa62fa69 100644
>> --- a/include/sound/sof/stream.h
>> +++ b/include/sound/sof/stream.h
>> @@ -83,10 +83,10 @@ struct sof_ipc_stream_params {
>>   	uint16_t sample_valid_bytes;
>>   	uint16_t sample_container_bytes;
>>   
>> -	/* for notifying host period has completed - 0 means no period
>> IRQ */
>>   	uint32_t host_period_bytes;
>> +	uint16_t no_period_irq; /* 1 means period IRQ mode OFF */
>>   
>> -	uint32_t reserved[2];
>> +	uint16_t reserved[3];
>>   	uint16_t chmap[SOF_IPC_MAX_CHANNELS];	/**< channel map -
>> SOF_CHMAP_ */
>>   } __packed;
>>   
> 
> 
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      reply	other threads:[~2019-07-03  1:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-02 12:11 [PATCH 1/2] ASoC: SOF: ipc: update sof_ipc_stream_params Keyon Jie
2019-07-02 12:11 ` [PATCH 2/2] ASoC: SOF: Intel: fix reset of host_period_bytes Keyon Jie
2019-07-02 23:29 ` [PATCH 1/2] ASoC: SOF: ipc: update sof_ipc_stream_params Ranjani Sridharan
2019-07-03  1:52   ` Keyon Jie [this message]

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=8e81bbac-8b5a-9bc0-60ed-115429b07e82@linux.intel.com \
    --to=yang.jie@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=marcin.rajwa@intel.com \
    --cc=marcin.rajwa@linux.intel.com \
    --cc=mengdong.lin@intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=ranjani.sridharan@linux.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