From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Cezary Rojewski <cezary.rojewski@intel.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org, broonie@kernel.org,
Daniel Baluta <daniel.baluta@nxp.com>
Subject: Re: [PATCH 4/6] ASoC: SOF: Intel: byt: Refactor fw ready / mem windows creation
Date: Wed, 7 Aug 2019 14:20:20 -0500 [thread overview]
Message-ID: <af12fa5a-89ea-2eb7-a8a2-0ba24b9fa214@linux.intel.com> (raw)
In-Reply-To: <ac41ec50-6484-cce1-2e41-c42e6bb541ef@intel.com>
On 8/7/19 2:07 PM, Cezary Rojewski wrote:
> On 2019-08-07 17:02, Pierre-Louis Bossart wrote:
>> From: Daniel Baluta <daniel.baluta@nxp.com>
>
>> So we are basically moving code from intel/byt.c to loader.c keeping
>> in mind that mbox_offset is a per platform constant so we need to
>> use newly introduced snd_sof_dsp_get_mailbox_offset /
>> snd_sof_dsp_get_window_offset in order to get the correct
>> mbox offset / window offset value.
>
> You've already explained your goal. These details are unnecessary.
They don't hurt and help explain the approach.
>
>>
>> Also, bar is a per platform constant so we use snd_sof_dsp_get_bar_index
>> instead of the hardcoded BYT_DSP_BAR.
>>
>> Signed-off-by: Daniel Baluta <daniel.baluta@nxp.com>
>> Signed-off-by: Pierre-Louis Bossart
>> <pierre-louis.bossart@linux.intel.com>
>> ---
>> sound/soc/sof/intel/byt.c | 164 +++++--------------------------------
>> sound/soc/sof/loader.c | 168 ++++++++++++++++++++++++++++++++++++++
>> sound/soc/sof/sof-priv.h | 2 +
>> 3 files changed, 189 insertions(+), 145 deletions(-)
>
> Hmm, even the commit message mentions two steps, not one. Splitting this
> commit into two - introduction of new generic functions and byt
> alignment towards the newly added approach - seems reasonable. Bdw & hda
> followups already make good examples.
The last two just remove the duplicate code and align on using the
common helpers.
In the initial step we still need to move the code from baytrail to the
common function. Doing it in two steps doesn't bring much added value
IMO. To preserve git bisect support, you'd need to add a new common
code, then remove the baytrail one in a follow-up patch. It'd make it
less self-explanatory where this new code comes from.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-08-07 19:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 15:01 [PATCH 0/6] ASoC: SOF: refactor duplicated code between Intel and i.MX8 Pierre-Louis Bossart
2019-08-07 15:01 ` [PATCH 1/6] ASoC: SOF: Remove call to snd_sof_dsp_mailbox_init Pierre-Louis Bossart
2019-08-09 12:31 ` Applied "ASoC: SOF: Remove call to snd_sof_dsp_mailbox_init" to the asoc tree Mark Brown
2019-08-07 15:01 ` [PATCH 2/6] ASoC: SOF: Introduce snd_sof_dsp_get_mailbox_offset Pierre-Louis Bossart
2019-08-09 12:31 ` Applied "ASoC: SOF: Introduce snd_sof_dsp_get_mailbox_offset" to the asoc tree Mark Brown
2019-08-07 15:02 ` [PATCH 3/6] ASoC: SOF: Introduce snd_sof_dsp_get_window_offset Pierre-Louis Bossart
2019-08-09 12:31 ` Applied "ASoC: SOF: Introduce snd_sof_dsp_get_window_offset" to the asoc tree Mark Brown
2019-08-07 15:02 ` [PATCH 4/6] ASoC: SOF: Intel: byt: Refactor fw ready / mem windows creation Pierre-Louis Bossart
2019-08-07 19:07 ` Cezary Rojewski
2019-08-07 19:20 ` Pierre-Louis Bossart [this message]
2019-08-09 12:31 ` Applied "ASoC: SOF: Intel: byt: Refactor fw ready / mem windows creation" to the asoc tree Mark Brown
2019-08-07 15:02 ` [PATCH 5/6] ASoC: SOF: Intel: bdw: Use generic function for fw ready / mem windows creation Pierre-Louis Bossart
2019-08-09 12:31 ` Applied "ASoC: SOF: Intel: bdw: Use generic function for fw ready / mem windows creation" to the asoc tree Mark Brown
2019-08-07 15:02 ` [PATCH 6/6] ASoC: SOF: Intel: hda: Use generic function for fw ready / mem windows creation Pierre-Louis Bossart
2019-08-09 12:31 ` Applied "ASoC: SOF: Intel: hda: Use generic function for fw ready / mem windows creation" to the asoc tree 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=af12fa5a-89ea-2eb7-a8a2-0ba24b9fa214@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=daniel.baluta@nxp.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;
as well as URLs for NNTP newsgroup(s).