diff options
author | Mika Westerberg <mika.westerberg@linux.intel.com> | 2017-07-28 13:50:42 +0300 |
---|---|---|
committer | Lee Jones <lee.jones@linaro.org> | 2017-09-05 08:46:01 +0100 |
commit | d9018976cdb6eefc62a7ba79a405f6c9661b08a7 (patch) | |
tree | 2e7aa3e375a4cc7479fad103c38536f8c9f23aaf /kernel/trace/trace_entries.h | |
parent | b0f3ab20e76499db12b0bbadb5737d9870f10418 (diff) | |
download | linux-d9018976cdb6eefc62a7ba79a405f6c9661b08a7.tar.gz linux-d9018976cdb6eefc62a7ba79a405f6c9661b08a7.tar.bz2 linux-d9018976cdb6eefc62a7ba79a405f6c9661b08a7.zip |
mfd: lpc_ich: Do not touch SPI-NOR write protection bit on Haswell/Broadwell
At least on Lenovo Thinkpad Yoga, the BIOS seems to monitor the SPI-NOR
write protection bit and if it is flipped to read/write it assumes the
BIOS configuration was changed on next reboot. It then, for unknown
reasons, resets the BIOS settings back to default.
We can prevent this by just leaving the write protection bit intact and
let the SPI-NOR driver know whether the device is writable or not. In
case of this particular Lenovo the SPI-NOR flash will be exposed as
read-only.
Fixes: ff00d7a32a1b ("mfd: lpc_ich: Add support for SPI serial flash host controller")
Link: https://bugzilla.kernel.org/show_bug.cgi?id=195951
Reported-by: Abdó Roig-Marange <abdo.roig@gmail.com>
Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Signed-off-by: Lee Jones <lee.jones@linaro.org>
Diffstat (limited to 'kernel/trace/trace_entries.h')
0 files changed, 0 insertions, 0 deletions