spi: pxa2xx: Adapt reset_sccr1() to the case when no message available
Subsystems (3)
Andy Shevchenko
reviewerPATCH 1/1 spi: pxa2xx: Adapt reset_sccr1() to the case when no message available
In some cases reset_sccr1() can be called when no message available. This means that there is no associated chip to receive that message and hence no threshold needs to be set. Adapt the function to such cases.
--- drivers/spi/spi-pxa2xx.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)
drivers/spi/spi-pxa2xx.c +10 -3
@@ -594,8 +594,15 @@ static int u32_reader(struct driver_data *drv_data)static void reset_sccr1 (struct driver_data *drv_data) { -struct chip_data *chip =spi_get_ctldata (drv_data->controller->cur_msg->spi); -u32 mask = drv_data->int_cr1 | drv_data->dma_cr1; +u32 mask = drv_data->int_cr1 | drv_data->dma_cr1, threshold; +struct chip_data *chip; + +if (drv_data->controller->cur_msg) { + chip =spi_get_ctldata (drv_data->controller->cur_msg->spi); + threshold = chip->threshold; + }else { + threshold =0 ; + }switch (drv_data->ssp_type) {case QUARK_X1000_SSP :
@@ -609,7 +616,7 @@ static void reset_sccr1(struct driver_data *drv_data)break ; } -pxa2xx_spi_update (drv_data,SSCR1 , mask, chip->threshold); +pxa2xx_spi_update (drv_data,SSCR1 , mask, threshold); }static void int_stop_and_reset (struct driver_data *drv_data)
Signature · 1 line
2.30.2
Mark Brown
maintainerQuoted 4 lines · Andy Shevchenko
In some cases
reset_sccr1()can be called when no message available. This means that there is no associated chip to receive that message and hence no threshold needs to be set. Adapt the function to such cases.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: pxa2xx: Adapt reset_sccr1() to the case when no message available
commit: e3aa9acc71778266cc4743217ff1a1a53caf15d6
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