From: Markus Elfring <Markus.Elfring@web.de>
To: Vijendar Mukunda <Vijendar.Mukunda@amd.com>,
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 13:35:55 +0200 [thread overview]
Message-ID: <ac7efdcd-cc79-4984-8b36-50898243afa5@web.de> (raw)
In-Reply-To: <20240813105944.3126903-1-Vijendar.Mukunda@amd.com>
> The existing code modifies IRAM and DRAM size after sha dma start …
SHA DMA?
…
> sha dma failure …
SHA DMA?
> IRAM size. To fix this issue, Move the iram-dram fence register sequence
Thus move the IRAM-DRAM …?
How do you think about to offer cover letters for patch series?
Regards,
Markus
next prev parent reply other threads:[~2024-08-13 11:36 UTC|newest]
Thread overview: 5+ 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 11:35 ` Markus Elfring [this message]
2024-08-13 11:46 ` [PATCH V2 1/2] ASoC: SOF: amd: move iram-dram fence register programming sequence Mukunda,Vijendar
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=ac7efdcd-cc79-4984-8b36-50898243afa5@web.de \
--to=markus.elfring@web.de \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=Vijendar.Mukunda@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox