lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174657894590.4155013.6784460979005872545.b4-ty@kernel.org>
Date: Wed, 07 May 2025 09:49:05 +0900
From: Mark Brown <broonie@...nel.org>
To: Daniel Baluta <daniel.baluta@....com>
Cc: lgirdwood@...il.com, kernel@...gutronix.de, s.hauer@...gutronix.de, 
 festevam@...il.com, p.zabel@...gutronix.de, Frank.Li@....com, 
 iuliana.prodan@....com, linux-sound@...r.kernel.org, imx@...ts.linux.dev, 
 linux-kernel@...r.kernel.org, kai.vehmanen@...ux.intel.com, 
 daniel.baluta@...il.com, Bard Liao <yung-chuan.liao@...ux.intel.com>, 
 Péter Ujfalusi <peter.ujfalusi@...ux.intel.com>, 
 Laurentiu Mihalcea <laurentiu.mihalcea@....com>
Subject: Re: [PATCH] ASoC: SOF: imx8m: Use reset controller API to control
 the DSP

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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ