diff options
author | Kevin Hilman <khilman@linaro.org> | 2013-12-09 15:38:00 -0800 |
---|---|---|
committer | Kevin Hilman <khilman@linaro.org> | 2013-12-09 15:38:41 -0800 |
commit | ed16c8c50e26df3c16e40d35c9a4c0e9f032656c (patch) | |
tree | f268748e4bd3a6ceb08b7a7a70fb86c4dfce0e02 /Documentation/filesystems | |
parent | 8ae19ec3356901bafa64816d9ea9378896f8979c (diff) | |
parent | f2e2c9d9b4087b74eb9e00d8dfac148354cb0b71 (diff) |
Merge tag 'omap-for-v3.13/yet-more-dt-regressions-take2' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into fixes
A rather big fix for a regression where we have dropped omap4 hwmod
data earlier but are not initializing it from device tree. In addition
to this fix we eventually also be fix the issues in the .dts files
and drivers, but that's too intrusive for the -rc cycle and must be
done later on.
Also a fix for a regression where we now are wrongly trying to initialize
devices on secure omaps like n900 and n9* when booted using device tree.
We need to set aes, sham and timer12 to disabled mode for secure
devices as they are claimed by the firmware running in the secure mode.
And two more legacy booting vs device tree based booting fixes for
am3517 that I did not notice earlier until Nishant Menon reported
these to me few days ago. With these we're good to go having v3.13
working both for legacy booting and device tree based booting, and we
can then go ahed and drop the legacy booting for mach-omap2 for v3.14.
* tag 'omap-for-v3.13/yet-more-dt-regressions-take2' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap: (494 commits)
ARM: dts: Fix booting for secure omaps
ARM: OMAP2+: Fix the machine entry for am3517
ARM: dts: Fix missing entries for am3517
ARM: OMAP2+: Fix overwriting hwmod data with data from device tree
+Linux 3.13-rc3
Diffstat (limited to 'Documentation/filesystems')
0 files changed, 0 insertions, 0 deletions