17 Oct, 2007

1 commit

  • The Synchronous Serial Controller (SSC) on Atmel microprocessors are
    capable of tranceiving many frame based protocols, like I2S. Tested on the
    AT32AP7000/ATSTK1000.

    This driver is used in the ALSA sound driver for the AT73C213 external DAC
    on the ATSTK1000 development board for AVR32. This sound driver will be
    submitted soon.

    Hardware documentation can be found in the AT32AP7000 data sheet, which can
    be downloaded from
    http://www.atmel.com/dyn/products/datasheets.asp?family_id=682

    [akpm@linux-foundation.org: init spinlock at compile time]
    Signed-off-by: Hans-Christian Egtvedt
    Acked-by: Haavard Skinnemoen
    Cc: David Brownell
    Cc: Andrew Victor
    Cc: Patrice Vilchez
    Cc: Nicolas Ferre
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Hans-Christian Egtvedt
     

16 Oct, 2007

1 commit


15 Oct, 2007

1 commit

  • * 'release' of git://lm-sensors.org/kernel/mhoffman/hwmon-2.6: (53 commits)
    hwmon: (vt8231) fix sparse warning
    hwmon: (sis5595) fix sparse warning
    hwmon: (w83627hf) don't assume bank 0
    hwmon: (w83627hf) Fix setting fan min right after driver load
    hwmon: (w83627hf) De-macro sysfs callback functions
    hwmon: Add new combined driver for FSC chips
    hwmon: (ibmpex) Release IPMI user if hwmon registration fails
    hwmon: (dme1737) Add sch311x support
    hwmon: (dme1737) group functions logically
    hwmon: (dme1737) cleanups
    hwmon: IBM power meter driver
    hwmon: (coretemp) Add support for Celeron 4xx
    hwmon: (lm87) Disable VID when it should be
    hwmon: (w83781d) Add individual alarm and beep files
    hwmon: VRM is not read from registers
    MAINTAINERS: update hwmon subsystem git trees
    hwmon: Fix the code examples in documentation
    hwmon: update sysfs interface document - error handling
    hwmon: (thmc50) Fix a debug message
    hwmon: (thmc50) Don't create temp3 if not enabled
    ...

    Linus Torvalds
     

13 Oct, 2007

1 commit

  • This changes the uevent buffer functions to use a struct instead of a
    long list of parameters. It does no longer require the caller to do the
    proper buffer termination and size accounting, which is currently wrong
    in some places. It fixes a known bug where parts of the uevent
    environment are overwritten because of wrong index calculations.

    Many thanks to Mathieu Desnoyers for finding bugs and improving the
    error handling.

    Signed-off-by: Kay Sievers
    Cc: Mathieu Desnoyers
    Cc: Cornelia Huck
    Signed-off-by: Greg Kroah-Hartman

    Kay Sievers
     

12 Oct, 2007

1 commit

  • * 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc: (408 commits)
    [POWERPC] Add memchr() to the bootwrapper
    [POWERPC] Implement logging of unhandled signals
    [POWERPC] Add legacy serial support for OPB with flattened device tree
    [POWERPC] Use 1TB segments
    [POWERPC] XilinxFB: Allow fixed framebuffer base address
    [POWERPC] XilinxFB: Add support for custom screen resolution
    [POWERPC] XilinxFB: Use pdata to pass around framebuffer parameters
    [POWERPC] PCI: Add 64-bit physical address support to setup_indirect_pci
    [POWERPC] 4xx: Kilauea defconfig file
    [POWERPC] 4xx: Kilauea DTS
    [POWERPC] 4xx: Add AMCC Kilauea eval board support to platforms/40x
    [POWERPC] 4xx: Add AMCC 405EX support to cputable.c
    [POWERPC] Adjust TASK_SIZE on ppc32 systems to 3GB that are capable
    [POWERPC] Use PAGE_OFFSET to tell if an address is user/kernel in SW TLB handlers
    [POWERPC] 85xx: Enable FP emulation in MPC8560 ADS defconfig
    [POWERPC] 85xx: Killed
    [POWERPC] 85xx: Add cpm nodes for 8541/8555 CDS
    [POWERPC] 85xx: Convert mpc8560ads to the new CPM binding.
    [POWERPC] mpc8272ads: Remove muram from the CPM reg property.
    [POWERPC] Make clockevents work on PPC601 processors
    ...

    Fixed up conflict in Documentation/powerpc/booting-without-of.txt manually.

    Linus Torvalds
     

10 Oct, 2007

2 commits

  • Convert from class_device to device for hwmon_device_register/unregister

    Signed-off-by: Tony Jones
    Signed-off-by: Greg Kroah-Hartman
    Signed-off-by: Kay Sievers
    Signed-off-by: Mark M. Hoffman

    Tony Jones
     
  • Three main sets of changes:

    1) dmi_get_system_info() return value should have been marked const,
    since callers should not be changing that data.

    2) const-ify DMI internals, since DMI firmware tables should,
    whenever possible, be marked const to ensure we never ever write to
    that data area.

    3) const-ify DMI API, to enable marking tables const where possible
    in low-level drivers.

    And if we're really lucky, this might enable some additional
    optimizations on the part of the compiler.

    The bulk of the changes are #2 and #3, which are interrelated. #1 could
    have been a separate patch, but it was so small compared to the others,
    it was easier to roll it into this changeset.

    Signed-off-by: Jeff Garzik

    Jeff Garzik
     

03 Oct, 2007

6 commits


17 Sep, 2007

3 commits

  • Len Brown
     
  • Name it thinkpad-acpi version 0.16 to avoid any confusion with some 0.15
    thinkpad-acpi development snapshots and backports that had input layer
    support, but no hotkey_report_mode support.

    Signed-off-by: Henrique de Moraes Holschuh
    Signed-off-by: Len Brown

    Henrique de Moraes Holschuh
     
  • Revert new 2.6.23 CONFIG_THINKPAD_ACPI_INPUT_ENABLED Kconfig option because
    it would create a legacy we don't want to support.

    CONFIG_THINKPAD_ACPI_INPUT_ENABLED was added to try to fix an issue that is
    now moot with the addition of the netlink ACPI event report interface to
    the ACPI core.

    Now that ACPI core can send events over netlink, we can use a different
    strategy to keep backwards compatibility with older userspace, without the
    need for the CONFIG_THINKPAD_ACPI_INPUT_ENABLED games. And it arrived
    before CONFIG_THINKPAD_ACPI_INPUT_ENABLED made it to a stable mainline
    kernel, even, which is Good.

    This patch is in sync with some changes to thinkpad-acpi backports, that
    will keep things sane for userspace across different combinations of kernel
    versions, thinkpad-acpi backports (or the lack thereof), and userspace
    capabilities:

    Unless a module parameter is used, thinkpad-acpi will now behave in such a
    way that it will work well (by default) with userspace that still uses only
    the old ACPI procfs event interface and doesn't care for thinkpad-acpi
    input devices.

    It will also always work well with userspace that has been updated to use
    both the thinkpad-acpi input devices, and ACPI core netlink event
    interface, regardless of any module parameter.

    The module parameter was added to allow thinkpad-acpi to work with
    userspace that has been partially updated to use thinkpad-acpi input
    devices, but not the new ACPI core netlink event interface. To use this
    mode of hot key reporting, one has to specify the hotkey_report_mode=2
    module parameter.

    The thinkpad-acpi driver exports the value of hotkey_report_mode through
    sysfs, as well. thinkpad-acpi backports to older kernels, that do not
    support the new ACPI core netlink interface, have code to allow userspace
    to switch hotkey_report_mode at runtime through sysfs. This capability
    will not be provided in mainline thinkpad-acpi as it is not needed there.

    Signed-off-by: Henrique de Moraes Holschuh
    Cc: Michael S. Tsirkin
    Cc: Hugh Dickins
    Cc: Richard Hughes
    Signed-off-by: Len Brown

    Henrique de Moraes Holschuh
     

29 Aug, 2007

1 commit


25 Aug, 2007

2 commits


24 Aug, 2007

5 commits

  • The asus laptop driver conditionnaly registers leds in asus_led_register()
    depending on their availability, but unconditionnaly unregisters them all at
    exit time or when the module fails to load. Unregistering not registered leds
    result in the following Oops. So we should check before unregistering.

    [] do_page_fault+0x511/0x5e9
    [] error_code+0x6a/0x70
    [] device_unregister+0x26/0x32
    [] led_classdev_unregister+0x58/0x94 [led_class]
    [] asus_led_exit+0x17/0x41 [asus_laptop]
    [] asus_laptop_exit+0xd/0x3f [asus_laptop]
    [] sys_delete_module+0x17b/0x1a2
    [] sysenter_past_esp+0x6b/0xa1

    EIP: [] device_del+0xb/0x23a SS:ESP 0068:f594ef0c

    Signed-off-by: Guillaume Chazarain
    Signed-off-by: Len Brown

    Guillaume Chazarain
     
  • sonypi_compat uses a kfifo that needs to be present before _SRS is
    called to be able to cope with the IRQs triggered when setting
    resources.

    Signed-off-by: Mattia Dongili
    Signed-off-by: Len Brown

    Mattia Dongili
     
  • Signed-off-by: Mattia Dongili
    Signed-off-by: Len Brown

    Mattia Dongili
     
  • Schedule /proc/acpi/event for removal in 6 months.

    Re-name acpi_bus_generate_event() to acpi_bus_generate_proc_event()
    to make sure there is no confusion that it is for /proc/acpi/event only.

    Add CONFIG_ACPI_PROC_EVENT to allow removal of /proc/acpi/event.
    There is no functional change if CONFIG_ACPI_PROC_EVENT=y

    Signed-off-by: Len Brown

    Len Brown
     
  • The previous events patch added a netlink event for every
    user of the legacy /proc/acpi/event interface.

    However, some users of /proc/acpi/event are really input events,
    and they already report their events via the input layer.

    Introduce a new interface, acpi_bus_generate_netlink_event(),
    which is explicitly called by devices that want to repoprt
    events via netlink. This allows the input-like events
    to opt-out of generating netlink events. In summary:

    events that are sent via netlink:
    ac/battery/sbs
    thermal
    processor
    thinkpad_acpi dock/bay

    events that are sent via input layer:
    button
    video hotkey
    thinkpad_acpi hotkey
    asus_acpi/asus-laptop hotkey
    sonypi/sonylaptop

    Signed-off-by: Zhang Rui
    Signed-off-by: Len Brown

    Zhang Rui
     

19 Aug, 2007

1 commit


12 Aug, 2007

1 commit


08 Aug, 2007

1 commit

  • The current kconfig help text was misleading users. Also, the default for
    an input-layer-optimized support caused way too many problems without
    up-to-date userspace in place.

    So, rework the help text, and change the default to N. Note that
    distributions are supposed to enable this option as soon as they update HAL
    to a version that handles the thinkpad-acpi new input layer interface.

    Signed-off-by: Henrique de Moraes Holschuh
    Cc: Michael S. Tsirkin
    Cc: Hugh Dickins
    Signed-off-by: Len Brown

    Henrique de Moraes Holschuh
     

04 Aug, 2007

3 commits


25 Jul, 2007

1 commit


24 Jul, 2007

2 commits

  • modpost is going to use these to create e.g. acpi:ACPI0001
    in modules.alias.

    Signed-off-by: Thomas Renninger
    Signed-off-by: Len Brown

    Thomas Renninger
     
  • > Subject : drivers/misc/asus-laptop.c:*: error: 'struct led_classdev' has no member named 'class_dev'
    > References : http://lkml.org/lkml/2007/7/22/299
    > Submitter : Gabriel C

    Fallout from f8a7c6fe14f556ca8eeddce258cb21392d0c3a2f. However, looking
    at it shows that checks done in ASUS_LED_UNREGISTER() can't trigger
    at all (we never get to asus_led_exit() if registration fails) and
    if that registration fails, we actually leak stuff. IOW, it's worse
    than just replacing class_dev with dev in there - the tests themselves
    had been papering over the lousy cleanup logics.

    Signed-off-by: Al Viro
    Signed-off-by: Len Brown

    Al Viro
     

22 Jul, 2007

7 commits