summaryrefslogtreecommitdiff
path: root/.gitignore
diff options
context:
space:
mode:
authorJoel Fernandes <joelf@ti.com>2013-11-27 03:03:36 +0400
committerTony Lindgren <tony@atomide.com>2013-11-27 03:03:36 +0400
commit912e663127c5f700da6805ce21635dce703cb2cc (patch)
treee972462c7d72a64e3a643ea896f522570b89673c /.gitignore
parentedd5eb4e99e4153ea7be05390fda542d986bf28d (diff)
downloadlinux-912e663127c5f700da6805ce21635dce703cb2cc.tar.xz
ARM: OMAP2+: Disable POSTED mode for errata i103 and i767
Enabling of Posted mode is seen to cause problems on dmtimer modules on AM33xx (much like other OMAPs). Reference discussions on forums [1] [2]. Earlier patch solving this on other OMAPs [3]. For OMAP SoCs with this errata, the fix has been to not enable Posted mode. However, on some SoCs (atleast AM33xx) which carry this errata, Posted mode is enabled on reset. So we not only need to ignore enabling of the POSTED bit when the timer is requested, but also disable Posted mode if errata is present. [1] http://e2e.ti.com/support/arm/sitara_arm/f/791/t/285744.aspx [2] http://e2e.ti.com/support/arm/sitara_arm/f/791/t/270632.aspx [3] http://www.spinics.net/lists/linux-omap/msg81770.html Cc: stable@vgerk.kernel.org Reported-by: Russ Dill <russ.dill@ti.com> Cc: Santosh Shilimkar <santosh.shilimkar@ti.com> Signed-off-by: Joel Fernandes <joelf@ti.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions