1. 28 8月, 2006 1 次提交
  2. 15 8月, 2006 1 次提交
  3. 06 8月, 2006 3 次提交
  4. 05 8月, 2006 1 次提交
  5. 03 8月, 2006 1 次提交
  6. 01 8月, 2006 3 次提交
  7. 22 7月, 2006 1 次提交
  8. 19 7月, 2006 2 次提交
  9. 15 7月, 2006 9 次提交
  10. 14 7月, 2006 1 次提交
  11. 13 7月, 2006 1 次提交
    • I
      [PATCH] lockdep: HPET/RTC fix · 0f749646
      Ingo Molnar 提交于
      Joseph Fannin reported that hpet_rtc_interrupt() enables hardirqs
      in irq context:
      
      [   25.628000]  [<c014af4e>] trace_hardirqs_on+0xce/0x200
      [   25.628000]  [<c036cf21>] _spin_unlock_irq+0x31/0x70
      [   25.628000]  [<c0296584>] rtc_get_rtc_time+0x44/0x1a0
      [   25.628000]  [<c01198bb>] hpet_rtc_interrupt+0x21b/0x280
      [   25.628000]  [<c0161141>] handle_IRQ_event+0x31/0x70
      [   25.628000]  [<c0162d37>] handle_edge_irq+0xe7/0x210
      [   25.628000]  [<c0106192>] do_IRQ+0x92/0x120
      [   25.628000]  [<c0104121>] common_interrupt+0x25/0x2c
      
      the call of rtc_get_rtc_time() is highly suspect. At a minimum we
      need the patch below to save/restore hardirq state.
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      Cc: Joseph Fannin <jfannin@gmail.com>
      Cc: John Stultz <johnstul@us.ibm.com>
      Cc: Arjan van de Ven <arjan@linux.intel.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      0f749646
  12. 11 7月, 2006 9 次提交
    • C
      [PATCH] snsc: switch from force_sig to kill_proc · 5c318bef
      Christoph Hellwig 提交于
      Currently the snsc driver uses force_sig to send init a SIGPWR when the
      system overheats.  This patch switches it to kill_proc instead which has
      the following advantages:
      
       (1) gets rid of one of the last remaining tasklist_lock users
           in modular code
       (2) simplifies the snsc code significantly
      
      The downside is that an init implementation could in theory block SIGPWR
      and it would not get delivered.  The sysvinit code used by all major
      distributions doesn't do this and blocking this signal in init would be a
      rather stupid thing to do.
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      5c318bef
    • J
      [PATCH] pc8736x_gpio: fix re-modprobe errors: fix/finish cdev-init · babcfade
      Jim Cromie 提交于
      - Switch from register_chrdev() to   (register|alloc)_chrdev_region().
      
      - use a cdev.  This was intended for original patchset, but was
        overlooked.
      
        We use a single cdev for all pins (minor device-numbers), as gleaned
        from cs5535_gpio, and in contrast to whats currently done in scx200_gpio
        (which I'll fix soon)
      Signed-off-by: NJim Cromie <jim.cromie@gmail.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      babcfade
    • J
      [PATCH] pc8736x_gpio: fix re-modprobe errors: undo region reservation · 27385085
      Jim Cromie 提交于
      Fix module-init-func by repairing usage of platform_device_del/put in
      module-exit-func.  IOW, it imitates Ingo's 'mishaps' patch, which fixed the
      module-init-func's undo handling.
      
      Also fixes lack of release_region to undo the earlier registration.
      
      Also starts to 'use a cdev' which was originally intended (its present in
      scx200_gpio).  Code compiles and runs, exhibits a lesser error than
      previously.  (re-register-chrdev fails)
      
      Since I had to add "include <linux/cdev.h>", I went ahead and made 2
      tweaks that fell into diff-context-window:
      - remove include <linux/config.h>      everyone's doing it
      - copyright updates - current date is 'wrong'
      Signed-off-by: NJim Cromie <jim.cromie@gmail.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      27385085
    • J
      [PATCH] pc8736x_gpio: fix re-modprobe errors: define and use constants · 4f197842
      Jim Cromie 提交于
      add constant defines - preparatory patch
      
      - adds #define CONSTs  for max-pin,  gpio-addr-range (for reserving region)
      - fix wrong max-pin check in gpio_open()
      - add 'Winbond' to module description.  NSC sold the product, Winbond
        has supported us / lm-sensors
      Signed-off-by: NJim Cromie <jim.cromie@gmail.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      4f197842
    • M
      [PATCH] char/rtc: Handle memory-mapped chips properly · 38e0e8c0
      Maciej W. Rozycki 提交于
      Handle memory-mapped chips properly, needed for example on DECstations.
      This support was in Linux 2.4 but for some reason got lost in 2.6.  This
      patch is taken directly from the linux-mips repository.
      
      [akpm@osdl.org: cleanup]
      Signed-off-by: NMaciej W. Rozycki <macro@linux-mips.org>
      Signed-off-by: NMartin Michlmayr <tbm@cyrius.com>
      Cc: Paul Gortmaker <penguin@muskoka.com>
      Cc: Ralf Baechle <ralf@linux-mips.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      38e0e8c0
    • L
      [PATCH] make valid_mmap_phys_addr_range() take a pfn · 06c67bef
      Lennert Buytenhek 提交于
      Newer ARMs have a 40 bit physical address space, but mapping physical
      memory above 4G needs a special page table format which we (currently?) do
      not use for userspace mappings, so what happens instead is that mapping an
      address >= 4G will happily discard the upper bits and wrap.
      
      There is a valid_mmap_phys_addr_range() arch hook where we could check for
      >= 4G addresses and deny the mapping, but this hook takes an unsigned long
      address:
      
      	static inline int valid_mmap_phys_addr_range(unsigned long addr, size_t size);
      
      And drivers/char/mem.c:mmap_mem() calls it like this:
      
      	static int mmap_mem(struct file * file, struct vm_area_struct * vma)
      	{
      		size_t size = vma->vm_end - vma->vm_start;
      
      		if (!valid_mmap_phys_addr_range(vma->vm_pgoff << PAGE_SHIFT, size))
      
      So that's not much help either.
      
      This patch makes the hook take a pfn instead of a phys address.
      Signed-off-by: NLennert Buytenhek <buytenh@wantstofly.org>
      Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>
      Cc: "Luck, Tony" <tony.luck@intel.com>
      Cc: Russell King <rmk@arm.linux.org.uk>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      06c67bef
    • B
      [PATCH] powerpc: fix trigger handling in the new irq code · 6e99e458
      Benjamin Herrenschmidt 提交于
      This patch slightly reworks the new irq code to fix a small design error.  I
      removed the passing of the trigger to the map() calls entirely, it was not a
      good idea to have one call do two different things.  It also fixes a couple of
      corner cases.
      
      Mapping a linux virtual irq to a physical irq now does only that.  Setting the
      trigger is a different action which has a different call.
      
      The main changes are:
      
      - I no longer call host->ops->map() for an already mapped irq, I just return
        the virtual number that was already mapped.  It was called before to give an
        opportunity to change the trigger, but that was causing issues as that could
        happen while the interrupt was in use by a device, and because of the
        trigger change, map would potentially muck around with things in a racy way.
         That was causing much burden on a given's controller implementation of
        map() to get it right.  This is much simpler now.  map() is only called on
        the initial mapping of an irq, meaning that you know that this irq is _not_
        being used.  You can initialize the hardware if you want (though you don't
        have to).
      
      - Controllers that can handle different type of triggers (level/edge/etc...)
        now implement the standard irq_chip->set_type() call as defined by the
        generic code.  That means that you can use the standard set_irq_type() to
        configure an irq line manually if you wish or (though I don't like that
        interface), pass explicit trigger flags to request_irq() as defined by the
        generic kernel interfaces.  Also, using those interfaces guarantees that
        your controller set_type callback is called with the descriptor lock held,
        thus providing locking against activity on the same interrupt (including
        mask/unmask/etc...) automatically.  A result is that, for example, MPIC's
        own map() implementation calls irq_set_type(NONE) to configure the hardware
        to the default triggers.
      
      - To allow the above, the irq_map array entry for the new mapped interrupt
        is now set before map() callback is called for the controller.
      
      - The irq_create_of_mapping() (also used by irq_of_parse_and_map()) function
        for mapping interrupts from the device-tree now also call the separate
        set_irq_type(), and only does so if there is a change in the trigger type.
      
      - While I was at it, I changed pci_read_irq_line() (which is the helper I
        would expect most archs to use in their pcibios_fixup() to get the PCI
        interrupt routing from the device tree) to also handle a fallback when the
        DT mapping fails consisting of reading the PCI_INTERRUPT_PIN to know wether
        the device has an interrupt at all, and the the PCI_INTERRUPT_LINE to get an
        interrupt number from the device.  That number is then mapped using the
        default controller, and the trigger is set to level low.  That default
        behaviour works for several platforms that don't have a proper interrupt
        tree like Pegasos.  If it doesn't work for your platform, then either
        provide a proper interrupt tree from the firmware so that fallback isn't
        needed, or don't call pci_read_irq_line()
      
      - Add back a bit that got dropped by my main rework patch for properly
        clearing pending IPIs on pSeries when using a kexec
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Paul Mackerras <paulus@samba.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      6e99e458
    • C
      [PATCH] Add Specialix IO8+ card support hotplug support · 7691030b
      Chuck Short 提交于
      Patch Description:
      Add "Specialix IO8+ card support" hotplug support
      
      patch location:
      http://www.kernel.org/git/?p=linux/kernel/git/bcollins/ubuntu-dapper.git;a=commitdiff;h=d795cfc591bb44f6b3d86d8f054a227cecb44bb4
      
      [akpm@osdl.org: cleanup]
      Cc: Randy Dunlap <randy.dunlap@oracle.com>
      Signed-off-by: NChuck Short <zulcss@gmail.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      7691030b
    • C
      [PATCH] Add Computone IntelliPort Plus serial hotplug support · eb0e71c7
      Chuck Short 提交于
      Patch Description:
      Add "Computone IntelliPort Plus serial" hotplug support
      
      patch location:
      http://www.kernel.org/git/?p=linux/kernel/git/bcollins/ubuntu-dapper.git;a=commitdiff;h=8c36723187c0fa5efe0e5c6a9b1e66ed4b824792
      
      [akpm@osdl.org: cleanup]
      Cc: Randy Dunlap <randy.dunlap@oracle.com>
      Signed-off-by: NChuck Short <zulcss@gmail.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      eb0e71c7
  13. 06 7月, 2006 2 次提交
  14. 04 7月, 2006 5 次提交