From: Mark Brown <broonie@kernel.org>
To: Clark Wang <xiaoning.wang@nxp.com>,
nikita.shubin@maquefel.me, shawnguo@kernel.org,
s.hauer@pengutronix.de
Cc: linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com,
kernel@pengutronix.de, festevam@gmail.com
Subject: Re: [PATCH] spi: imx: fix the unbalanced spi runtime pm management
Date: Tue, 24 Nov 2020 15:37:32 +0000 [thread overview]
Message-ID: <160623225208.5156.18283999364037268437.b4-ty@kernel.org> (raw)
In-Reply-To: <20201124085247.18025-1-xiaoning.wang@nxp.com>
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
prev parent reply other threads:[~2020-11-24 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 8:52 Clark Wang
2020-11-24 15:37 ` 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=160623225208.5156.18283999364037268437.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=nikita.shubin@maquefel.me \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=xiaoning.wang@nxp.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
all inboxes | Powered by JetHome®