1. 12 11月, 2010 2 次提交
  2. 11 11月, 2010 4 次提交
  3. 09 11月, 2010 2 次提交
    • J
      x86: mrst: Parse SFI timer table for all timer configs · 7f05dec3
      Jacob Pan 提交于
      Penwell has APB timer based watchdog timers, it requires platform code to parse
      SFI MTMR tables in order to claim its timer.
      
      This patch will always parse SFI MTMR regardless of system timer configuration
      choices. Otherwise, SFI MTMR table may not get parsed if running on Medfield
      with always-on local APIC timers and constant TSC. Watchdog timer driver will
      then not get a timer to use.
      Signed-off-by: NJacob Pan <jacob.jun.pan@linux.intel.com>
      Signed-off-by: NAlan Cox <alan@linux.intel.com>
      LKML-Reference: <20101109112800.20591.10802.stgit@localhost.localdomain>
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      7f05dec3
    • F
      x86/mrst: Add SFI platform device parsing code · 1da4b1c6
      Feng Tang 提交于
      SFI provides a series of tables. These describe the platform devices present
      including SPI and I²C devices, as well as various sensors, keypads and other
      glue as well as interfaces provided via the SCU IPC mechanism (intel_scu_ipc.c)
      
      This patch is a merge of the core elements and relevant fixes from the
      Intel development code by Feng, Alek, myself into a single coherent patch
      for upstream submission.
      
      It provides the needed infrastructure to register I2C, SPI and platform devices
      described by the tables, as well as handlers for some of the hardware already
      supported in kernel. The 0.8 firmware also provides GPIO tables.
      
      Devices are created at boot time or if they are SCU dependant at the point an
      SCU is discovered. The existing Linux device mechanisms will then handle the
      device binding. At an abstract level this is an SFI to Linux device translator.
      
      Device/platform specific setup/glue is in this file. This is done so that the
      drivers for the generic I²C and SPI bus devices remain cross platform as they
      should.
      
      (Updated from RFC version to correct the emc1403 name used by the firmware
       and a wrongly used #define)
      Signed-off-by: NAlek Du <alek.du@linux.intel.com>
      LKML-Reference: <20101109112158.20013.6158.stgit@localhost.localdomain>
      [Clean ups, removal of 0.7 support]
      Signed-off-by: NFeng Tang <feng.tang@linux.intel.com>
      [Clean ups]
      Signed-off-by: NAlan Cox <alan@linux.intel.com>
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      1da4b1c6
  4. 08 11月, 2010 1 次提交
  5. 06 11月, 2010 9 次提交
  6. 04 11月, 2010 5 次提交
  7. 03 11月, 2010 2 次提交
    • P
      m68k, m68knommu: Do not include linux/hardirq.h in asm/irqflags.h · ed35f654
      Philippe De Muyter 提交于
      Recent changes to header files made kernel compilation for m68k/m68knommu
      fail with :
        CC      arch/m68knommu/kernel/asm-offsets.s
      In file included from /archives/linux/git/arch/m68k/include/asm/system.h:2,
                       from include/linux/wait.h:25,
                       from include/linux/mmzone.h:9,
                       from include/linux/gfp.h:4,
                       from include/linux/irq.h:20,
                       from include/asm-generic/hardirq.h:12,
                       from /archives/linux/git/arch/m68k/include/asm/hardirq_no.h:17,
                       from /archives/linux/git/arch/m68k/include/asm/hardirq.h:2,
                       from include/linux/hardirq.h:10,
                       from /archives/linux/git/arch/m68k/include/asm/irqflags.h:5,
                       from include/linux/irqflags.h:15,
                       from include/linux/spinlock.h:53,
                       from include/linux/seqlock.h:29,
                       from include/linux/time.h:8,
                       from include/linux/timex.h:56,
                       from include/linux/sched.h:56,
                       from arch/m68knommu/kernel/asm-offsets.c:12:
      /archives/linux/git/arch/m68k/include/asm/system_no.h: In function ‘__xchg’:
      /archives/linux/git/arch/m68k/include/asm/system_no.h:79: error: implicit
      +declaration of function ‘local_irq_save’
      /archives/linux/git/arch/m68k/include/asm/system_no.h:101: error: implicit
      +declaration of function ‘local_irq_restore’
      
      Fix that
      Signed-off-by: NPhilippe De Muyter <phdm@macqel.be>
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      ed35f654
    • G
      m68knommu: add back in declaration of do_IRQ · 79c1a903
      Greg Ungerer 提交于
      The cleanup and merge of machdep should not have removed the do_IRQ
      declaration. It is needed by the 68328 based targets.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      79c1a903
  8. 02 11月, 2010 8 次提交
    • G
      ARM: mach-shmobile: fix sh7372 after a recent clock framework rework · 5c4e0f19
      Guennadi Liakhovetski 提交于
      The updated sh clock framework has introduced a .nr_freqs element of struct
      clk, which has to be initialised with the number of possible frequencies.
      Signed-off-by: NGuennadi Liakhovetski <g.liakhovetski@gmx.de>
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      5c4e0f19
    • C
      arch/tile: mark "hardwall" device as non-seekable · d02db4f8
      Chris Metcalf 提交于
      Arnd's recent patch series tagged this device with noop_llseek,
      conservatively.  In fact, it should be no_llseek, which we arrange
      for by opening the device with nonseekable_open().
      Signed-off-by: NChris Metcalf <cmetcalf@tilera.com>
      d02db4f8
    • C
      asm-generic/stat.h: support 64-bit file time_t for stat() · 2c7387ef
      Chris Metcalf 提交于
      The existing asm-generic/stat.h specifies st_mtime, etc., as a 32-value,
      and works well for 32-bit architectures (currently microblaze, score,
      and 32-bit tile).  However, for 64-bit architectures it isn't sufficient
      to return 32 bits of time_t; this isn't good insurance against the 2037
      rollover.  (It also makes glibc support less convenient, since we can't
      use glibc's handy STAT_IS_KERNEL_STAT mode.)
      
      This change extends the two "timespec" fields for each of the three atime,
      mtime, and ctime fields from "int" to "long".  As a result, on 32-bit
      platforms nothing changes, and 64-bit platforms will now work as expected.
      
      The only wrinkle is 32-bit userspace under 64-bit kernels taking advantage
      of COMPAT mode.  For these, we leave the "struct stat64" definitions with
      the "int" versions of the time_t and nsec fields, so that architectures
      can implement compat_sys_stat64() and friends with sys_stat64(), etc.,
      and get the expected 32-bit structure layout.  This requires a
      field-by-field copy in the kernel, implemented by the code guarded
      under __ARCH_WANT_STAT64.
      
      This does mean that the shape of the "struct stat" and "struct stat64"
      structures is different on a 64-bit kernel, but only one of the two
      structures should ever be used by any given process: "struct stat"
      is meant for 64-bit userspace only, and "struct stat64" for 32-bit
      userspace only.  (On a 32-bit kernel the two structures continue to have
      the same shape, since "long" is 32 bits.)
      
      The alternative is keeping the two structures the same shape on 64-bit
      kernels, which means a 64-bit time_t in "struct stat64" for 32-bit
      processes.  This is a little unnatural since 32-bit userspace can't
      do anything with 64 bits of time_t information, since time_t is just
      "long", not "int64_t"; and in any case 32-bit userspace might expect
      to be running under a 32-bit kernel, which can't provide the high 32
      bits anyway.  In the case of a 32-bit kernel we'd then be extending the
      kernel's 32-bit time_t to 64 bits, then truncating it back to 32 bits
      again in userspace, for no particular reason.  And, as mentioned above,
      if we have 64-bit time_t for 32-bit processes we can't easily use glibc's
      STAT_IS_KERNEL_STAT, since glibc's stat structure requires an embedded
      "struct timespec", which is a pair of "long" (32-bit) values in a 32-bit
      userspace.  "Inventive" solutions are possible, but are pretty hacky.
      Signed-off-by: NChris Metcalf <cmetcalf@tilera.com>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      2c7387ef
    • C
      arch/tile: don't allow user code to set the PL via ptrace or signal return · 1deb9c5d
      Chris Metcalf 提交于
      The kernel was allowing any component of the pt_regs to be updated either
      by signal handlers writing to the stack, or by processes writing via
      PTRACE_POKEUSR or PTRACE_SETREGS, which meant they could set their PL
      up from 0 to 1 and get access to kernel code and data (or, in practice,
      cause a kernel panic).  We now always reset the ex1 field, allowing the
      user to set their ICS bit only.
      Signed-off-by: NChris Metcalf <cmetcalf@tilera.com>
      1deb9c5d
    • C
      arch/tile: correct double syscall restart for nested signals · 34a89d26
      Chris Metcalf 提交于
      This change is modelled on similar fixes for other architectures.
      The pt_regs "faultnum" member is set to the trap (fault) number that
      caused us to enter the kernel, and is INT_SWINT_1 for the syscall software
      interrupt.  We already supported a pseudo value, INT_SWINT_1_SIGRETURN,
      that we used for the rt_sigreturn syscall; it avoided the case where
      one signal was handled, then we "tail-called" to another handler.
      
      This change avoids the similar case where we start to call one handler,
      then are preempted into another handler when we start trying to run
      the first handler.  We clear ->faultnum after calling handle_signal(),
      and to be paranoid also in the case where there was no signal to deliver.
      Signed-off-by: NChris Metcalf <cmetcalf@tilera.com>
      34a89d26
    • C
      arch/tile: avoid __must_check warning on one strict_strtol check · d59e609d
      Chris Metcalf 提交于
      For the "initfree" boot argument it's not that big a deal, but
      to avoid warnings in the code, we check for a valid value before
      allowing the specified argument to override the kernel default.
      Signed-off-by: NChris Metcalf <cmetcalf@tilera.com>
      d59e609d
    • C
      arch/tile: bomb raw_local_irq_ to arch_local_irq_ · 5d966115
      Chris Metcalf 提交于
      This completes the tile migration to the new naming scheme for
      the architecture-specific irq management code.
      Signed-off-by: NChris Metcalf <cmetcalf@tilera.com>
      5d966115
    • C
      arch/tile: complete migration to new kmap_atomic scheme · 38a6f426
      Chris Metcalf 提交于
      This change makes KM_TYPE_NR independent of the actual deprecated
      list of km_type values, which are no longer used in tile code anywhere.
      For now we leave it set to 8, allowing that many nested mappings,
      and thus reserving 32MB of address space.
      
      A few remaining places using KM_* values were cleaned up as well.
      Signed-off-by: NChris Metcalf <cmetcalf@tilera.com>
      38a6f426
  9. 01 11月, 2010 2 次提交
  10. 31 10月, 2010 2 次提交
  11. 30 10月, 2010 3 次提交