mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-21 03:33:59 +08:00
e48880e02e
When reviewing a recent patch I noticed a potential trouble spot in the registration of new SPI devices. The SPI master driver is told to set the device up before adding it to the driver model, so that it's always properly set up when probe() is called. (This is important, because in the case of inverted chipselects, this device can make the bus misbehave until it's properly deselected. It's got to be set up even if no driver binds to the device.) The trouble spot is that it doesn't first verify that no other device has been added using that chipselect. If such a device has been added, its configuration gets trashed. (Fortunately this has not been a common error!) The fix here adds an explicit check, and a mutex to protect the relevant critical region. [akpm@linux-foundation.org: make the lock local to spi_add_device()] Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> |
||
|---|---|---|
| .. | ||
| at25.c | ||
| atmel_spi.c | ||
| atmel_spi.h | ||
| au1550_spi.c | ||
| Kconfig | ||
| Makefile | ||
| mpc52xx_psc_spi.c | ||
| omap2_mcspi.c | ||
| omap_uwire.c | ||
| orion_spi.c | ||
| pxa2xx_spi.c | ||
| spi_bfin5xx.c | ||
| spi_bitbang.c | ||
| spi_butterfly.c | ||
| spi_imx.c | ||
| spi_lm70llp.c | ||
| spi_mpc83xx.c | ||
| spi_s3c24xx_gpio.c | ||
| spi_s3c24xx.c | ||
| spi_sh_sci.c | ||
| spi_txx9.c | ||
| spi.c | ||
| spidev.c | ||
| tle62x0.c | ||
| xilinx_spi.c | ||