Skip to content
  1. Apr 16, 2014
    • Stephen Warren's avatar
      ARM: tegra: add Jetson TK1 device tree · 15e524a4
      Stephen Warren authored
      
      
      Jetson TK1 is an NVIDIA Tegra124 development board, containing Tegra124,
      2GB RAM, eMMC, SD card, SPI flash, serial port, PCIe Ethernet, HDMI,
      audio, mini PCIe, JTAG, SATA, and an expansion IO connector containing
      GPIOs, I2C, SPI, CSI, eDP, etc.
      
      The following features work with this device tree: UART, SD card, eMMC,
      SPI flash, USB (full-size jack, and mini-PCIe), audio, AS3722 RTC, system
      power-off, suspend/resume (LP1) with wake via RTC alarm.
      
      The following features should work with this device tree, but are not
      validated: Expansion I2C, expansion SPI, expansion GPIO, gpio-key for the
      power button.
      
      The following features are not yet implemented in this device tree: Most
      voltage regulators, expansion UART, HDMI, eDP, PCIe (Ethernet, and mini-
      PCIe connector), CSI, SATA.
      
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      15e524a4
  2. Apr 11, 2014
  3. Apr 09, 2014
  4. Apr 08, 2014
    • Russell King's avatar
      ARM: add missing system_misc.h include to process.c · 779dd959
      Russell King authored
      
      
      arm_pm_restart(), arm_pm_idle() and soft_restart() are all declared in
      system_misc.h, but this file is not included in process.c.  Add this
      missing include.  Found via sparse:
      
      arch/arm/kernel/process.c:98:6: warning: symbol 'soft_restart' was not declared. Should it be static?
      arch/arm/kernel/process.c:127:6: warning: symbol 'arm_pm_restart' was not declared. Should it be static?
      arch/arm/kernel/process.c:134:6: warning: symbol 'arm_pm_idle' was not declared. Should it be static?
      
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      779dd959
    • Uwe Kleine-König's avatar
      Kconfig: rename HAS_IOPORT to HAS_IOPORT_MAP · ce816fa8
      Uwe Kleine-König authored
      
      
      If the renamed symbol is defined lib/iomap.c implements ioport_map and
      ioport_unmap and currently (nearly) all platforms define the port
      accessor functions outb/inb and friend unconditionally.  So
      HAS_IOPORT_MAP is the better name for this.
      
      Consequently NO_IOPORT is renamed to NO_IOPORT_MAP.
      
      The motivation for this change is to reintroduce a symbol HAS_IOPORT
      that signals if outb/int et al are available.  I will address that at
      least one merge window later though to keep surprises to a minimum and
      catch new introductions of (HAS|NO)_IOPORT.
      
      The changes in this commit were done using:
      
      	$ git grep -l -E '(NO|HAS)_IOPORT' | xargs perl -p -i -e 's/\b((?:CONFIG_)?(?:NO|HAS)_IOPORT)\b/$1_MAP/'
      
      Signed-off-by: default avatarUwe Kleine-König <u.kleine-koenig@pengutronix.de>
      Acked-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      ce816fa8
  5. Apr 07, 2014
  6. Apr 04, 2014
  7. Apr 02, 2014
  8. Apr 01, 2014
  9. Mar 31, 2014
    • Jeff Layton's avatar
      locks: add new fcntl cmd values for handling file private locks · 5d50ffd7
      Jeff Layton authored
      
      
      Due to some unfortunate history, POSIX locks have very strange and
      unhelpful semantics. The thing that usually catches people by surprise
      is that they are dropped whenever the process closes any file descriptor
      associated with the inode.
      
      This is extremely problematic for people developing file servers that
      need to implement byte-range locks. Developers often need a "lock
      management" facility to ensure that file descriptors are not closed
      until all of the locks associated with the inode are finished.
      
      Additionally, "classic" POSIX locks are owned by the process. Locks
      taken between threads within the same process won't conflict with one
      another, which renders them useless for synchronization between threads.
      
      This patchset adds a new type of lock that attempts to address these
      issues. These locks conflict with classic POSIX read/write locks, but
      have semantics that are more like BSD locks with respect to inheritance
      and behavior on close.
      
      This is implemented primarily by changing how fl_owner field is set for
      these locks. Instead of having them owned by the files_struct of the
      process, they are instead owned by the filp on which they were acquired.
      Thus, they are inherited across fork() and are only released when the
      last reference to a filp is put.
      
      These new semantics prevent them from being merged with classic POSIX
      locks, even if they are acquired by the same process. These locks will
      also conflict with classic POSIX locks even if they are acquired by
      the same process or on the same file descriptor.
      
      The new locks are managed using a new set of cmd values to the fcntl()
      syscall. The initial implementation of this converts these values to
      "classic" cmd values at a fairly high level, and the details are not
      exposed to the underlying filesystem. We may eventually want to push
      this handing out to the lower filesystem code but for now I don't
      see any need for it.
      
      Also, note that with this implementation the new cmd values are only
      available via fcntl64() on 32-bit arches. There's little need to
      add support for legacy apps on a new interface like this.
      
      Signed-off-by: default avatarJeff Layton <jlayton@redhat.com>
      5d50ffd7
    • Hans de Goede's avatar
      ARM: sun7i/sun6i: dts: Fix IRQ number for sun6i NMI controller · 536a44d4
      Hans de Goede authored
      
      
      The IRQ line used in sun6i-a31.dtsi for the NMI controller is wrong.
      This causes a IRQ storm since the NMI controller is repeatedly fired.
      This patch fixes this problem assigning the correct IRQ number to the
      NMI controller.
      
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
      Signed-off-by: default avatarCarlo Caione <carlo@caione.org>
      Cc: maxime.ripard@free-electrons.com
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: linux-sunxi@googlegroups.com
      Link: http://lkml.kernel.org/r/1395939759-11135-2-git-send-email-carlo@caione.org
      
      
      Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
      536a44d4
    • Daniel Borkmann's avatar
      net: filter: add jited flag to indicate jit compiled filters · f8bbbfc3
      Daniel Borkmann authored
      
      
      This patch adds a jited flag into sk_filter struct in order to indicate
      whether a filter is currently jited or not. The size of sk_filter is
      not being expanded as the 32 bit 'len' member allows upper bits to be
      reused since a filter can currently only grow as large as BPF_MAXINSNS.
      
      Therefore, there's enough room also for other in future needed flags to
      reuse 'len' field if necessary. The jited flag also allows for having
      alternative interpreter functions running as currently, we can only
      detect jit compiled filters by testing fp->bpf_func to not equal the
      address of sk_run_filter().
      
      Joint work with Alexei Starovoitov.
      
      Signed-off-by: default avatarAlexei Starovoitov <ast@plumgrid.com>
      Signed-off-by: default avatarDaniel Borkmann <dborkman@redhat.com>
      Cc: Pablo Neira Ayuso <pablo@netfilter.org>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      f8bbbfc3
  10. Mar 29, 2014