summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin/stackcollapse-report
diff options
context:
space:
mode:
authorFrieder Schrempf <frieder.schrempf@kontron.de>2026-09-17 16:10:15 +0200
committerMark Brown <broonie@kernel.org>2026-09-17 19:46:29 +0100
commit3d743adf090cd4c9a2120c1e02b0482e88aa0d2d (patch)
treebdf434c24c497bfbbf6c938d5fc0fd54f592f69b /tools/perf/scripts/python/bin/stackcollapse-report
parente922bad8b2d5028c51a096d083fea41cd0987154 (diff)
downloadlinux-next-3d743adf090cd4c9a2120c1e02b0482e88aa0d2d.tar.gz
linux-next-3d743adf090cd4c9a2120c1e02b0482e88aa0d2d.zip
spi: fsl-qspi: Reprogram the clock rate when the operation frequency changes
fsl_qspi_select_mem() returns early when the chip select has not changed, which happens before it reaches clk_set_rate(). Since the rate is now taken from the spi-mem operation rather than from the SPI device, the controller honours op->max_freq exactly once per chip select and ignores it for every operation after that. q->selected is only reset to -1 in fsl_qspi_default_setup(), i.e. at probe and on resume, so on the common single chip select board the very first operation latches a rate that all subsequent operations inherit, whatever frequency they asked for. This results in operations being issued with the wrong frequency. Cache the operation frequency the clock was programmed for next to the selected chip select, and redo the clock setup when either changes. Fixes: 2438db5253eb ("spi: fsl-qspi: Support per spi-mem operation frequency switches") Cc: stable@vger.kernel.org Assisted-by: Claude:claude-opus-5 Signed-off-by: Frieder Schrempf <frieder.schrempf@kontron.de> Acked-by: Han Xu <han.xu@nxp.com> Link: https://patch.msgid.link/20260917-fsl-qspi-freq-op-fix-v1-1-5fbe6b02f738@kontron.de Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions