diff options
| author | Arnd Bergmann <arnd@arndb.de> | 2016-01-08 17:46:45 +0100 |
|---|---|---|
| committer | Arnd Bergmann <arnd@arndb.de> | 2016-01-08 17:46:45 +0100 |
| commit | 841bcd2e5014f83ed99e88bd550645d8848ce19a (patch) | |
| tree | 84febff83e099171cffc49e91ee62842e63d5009 /drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | |
| parent | 0f090bf14e51e7eefb71d9d1c545807f8b627986 (diff) | |
| parent | e7b11dc7b77bfce0a351230a5feeadc1d0bba997 (diff) | |
Merge tag 'omap-for-v4.4/onenand-corruption' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into fixes
Pull "urgent onenand file system corruption fix for n900" from Tony Lindgren:
Last minute urgent pull request to prevent file system corruption
on Nokia N900.
Looks like we have a GPMC bus timing bug that has gone unnoticed
because of bootloader configured registers until few days ago. We
are not detecting the onenand clock rate properly unless we have
CONFIG_OMAP_GPMC_DEBUG set and this causes onenand corruption
that can be easily be reproduced.
There seems to be also an additional bug still lurking around for
onenand corruption. But that is still being investigated and
it does not seem to be GPMC timings related.
Meanwhile, it would be good to get this fix into v4.4 to prevent
wrong timings from corrupting onenand.
* tag 'omap-for-v4.4/onenand-corruption' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap:
ARM: OMAP2+: Fix onenand rate detection to avoid filesystem corruption
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_object.c')
0 files changed, 0 insertions, 0 deletions