On Wed, Dec 02, 2020 at 05:25:52PM +0300, Maxim Kochetkov wrote: > If cs-gpios property is used in devicetree then ctlr->num_chipselect value > may be changed by spi_get_gpio_descs(). > So use ctlr->max_native_cs instead of ctlr->num_chipselect to set SPI_MCR > > Fixes: 4fcc7c2292de (spi: spi-fsl-dspi: Don't access reserved fields in SPI_MCR) > Signed-off-by: Maxim Kochetkov <fido_max@xxxxxxxx> > --- In this case, it looks like Mark did really apply it, Maxim, I'm not sure why you resent: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git/commit/?h=for-5.10&id=2c2b3ad2c4c801bab1eec7264ea6991b1e4e8f2c
Re: [PATCH] spi: spi-fsl-dspi: Use max_native_cs instead of num_chipselect to set SPI_MCR
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH] spi: spi-fsl-dspi: Use max_native_cs instead of num_chipselect to set SPI_MCR
- From: Vladimir Oltean <olteanv@xxxxxxxxx>
- Date: Thu, 3 Dec 2020 01:57:28 +0200
- Cc: broonie@xxxxxxxxxx, linux-spi@xxxxxxxxxxxxxxx
- In-reply-to: <20201202142552.44385-1-fido_max@inbox.ru>
- References: <20201202142552.44385-1-fido_max@inbox.ru>
- Follow-Ups:
- References:
- [PATCH] spi: spi-fsl-dspi: Use max_native_cs instead of num_chipselect to set SPI_MCR
- From: Maxim Kochetkov
- [PATCH] spi: spi-fsl-dspi: Use max_native_cs instead of num_chipselect to set SPI_MCR
- Prev by Date: Re: [PATCH] spi: spi-fsl-dspi: Use max_native_cs instead of num_chipselect to set SPI_MCR
- Next by Date: Re: [PATCH 4/4] riscv: dts: add initial board data for the SiFive HiFive Unmatched
- Previous by thread: [PATCH] spi: spi-fsl-dspi: Use max_native_cs instead of num_chipselect to set SPI_MCR
- Next by thread: Re: [PATCH] spi: spi-fsl-dspi: Use max_native_cs instead of num_chipselect to set SPI_MCR
- Index(es):
 |