1. 18 Mar, 2014 2 commits
  2. 01 Mar, 2014 1 commit
  3. 26 Feb, 2014 3 commits
    • Murali Karicheri's avatar
      ARM: dts: keystone: add support for k2 Edison SoC and EVM · 209636b6
      Murali Karicheri authored
      Keystone2 Edison (K2E) is a Quad Cortex A15 based SoC with
      1 DSP. It has standard peripherals such as i2c, spi, uart, timer,
      pcie, etc similar to k2hk, but without wireless hardwares. This
      patch add support for k2 Edison SoC and EVM. This re-uses the common
      keystone.dtsi to include common bindings across the various k2
      devices.
      Signed-off-by: default avatarMurali Karicheri <m-karicheri2@ti.com>
      Signed-off-by: default avatarSantosh Shilimkar <santosh.shilimkar@ti.com>
      209636b6
    • Murali Karicheri's avatar
      ARM: dts: keystone: add support for K2 Lamarr SoC and EVM · fc1c72eb
      Murali Karicheri authored
      Keystone2 Lamarr (K2L) is a dual Cortex A15 core based SoC with
      4 DSPs. It has standard peripherals such as i2c, spi, uart, timer,
      pcie etc., similar to k2hk, but different set of wireless hardware.
      This patch add support for k2 Lamarr SoC and EVM. This re-uses the
      common keystone.dtsi to include common bindings across the various
      k2 devices.
      
      Cc: Olof Johansson <olof@lixom.net>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Rob Herring <robh+dt@kernel.org>
      Cc: Kumar Gala <galak@codeaurora.org>
      Cc: Mark Rutland <mark.rutland@arm.com>
      Signed-off-by: default avatarMurali Karicheri <m-karicheri2@ti.com>
      Signed-off-by: default avatarSantosh Shilimkar <santosh.shilimkar@ti.com>
      fc1c72eb
    • Murali Karicheri's avatar
      ARM: dts: keystone: preparatory patch to support K2L and K2E SOCs · a2067676
      Murali Karicheri authored
      Current keystone.dtsi includes SoC specific definitions for K2HK
      SoCs. In order to support two addition keystone devices, k2 Edison
      and K2 Lamarr and corresponding EVMs, This patch restructure the
      dts files for the following:-
      
       - All clock nodes that are only available in k2hk SoC are moved
         from keystone-clocks.dtsi to a new k2hk-clocks.dtsi include file
       - The CPU nodes are now part of the soc specific k2hk.dtsi.
       - Change the compatibility string to ti,k2hk-evm and change
         the model name accordingly
       - Finally include k2hk-clocks.dtsi in k2hk.dtsi and that in
         k2hk-evm.dts
      
      Cc: Olof Johansson <olof@lixom.net>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Rob Herring <robh+dt@kernel.org>
      Cc: Kumar Gala <galak@codeaurora.org>
      Cc: Mark Rutland <mark.rutland@arm.com>
      Signed-off-by: default avatarMurali Karicheri <m-karicheri2@ti.com>
      Signed-off-by: default avatarSantosh Shilimkar <santosh.shilimkar@ti.com>
      a2067676
  4. 25 Feb, 2014 2 commits
  5. 18 Feb, 2014 1 commit
    • Ivan Khoronzhuk's avatar
      ARM: dts: keystone: drop msmcsram clock node · 5a2abe19
      Ivan Khoronzhuk authored
      At late init all unused clocks are disabled. So clocks that were not
      get before will be gated. In Keysone 2 SoC we have at least one
      necessary clock that is not used by any driver - "msmcsram". This
      clock is necessary, because it supplies the Multicore Shared Memory
      Controller (MSMC). MSMC is the coherency interconnect and all the
      coherent masters are connected to it including devices which are not
      under Linux OS control. MSMC clock should not be touched even in low
      power states.
      
      So drop the clock node, otherwise 'clk_ignore_unused' parameter will
      disable the clock leading to system stall.
      Signed-off-by: default avatarIvan Khoronzhuk <ivan.khoronzhuk@ti.com>
      Signed-off-by: default avatarSantosh Shilimkar <santosh.shilimkar@ti.com>
      5a2abe19
  6. 17 Feb, 2014 5 commits
  7. 03 Feb, 2014 4 commits
    • Linus Torvalds's avatar
      Linus 3.14-rc1 · 38dbfb59
      Linus Torvalds authored
      38dbfb59
    • Linus Torvalds's avatar
      Merge branch 'parisc-3.14' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux · 69048e01
      Linus Torvalds authored
      Pull parisc updates from Helge Deller:
       "The three major changes in this patchset is a implementation for
        flexible userspace memory maps, cache-flushing fixes (again), and a
        long-discussed ABI change to make EWOULDBLOCK the same value as
        EAGAIN.
      
        parisc has been the only platform where we had EWOULDBLOCK != EAGAIN
        to keep HP-UX compatibility.  Since we will probably never implement
        full HP-UX support, we prefer to drop this compatibility to make it
        easier for us with Linux userspace programs which mostly never checked
        for both values.  We don't expect major fall-outs because of this
        change, and if we face some, we will simply rebuild the necessary
        applications in the debian archives"
      
      * 'parisc-3.14' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux:
        parisc: add flexible mmap memory layout support
        parisc: Make EWOULDBLOCK be equal to EAGAIN on parisc
        parisc: convert uapi/asm/stat.h to use native types only
        parisc: wire up sched_setattr and sched_getattr
        parisc: fix cache-flushing
        parisc/sti_console: prefer Linux fonts over built-in ROM fonts
      69048e01
    • Mikulas Patocka's avatar
      hpfs: optimize quad buffer loading · 1c0b8a7a
      Mikulas Patocka authored
      HPFS needs to load 4 consecutive 512-byte sectors when accessing the
      directory nodes or bitmaps.  We can't switch to 2048-byte block size
      because files are allocated in the units of 512-byte sectors.
      
      Previously, the driver would allocate a 2048-byte area using kmalloc,
      copy the data from four buffers to this area and eventually copy them
      back if they were modified.
      
      In the current implementation of the buffer cache, buffers are allocated
      in the pagecache.  That means that 4 consecutive 512-byte buffers are
      stored in consecutive areas in the kernel address space.  So, we don't
      need to allocate extra memory and copy the content of the buffers there.
      
      This patch optimizes the code to avoid copying the buffers.  It checks
      if the four buffers are stored in contiguous memory - if they are not,
      it falls back to allocating a 2048-byte area and copying data there.
      Signed-off-by: default avatarMikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      1c0b8a7a
    • Mikulas Patocka's avatar
      hpfs: remember free space · 2cbe5c76
      Mikulas Patocka authored
      Previously, hpfs scanned all bitmaps each time the user asked for free
      space using statfs.  This patch changes it so that hpfs scans the
      bitmaps only once, remembes the free space and on next invocation of
      statfs it returns the value instantly.
      
      New versions of wine are hammering on the statfs syscall very heavily,
      making some games unplayable when they're stored on hpfs, with load
      times in minutes.
      
      This should be backported to the stable kernels because it fixes
      user-visible problem (excessive level load times in wine).
      Signed-off-by: default avatarMikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>
      Cc: stable@vger.kernel.org
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      2cbe5c76
  8. 02 Feb, 2014 12 commits
  9. 01 Feb, 2014 10 commits