linux-kernel - Re: [PATCH] spi: davinci: Unset POWERDOWN bit when releasing resources

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]

Date: Mon, 01 Jul 2024 15:08:18 +0100
From: Mark Brown <broonie@...nel.org>
To: Bastien Curutchet <bastien.curutchet@...tlin.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Thomas Petazzoni <thomas.petazzoni@...tlin.com>, 
 Herve Codina <herve.codina@...tlin.com>, 
 Christopher Cordahi <christophercordahi@...ometrics.ca>
Subject: Re: [PATCH] spi: davinci: Unset POWERDOWN bit when releasing
 resources

On Mon, 24 Jun 2024 09:17:45 +0200, Bastien Curutchet wrote:
> On the OMAPL138, the SPI reference clock is provided by the Power and
> Sleep Controller (PSC). The PSC's datasheet says that 'some peripherals
> have special programming requirements and additional recommended steps
> you must take before you can invoke the PSC module state transition'. I
> didn't find more details in documentation but it appears that PSC needs
> the SPI to clear the POWERDOWN bit before disabling the clock. Indeed,
> when this bit is set, the PSC gets stuck in transitions from enable to
> disable state.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: davinci: Unset POWERDOWN bit when releasing resources
      commit: 1762dc01fc78ef5f19693e9317eae7491c6c7e1b

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