1. 10 7月, 2011 1 次提交
    • S
      OMAP4: clock data: Keep GPMC clocks always enabled and hardware managed · 93cac2ad
      Santosh Shilimkar 提交于
      On OMAP4, CPU accesses on unmapped addresses are redirected to GPMC by
      L3 interconnect. Because of CPU speculative nature, such accesses are
      possible which can lead to indirect access to GPMC and if it's clock is
      not running, it can result in hang/abort on the platform.
      
      Above makes access to GPMC unpredictable during the execution, so it's
      module mode needs to be kept under hardware control instead of software
      control.
      Since the auto gating is supported for GPMC, there isn't any power impact
      because of this change.
      
      The issue was un-covered with security middleware running along with HLOS.
      In this case GPMC had a valid MMU descriptor on secure side where as HLOS
      didn't map the GMPC because it isn't being used.
      Signed-off-by: NSantosh Shilimkar <santosh.shilimkar@ti.com>
      [b-cousson@ti.com: Update subject and fix typos in the changelog]
      Signed-off-by: NBenoit Cousson <b-cousson@ti.com>
      Cc: Kevin Hilman <khilman@ti.com>
      Cc: Rajendra Nayak <rnayak@ti.com>
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      93cac2ad
  2. 12 6月, 2011 1 次提交
  3. 10 6月, 2011 1 次提交
  4. 05 6月, 2011 1 次提交
  5. 04 6月, 2011 6 次提交
  6. 02 6月, 2011 4 次提交
  7. 01 6月, 2011 16 次提交
  8. 31 5月, 2011 5 次提交
  9. 29 5月, 2011 1 次提交
    • E
      ns: Wire up the setns system call · 7b21fddd
      Eric W. Biederman 提交于
      32bit and 64bit on x86 are tested and working.  The rest I have looked
      at closely and I can't find any problems.
      
      setns is an easy system call to wire up.  It just takes two ints so I
      don't expect any weird architecture porting problems.
      
      While doing this I have noticed that we have some architectures that are
      very slow to get new system calls.  cris seems to be the slowest where
      the last system calls wired up were preadv and pwritev.  avr32 is weird
      in that recvmmsg was wired up but never declared in unistd.h.  frv is
      behind with perf_event_open being the last syscall wired up.  On h8300
      the last system call wired up was epoll_wait.  On m32r the last system
      call wired up was fallocate.  mn10300 has recvmmsg as the last system
      call wired up.  The rest seem to at least have syncfs wired up which was
      new in the 2.6.39.
      
      v2: Most of the architecture support added by Daniel Lezcano <dlezcano@fr.ibm.com>
      v3: ported to v2.6.36-rc4 by: Eric W. Biederman <ebiederm@xmission.com>
      v4: Moved wiring up of the system call to another patch
      v5: ported to v2.6.39-rc6
      v6: rebased onto parisc-next and net-next to avoid syscall  conflicts.
      v7: ported to Linus's latest post 2.6.39 tree.
      
      >  arch/blackfin/include/asm/unistd.h     |    3 ++-
      >  arch/blackfin/mach-common/entry.S      |    1 +
      Acked-by: NMike Frysinger <vapier@gentoo.org>
      
      Oh - ia64 wiring looks good.
      Acked-by: NTony Luck <tony.luck@intel.com>
      Signed-off-by: NEric W. Biederman <ebiederm@xmission.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      7b21fddd
  10. 28 5月, 2011 1 次提交
  11. 27 5月, 2011 3 次提交