aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/check-perf-trace.py
diff options
context:
space:
mode:
authorLinus Walleij <[email protected]>2019-12-04 16:27:49 +0100
committerUlf Hansson <[email protected]>2019-12-16 12:29:05 +0100
commitaf3ed119329cf9690598c5a562d95dfd128e91d6 (patch)
tree50877c05a8b81be132b6c506b6f9677de09acd72 /tools/perf/scripts/python/check-perf-trace.py
parent3976656d67c1e47a5deb25f2c2fdc188dd97dbd7 (diff)
mmc: spi: Toggle SPI polarity, do not hardcode it
The code in mmc_spi_initsequence() tries to send a burst with high chipselect and for this reason hardcodes the device into SPI_CS_HIGH. This is not good because the SPI_CS_HIGH flag indicates logical "asserted" CS not always the physical level. In some cases the signal is inverted in the GPIO library and in that case SPI_CS_HIGH is already set, and enforcing SPI_CS_HIGH again will actually drive it low. Instead of hard-coding this, toggle the polarity so if the default is LOW it goes high to assert chipselect but if it is already high then toggle it low instead. Cc: Phil Elwell <[email protected]> Reported-by: Mark Brown <[email protected]> Signed-off-by: Linus Walleij <[email protected]> Reviewed-by: Mark Brown <[email protected]> Link: https://lore.kernel.org/r/[email protected] Cc: [email protected] Signed-off-by: Ulf Hansson <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions