diff options
author | Mark Brown <broonie@kernel.org> | 2022-02-15 12:53:31 +0000 |
---|---|---|
committer | Mark Brown <broonie@kernel.org> | 2022-02-15 12:53:31 +0000 |
commit | 0177212e2789919be68c7922f33c71febc74842b (patch) | |
tree | 55888e58957dcef4534424329836f8d03824dde6 /net/ipv4/tcp_ipv4.c | |
parent | f48dc6b9664963107e500aecfc2f4df27dc5afb6 (diff) | |
parent | 4ab13489735d9b5b6e91634eab83922914a3310c (diff) | |
download | linux-0177212e2789919be68c7922f33c71febc74842b.tar.bz2 |
mtd: spi-nor / spi / MFD: Convert intel-spi to SPI MEM
Merge series from Mika Westerberg <mika.westerberg@linux.intel.com>:
Based on discussion on the patch I sent some time ago here:
http://lists.infradead.org/pipermail/linux-mtd/2021-June/086867.html
it turns out that the preferred way to deal with the SPI flash controller
drivers is through SPI MEM which is part of Linux SPI subsystem.
This series does that for the intel-spi driver. This also renames the
driver to follow the convention used in the SPI subsystem. The first patch
improves the write protection handling to be slightly more safer. The
following two patches do the conversion itself. Note the Intel SPI flash
controller only allows commands such as read, write and so on and it
internally uses whatever addressing etc. it figured from the SFDP on the
flash device.
base-commit: e783362eb54cd99b2cac8b3a9aeac942e6f6ac07
Diffstat (limited to 'net/ipv4/tcp_ipv4.c')
0 files changed, 0 insertions, 0 deletions