From: Mark Brown <broonie@kernel.org>
To: Daniel Baluta <daniel.baluta@nxp.com>
Cc: lgirdwood@gmail.com, kernel@pengutronix.de,
s.hauer@pengutronix.de, festevam@gmail.com,
p.zabel@pengutronix.de, Frank.Li@nxp.com, iuliana.prodan@nxp.com,
linux-sound@vger.kernel.org, imx@lists.linux.dev,
linux-kernel@vger.kernel.org, kai.vehmanen@linux.intel.com,
daniel.baluta@gmail.com,
"Bard Liao" <yung-chuan.liao@linux.intel.com>,
"Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>,
"Laurentiu Mihalcea" <laurentiu.mihalcea@nxp.com>
Subject: Re: [PATCH] ASoC: SOF: imx8m: Use reset controller API to control the DSP
Date: Wed, 07 May 2025 09:49:05 +0900 [thread overview]
Message-ID: <174657894590.4155013.6784460979005872545.b4-ty@kernel.org> (raw)
In-Reply-To: <20250505114251.57018-1-daniel.baluta@nxp.com>
On Mon, 05 May 2025 14:42:51 +0300, Daniel Baluta wrote:
> DSP on i.MX8MP doesn't have a direct reset line so according to hardware
> design team in order to handle assert/deassert/reset functionality we
> need to use a combination of control bits from two modules. Audio block
> control module for Run/Stall control of the DSP and DAP module in order
> to do software reset.
>
> In a first step, for i.MX8MP we are switching on using the reset
> controller API to handle the DSP Run/Stall bits i.MX8MP. This comes with
> the advantage of offering a better probe ordering and a more natural way
> of abstracting the Audio block control bits.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: SOF: imx8m: Use reset controller API to control the DSP
commit: a71b261c19a455f7f8e560b4ddfac44d3150ae39
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2025-05-07 0:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 11:42 [PATCH] ASoC: SOF: imx8m: Use reset controller API to control the DSP Daniel Baluta
2025-05-07 0:49 ` Mark Brown [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=174657894590.4155013.6784460979005872545.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=daniel.baluta@gmail.com \
--cc=daniel.baluta@nxp.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=iuliana.prodan@nxp.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=kernel@pengutronix.de \
--cc=laurentiu.mihalcea@nxp.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=peter.ujfalusi@linux.intel.com \
--cc=s.hauer@pengutronix.de \
--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