From: Mark Brown <broonie@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
Marc Kleine-Budde <mkl@pengutronix.de>,
linux-spi@vger.kernel.org, Frieder Schrempf <frieder@fris.de>,
David Jander <david@protonic.nl>, Shawn Guo <shawnguo@kernel.org>,
linux-kernel@vger.kernel.org, Marek Vasut <marex@denx.de>,
Sascha Hauer <s.hauer@pengutronix.de>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Minghao Chi <chi.minghao@zte.com.cn>,
Frieder Schrempf <frieder.schrempf@kontron.de>,
stable@vger.kernel.org, Baruch Siach <baruch.siach@siklu.com>
Subject: Re: [PATCH v3] spi: spi-imx: Fix spi_bus_clk if requested clock is higher than input clock
Date: Wed, 16 Nov 2022 13:42:56 +0000 [thread overview]
Message-ID: <166860617673.408509.6245809939301847607.b4-ty@kernel.org> (raw)
In-Reply-To: <20221115181002.2068270-1-frieder@fris.de>
On Tue, 15 Nov 2022 19:10:00 +0100, Frieder Schrempf wrote:
> From: Frieder Schrempf <frieder.schrempf@kontron.de>
>
> In case the requested bus clock is higher than the input clock, the correct
> dividers (pre = 0, post = 0) are returned from mx51_ecspi_clkdiv(), but
> *fres is left uninitialized and therefore contains an arbitrary value.
>
> This causes trouble for the recently introduced PIO polling feature as the
> value in spi_imx->spi_bus_clk is used there to calculate for which
> transfers to enable PIO polling.
>
> [...]
Applied to
broonie/spi.git for-next
Thanks!
[1/1] spi: spi-imx: Fix spi_bus_clk if requested clock is higher than input clock
commit: db2d2dc9a0b58c6faefb6b002fdbed4f0362d1a4
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:[~2022-11-16 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 18:10 Frieder Schrempf
2022-11-15 23:49 ` Marek Vasut
2022-11-16 8:17 ` Frieder Schrempf
2022-11-16 10:49 ` Marek Vasut
2022-11-16 13:42 ` 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=166860617673.408509.6245809939301847607.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=baruch.siach@siklu.com \
--cc=chi.minghao@zte.com.cn \
--cc=david@protonic.nl \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=frieder@fris.de \
--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=marex@denx.de \
--cc=mkl@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stable@vger.kernel.org \
/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®