Eric Lee / smarc-fsl-linux-kernel

15 Oct, 2007

1 commit

13 Oct, 2007

5 commits

  • efefc6eb3   Merge master.kernel.org:/pub/scm/linux/kernel/git/gregkh/driver-2.6 ... Browse Code »

    * master.kernel.org:/pub/scm/linux/kernel/git/gregkh/driver-2.6: (75 commits)
    PM: merge device power-management source files
    sysfs: add copyrights
    kobject: update the copyrights
    kset: add some kerneldoc to help describe what these strange things are
    Driver core: rename ktype_edd and ktype_efivar
    Driver core: rename ktype_driver
    Driver core: rename ktype_device
    Driver core: rename ktype_class
    driver core: remove subsystem_init()
    sysfs: move sysfs file poll implementation to sysfs_open_dirent
    sysfs: implement sysfs_open_dirent
    sysfs: move sysfs_dirent->s_children into sysfs_dirent->s_dir
    sysfs: make sysfs_root a regular directory dirent
    sysfs: open code sysfs_attach_dentry()
    sysfs: make s_elem an anonymous union
    sysfs: make bin attr open get active reference of parent too
    sysfs: kill unnecessary NULL pointer check in sysfs_release()
    sysfs: kill unnecessary sysfs_get() in open paths
    sysfs: reposition sysfs_dirent->s_mode.
    sysfs: kill sysfs_update_file()
    ...

    Linus Torvalds
     
  • 60043428a   Convert from class_device to device for drivers/video ... Browse Code »

    Convert from class_device to device for drivers/video.

    Signed-off-by: Tony Jones
    Signed-off-by: Kay Sievers
    Signed-off-by: Greg Kroah-Hartman

    tonyj@suse.de
     
  • 19c38de88   kobjects: fix up improper use of the kobject name field ... Browse Code »

    A number of different drivers incorrect access the kobject name field
    directly. This is not correct as the name might not be in the array.
    Use the proper accessor function instead.

    Greg Kroah-Hartman
     
  • 7eff2e7a8   Driver core: change add_uevent_var to use a struct ... Browse Code »

    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
     
  • 43ca7ec96   ACPI: remove the now unused ifdef code ... Browse Code »

    The conversion of x86-64 to clock events makes the
    #ifdef CONFIG_GENERIC_CLOCKEVENTS
    n the timer broadcast functions useless. Remove it.

    Signed-off-by: Thomas Gleixner
    Cc: john stultz
    Cc: Andi Kleen
    Signed-off-by: Andrew Morton
    Signed-off-by: Ingo Molnar
    Signed-off-by: Arjan van de Ven

    Thomas Gleixner
     

12 Oct, 2007

2 commits

  • 19f71153b   Merge git://git.kernel.org/pub/scm/linux/kernel/git/bart/ide-2.6 ... Browse Code »

    * git://git.kernel.org/pub/scm/linux/kernel/git/bart/ide-2.6: (24 commits)
    ide: use only ->set_pio_mode method for programming PIO modes (take 2)
    sis5513: don't change UDMA settings when programming PIO
    it8213/piix/slc90e66: don't change DMA settings when programming PIO
    alim15x3: PIO mode setup fixes
    siimage: fix ->set_pio_mode method to select PIO data transfer
    cs5520: don't enable VDMA in ->speedproc
    sc1200: remove redundant warning message from sc1200_tune_chipset()
    ide-pmac: PIO mode setup fixes (take 3)
    icside: fix ->speedproc to return on unsupported modes (take 5)
    sgiioc4: use ide_tune_dma()
    amd74xx/via82cxxx: use ide_tune_dma()
    ide: add ide_set{_max}_pio() (take 4)
    ide: Kconfig face-lift
    ide: move ide_rate_filter() calls to the upper layer (take 2)
    sis5513: add ->udma_filter method for chipset_family >= ATA_133
    ide: mode limiting fixes for user requested speed changes
    ide: add missing ide_rate_filter() calls to ->speedproc()-s
    ide: call udma_filter() before resorting to the UltraDMA mask
    ide: make jmicron match vendor and device class
    pdc202xx_new: switch to using pci_get_slot() (take 2)
    ...

    Linus Torvalds
     
  • 5e32132be   ide: hook ACPI _PSx method to IDE power on/off ... Browse Code »

    ACPI spec defines the sequence of IDE power on/off:
    Powering down:
    Call _GTM.
    Power down drive (calls _PS3 method and turns off power planes).
    Powering up:
    Power up drive (calls _PS0 method if present and turns on power planes).
    Call _STM passing info from _GTM (possibly modified), with ID data from
    each drive.
    Initialize the channel.
    May modify the results of _GTF.
    For each drive:
    Call _GTF.
    Execute task file (possibly modified).
    This patch adds the missed _PS0/_PS3 methods call.

    Signed-off-by: Shaohua Li
    Acked-by: Len Brown
    Signed-off-by: Bartlomiej Zolnierkiewicz

    Shaohua Li
     

10 Oct, 2007

1 commit

  • 1855256c4   drivers/firmware: const-ify DMI API and internals ... Browse Code »

    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
     

26 Sep, 2007

2 commits

23 Sep, 2007

1 commit

  • b04e7bdb9   ACPI: disable lower idle C-states across suspend/resume ... Browse Code »
    44

    device_suspend() calls ACPI suspend functions, which seems to have undesired
    side effects on lower idle C-states. It took me some time to realize that
    especially the VAIO BIOSes (both Andrews jinxed UP and my elfstruck SMP one)
    show this effect. I'm quite sure that other bug reports against suspend/resume
    about turning the system into a brick have the same root cause.

    After fishing in the dark for quite some time, I realized that removing the ACPI
    processor module before suspend (this removes the lower C-state functionality)
    made the problem disappear. Interestingly enough the propability of having a
    bricked box is influenced by various factors (interrupts, size of the ram image,
    ...). Even adding a bunch of printks in the wrong places made the problem go
    away. The previous periodic tick implementation simply pampered over the
    problem, which explains why the dyntick / clockevents changes made this more
    prominent.

    We avoid complex functionality during the boot process and we have to do the
    same during suspend/resume. It is a similar scenario and equaly fragile.

    Add suspend / resume functions to the ACPI processor code and disable the lower
    idle C-states across suspend/resume. Fall back to the default idle
    implementation (halt) instead.

    Signed-off-by: Thomas Gleixner
    Tested-by: Andrew Morton
    Cc: Len Brown
    Cc: Venkatesh Pallipadi
    Cc: Rafael J. Wysocki
    Signed-off-by: Linus Torvalds

    Thomas Gleixner
     

22 Sep, 2007

2 commits

21 Sep, 2007

1 commit

  • f216cc374   ACPI: suspend: consolidate handling of Sx states. ... Browse Code »

    Recent changes to sleep initialization in ACPI dropped reporting of supported Sx
    states above S3. Fix that and also move S5 init into same file as other Sx.
    The only functional change is adding printk() for S4 and S5 cases.

    Signed-off-by: Alexey Starikovskiy
    Acked-by: Rafael J. Wysocki
    Signed-off-by: Len Brown

    Alexey Starikovskiy
     

19 Sep, 2007

2 commits

  • 7f10cc4e8   ACPI: video: remove dmesg spam ... Browse Code »

    i am actually heavily using the ACPI video extension for my Thinkpad X61
    Tablet. I have bound the input events triggered by the brightness
    up/down keys to a simple

    echo > /sys/class/backlight/acpi_video1/brightness

    but everytime the event is triggered and acpi_video_device_lcd_set_level()
    is called i got a notificication in my kernel log like:

    set_level status: 0
    set_level status: 0
    set_level status: 0
    set_level status: 0
    ...

    Signed-off-by: Maik Broemme
    Signed-off-by: Len Brown

    Maik Broemme
     
  • a21101c46   ACPI: video: _DOS=0 by default to prevent hotkey hang ... Browse Code »

    In the past, the Linux/ACPI video driver invoked _DOS
    (Display Output Switch) with the parameter 1
    to tell the BIOS to switch the video output display for us.

    But this conflicts with Linux native graphics drivers,
    and can cause all sorts of issues, including hanging the system.

    http://bugzilla.kernel.org/show_bug.cgi?id=6001

    Here we change the Linux default to evaluate _DOS=0,
    which tells the BIOS to simply send us a hotkey event
    and not touch the graphics hardware.

    The acpi video driver sends the display switch hotkey
    event up through the intput layer, and X can interpret
    that and use its native graphics driver to switch the display.

    For the case where Linux has no native graphics driver running,
    or the graphics driver doesn't know how to switch video and
    the BIOS (safely) does, the previous behaviour can be restored with:

    # echo 1 > /proc/acpi/video/*/DOS

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

    Zhang Rui
     

17 Sep, 2007

1 commit

16 Sep, 2007

1 commit

03 Sep, 2007

1 commit

31 Aug, 2007

1 commit

29 Aug, 2007

1 commit

28 Aug, 2007

1 commit

  • 721ebe005   reverse CONFIG_ACPI_PROC_EVENT default ... Browse Code »

    Sigh. Again an ACPI assault on the Thinkpad's Fn+F4 to suspend to RAM.
    The default and text for CONFIG_THINKPAD_ACPI_INPUT_ENABLED were fixed
    in -rc3, but now commit 14e04fb34ffa82ee61ae69f98d8fca12d2e8e31c ("ACPI:
    Schedule /proc/acpi/event for removal") introduces the ACPI_PROC_EVENT
    config entry, and defaults it to 'n' to disable it again.

    Change default to y, and add comment to make it clearer that n is for
    future distros.

    Signed-off-by: Hugh Dickins
    Cc: Andrew Morton
    Cc: Len Brown
    Signed-off-by: Linus Torvalds

    Hugh Dickins
     

25 Aug, 2007

17 commits