From: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>
To: Markus Elfring <Markus.Elfring@web.de>,
linux-sound@vger.kernel.org, alsa-devel@alsa-project.org,
sound-open-firmware@alsa-project.org,
Mark Brown <broonie@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Basavaraj Hiregoudar <Basavaraj.Hiregoudar@amd.com>,
Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
Jaroslav Kysela <perex@perex.cz>,
Liam Girdwood <lgirdwood@gmail.com>,
Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Sunil-kumar Dommati <Sunil-kumar.Dommati@amd.com>,
Takashi Iwai <tiwai@suse.com>,
Venkata Prasad Potturu <venkataprasad.potturu@amd.com>
Subject: Re: [PATCH V2 1/2] ASoC: SOF: amd: move iram-dram fence register programming sequence
Date: Tue, 13 Aug 2024 17:16:24 +0530 [thread overview]
Message-ID: <0e8afd21-60f8-4a8a-aaa6-e148d4571908@amd.com> (raw)
In-Reply-To: <ac7efdcd-cc79-4984-8b36-50898243afa5@web.de>
On 13/08/24 17:05, Markus Elfring wrote:
>> The existing code modifies IRAM and DRAM size after sha dma start …
> SHA DMA?
>
>
> …
>> sha dma failure …
> SHA DMA?
I think above one seems to be okay.
>
>> IRAM size. To fix this issue, Move the iram-dram fence register sequence
>
> Thus move the IRAM-DRAM …?
I think above one seems to be okay.
>
>
> How do you think about to offer cover letters for patch series?
As these are individual fixes, I don't think a cover letter should
be included in the patch series.
>
> Regards,
> Markus
next prev parent reply other threads:[~2024-08-13 11:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 10:59 [PATCH V2 1/2] ASoC: SOF: amd: move iram-dram fence register programming sequence Vijendar Mukunda
2024-08-13 10:59 ` [PATCH V2 2/2] ASoC: SOF: amd: Fix for incorrect acp error register offsets Vijendar Mukunda
2024-08-13 10:59 ` Vijendar Mukunda
2024-08-13 11:35 ` [PATCH V2 1/2] ASoC: SOF: amd: move iram-dram fence register programming sequence Markus Elfring
2024-08-13 11:46 ` Mukunda,Vijendar [this message]
2024-08-13 14:52 ` 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=0e8afd21-60f8-4a8a-aaa6-e148d4571908@amd.com \
--to=vijendar.mukunda@amd.com \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Markus.Elfring@web.de \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sound-open-firmware@alsa-project.org \
--cc=tiwai@suse.com \
--cc=venkataprasad.potturu@amd.com \
--cc=yung-chuan.liao@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.