summaryrefslogtreecommitdiffstats
path: root/scripts/Makefile.modsign
diff options
context:
space:
mode:
authorDmitry Eremin-Solenikov <dbaryshkov@gmail.com>2014-10-23 01:23:01 +0200
committerBrian Norris <computersforpeace@gmail.com>2014-10-30 02:50:52 +0100
commit89cf38dd536a7301d6b5f5ddd73f42074c01bfaa (patch)
treed6b1e5e6dfccdefd4660baa662ec427d7f73eee9 /scripts/Makefile.modsign
parentmtd: omap: fix mtd devices not showing up (diff)
downloadlinux-89cf38dd536a7301d6b5f5ddd73f42074c01bfaa.tar.xz
linux-89cf38dd536a7301d6b5f5ddd73f42074c01bfaa.zip
mtd: cfi_cmdset_0001.c: fix resume for LH28F640BF chips
After '#echo mem > /sys/power/state' some devices can not be properly resumed because apparently the MTD Partition Configuration Register has been reset to default thus the rootfs cannot be mounted cleanly on resume. An example of this can be found in the SA-1100 Developer's Manual at 9.5.3.3 where the second step of the Sleep Shutdown Sequence is described: "An internal reset is applied to the SA-1100. All units are reset...". As workaround we refresh the PCR value as done initially on chip setup. This behavior and the fix are confirmed by our tests done on 2 different Zaurus collie units with kernel 3.17. Fixes: 812c5fa82bae: ("mtd: cfi_cmdset_0001.c: add support for Sharp LH28F640BF NOR") Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> Signed-off-by: Andrea Adami <andrea.adami@gmail.com> Cc: <stable@vger.kernel.org> # 3.16+ Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Diffstat (limited to 'scripts/Makefile.modsign')
0 files changed, 0 insertions, 0 deletions