1. 08 8月, 2006 1 次提交
  2. 01 8月, 2006 2 次提交
    • A
      [POWERPC] clean up pseries hcall interfaces · b9377ffc
      Anton Blanchard 提交于
      Our pseries hcall interfaces are out of control:
      
      	plpar_hcall_norets
      	plpar_hcall
      	plpar_hcall_8arg_2ret
      	plpar_hcall_4out
      	plpar_hcall_7arg_7ret
      	plpar_hcall_9arg_9ret
      
      Create 3 interfaces to cover all cases:
      
      	plpar_hcall_norets:	7 arguments no returns
      	plpar_hcall:		6 arguments 4 returns
      	plpar_hcall9:		9 arguments 9 returns
      
      There are only 2 cases in the kernel that need plpar_hcall9, hopefully
      we can keep it that way.
      
      Pass in a buffer to stash return parameters so we avoid the &dummy1,
      &dummy2 madness.
      Signed-off-by: NAnton Blanchard <anton@samba.org>
      --
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      b9377ffc
    • M
      [PATCH] powermac: More powermac backlight fixes · 4b755999
      Michael Hanselmann 提交于
      This patch fixes several problems:
      - The legacy backlight value might be set at interrupt time. Introduced
        a worker to prevent it from directly calling the backlight code.
      - via-pmu allows the backlight to be grabbed, in which case we need to
        prevent other kernel code from changing the brightness.
      - Don't send PMU requests in via-pmu-backlight when the machine is about
        to sleep or waking up.
      - More Kconfig fixes.
      Signed-off-by: NMichael Hanselmann <linux-kernel@hansmi.ch>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: "Antonino A. Daplas" <adaplas@pol.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      4b755999
  3. 31 7月, 2006 8 次提交
  4. 28 7月, 2006 3 次提交
  5. 25 7月, 2006 2 次提交
  6. 14 7月, 2006 1 次提交
  7. 13 7月, 2006 9 次提交
  8. 11 7月, 2006 2 次提交
    • M
      [PATCH] powermac: Combined fixes for backlight code · e01af038
      Michael Hanselmann 提交于
      This patch fixes several problems:
      - pmac_backlight_key() is called under interrupt context, and therefore
        can't use mutexes or semaphores, so defer the backlight level for
        later, as it's not critical (original code by Aristeu S. Rozanski F.
        <aris@valeta.org>).
      - Add exports for functions that might be called from modules
      - Fix Kconfig depdencies on PMAC_BACKLIGHT.
      - Fix locking issues on calls from inside the driver (reported by
        Aristeu S. Rozanski F., too)
      - Fix wrong calculation of backlight values in some of the drivers
      - Replace pmac_backlight_key_up/down by inline functions
      
      [akpm@osdl.org: fix function prototypes]
      Signed-off-by: NMichael Hanselmann <linux-kernel@hansmi.ch>
      Acked-by: NAristeu S. Rozanski F. <aris@valeta.org>
      Acked-by: NRene Nussbaumer <linux-kernel@killerfox.forkbomb.ch>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      e01af038
    • 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
  9. 07 7月, 2006 4 次提交
  10. 04 7月, 2006 2 次提交
  11. 03 7月, 2006 6 次提交