summaryrefslogtreecommitdiffstats
path: root/fs/nfs/proc.c
diff options
context:
space:
mode:
authorWilliam Zhang <william.zhang@broadcom.com>2023-02-09 12:02:40 -0800
committerMark Brown <broonie@kernel.org>2023-02-10 21:36:40 +0000
commitc00d5e93ea018786d98670fc1d0dab4c36c2217c (patch)
tree836be138f9e24dcfec5ba35cbdea81232f37802e /fs/nfs/proc.c
parent6e80133abeb09721ec4601de5b1e68be67135309 (diff)
downloadlinux-c00d5e93ea018786d98670fc1d0dab4c36c2217c.tar.gz
linux-c00d5e93ea018786d98670fc1d0dab4c36c2217c.tar.bz2
linux-c00d5e93ea018786d98670fc1d0dab4c36c2217c.zip
spi: bcm63xx-hsspi: Handle cs_change correctly
The kernel SPI interface includes the cs_change flag that alters how the CS behaves. If we're in the middle of transfers, it tells us to unselect the CS momentarily since the target device requires that. If we're at the end of a transfer, it tells us to keep the CS selected, perhaps because the next transfer is likely targeted to the same device. We implement this scheme in the HSSPI driver in this change. Prior to this change, the CS would toggle momentarily if cs_change was set for the last transfer. This can be ignored by some or most devices, but the Microchip TPM2 device does not ignore it. With the change, the behavior is corrected and the 'glitch' is eliminated. Signed-off-by: Kursad Oney <kursad.oney@broadcom.com> Signed-off-by: William Zhang <william.zhang@broadcom.com> Link: https://lore.kernel.org/r/20230209200246.141520-10-william.zhang@broadcom.com Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'fs/nfs/proc.c')
0 files changed, 0 insertions, 0 deletions