linux-kernel - Re: [PATCH] spi: imx: fix the unbalanced spi runtime pm management

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: <160623225208.5156.18283999364037268437.b4-ty@kernel.org>
Date:   Tue, 24 Nov 2020 15:37:32 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Clark Wang <xiaoning.wang@....com>, nikita.shubin@...uefel.me,
        shawnguo@...nel.org, s.hauer@...gutronix.de
Cc:     linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, linux-imx@....com,
        kernel@...gutronix.de, festevam@...il.com
Subject: Re: [PATCH] spi: imx: fix the unbalanced spi runtime pm management

On Tue, 24 Nov 2020 16:52:47 +0800, Clark Wang wrote:
> If set active without increase the usage count of pm, the dont use
> autosuspend function will call the suspend callback to close the two
> clocks of spi because the usage count is reduced to -1.
> This will cause the warning dump below when the defer-probe occurs.
> 
> [  129.379701] ecspi2_root_clk already disabled
> [  129.384005] WARNING: CPU: 1 PID: 33 at drivers/clk/clk.c:952 clk_core_disable+0xa4/0xb0
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: imx: fix the unbalanced spi runtime pm management
      commit: 7cd71202961090d8f2d2b863ec66b25ae43e1d39

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