09 Jun, 2019

1 commit

  • Mostly due to x86 and acpi conversion, several documentation
    links are still pointing to the old file. Fix them.

    Signed-off-by: Mauro Carvalho Chehab
    Reviewed-by: Wolfram Sang
    Reviewed-by: Sven Van Asbroeck
    Reviewed-by: Bhupesh Sharma
    Acked-by: Mark Brown
    Signed-off-by: Jonathan Corbet

    Mauro Carvalho Chehab
     

08 May, 2019

1 commit

  • …anaszewski/linux-leds

    Pull LED updates from Jacek Anaszewski:
    "LED core fixes and improvements:

    - avoid races with workqueue
    - Kconfig: pedantic cleanup
    - small fixes for Flash class description

    leds-lt3593:

    - remove unneeded assignment in lt3593_led_probe
    - drop pdata handling code

    leds-blinkm:

    - clean up double assignment to data->i2c_addr

    leds-pca955x, leds-pca963x:

    - revert ACPI support, as it turned out that there is no evidence
    of officially registered ACPI IDs for these devices.
    - make use of device property API

    leds-as3645a:

    - switch to fwnode property API

    LED related addition to ACPI documentation:

    - document how to refer to LEDs from remote nodes

    LED related fix to ALSA line6/toneport driver:

    - avoid polluting led_* namespace

    And lm3532 driver relocation from MFD to LED subsystem, accompanied by
    various improvements and optimizations; it entails also a change in
    omap4-droid4-xt894.dts:

    - leds: lm3532: Introduce the lm3532 LED driver
    - mfd: ti-lmu: Remove LM3532 backlight driver references
    - ARM: dts: omap4-droid4: Update backlight dt properties
    - dt: lm3532: Add lm3532 dt doc and update ti_lmu doc"

    * tag 'leds-for-5.2-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds:
    leds: avoid races with workqueue
    ALSA: line6: Avoid polluting led_* namespace
    leds: lm3532: Introduce the lm3532 LED driver
    mfd: ti-lmu: Remove LM3532 backlight driver references
    ARM: dts: omap4-droid4: Update backlight dt properties
    dt: lm3532: Add lm3532 dt doc and update ti_lmu doc
    leds: Small fixes for Flash class description
    leds: blinkm: clean up double assignment to data->i2c_addr
    leds: pca963x: Make use of device property API
    leds: pca955x: Make use of device property API
    leds: lt3593: Remove unneeded assignment in lt3593_led_probe
    leds: lt3593: drop pdata handling code
    leds: pca955x: Revert "Add ACPI support"
    leds: pca963x: Revert "Add ACPI support"
    drivers: leds: Kconfig: pedantic cleanups
    ACPI: Document how to refer to LEDs from remote nodes
    leds: as3645a: Switch to fwnode property API

    Linus Torvalds
     

26 Apr, 2019

23 commits


28 Mar, 2019

1 commit


19 Mar, 2019

1 commit


07 Mar, 2019

1 commit


14 Jan, 2019

1 commit

  • In some scenario, we need to build initrd with kernel in a single image.
    This can simplify system deployment process by downloading the whole system
    once, such as in IC verification.

    This patch adds support to override ACPI tables from built-in initrd.

    Signed-off-by: Shunyong Yang
    [ rjw: Minor cleanups ]
    Signed-off-by: Rafael J. Wysocki

    Shunyong Yang
     

23 Jul, 2018

6 commits

  • Instead of port and endpoint properties for representing ports and
    endpoints, use the keys of the hierarchical data extension references
    when referring to the port and endpoint nodes. Additionally, use "reg"
    properties as in Device Tree to specify the number of the port or the
    endpoint.

    The keys of the port nodes begin with "port" and the keys of the endpoint
    nodes begin with "endpoint", both followed by "@" character and the number
    of the port or the endpoint.

    These changes have the advantage that no ACPI specific properties need to
    be added to refer to non-device nodes. Additionally, using the name of the
    node instead of an integer property inside the node is easier to parse in
    code and easier for humans to understand.

    Signed-off-by: Sakari Ailus
    Signed-off-by: Rafael J. Wysocki

    Sakari Ailus
     
  • Document that if a port has a single endpoint only, its value shall be
    zero. Similarly, if a device object only has a single port, its value
    shlla be zero.

    Signed-off-by: Sakari Ailus
    Signed-off-by: Rafael J. Wysocki

    Sakari Ailus
     
  • Address a few issues in the ACPI _DSD properties graph documentation:

    - the extension for port nodes is a data extension (and not property
    extension),

    - clean up language in port hierarchical data extension definition,

    - add examples of port and endpoint packages,

    - port property value is the number of the "port" and not the number
    of the "port node",

    - remove word "individual" from endpoint data node description, it
    was redundant,

    - remove the extra "The" in the endpoint property description,

    - refer to hierarchical data extension keys and targets instead of
    first and second package list entries.

    Signed-off-by: Sakari Ailus
    Signed-off-by: Rafael J. Wysocki

    Sakari Ailus
     
  • Hierarchical data extension 1.1 allows using references as the second
    entries of the hierearchical data extension packages. Update the
    references and the examples.

    The quotes are left in documentation for clarity.

    Signed-off-by: Sakari Ailus
    Signed-off-by: Rafael J. Wysocki

    Sakari Ailus
     
  • As part of the hierarchical data extension key naming, introduce numbering
    scheme for the nodes that may be referred to using hierarchical data
    extension references. This allows iterating over particular kind of nodes
    recognised by the node name whilst allowing numbering the nodes, bringing
    ACPI to feature parity with DT in this respect.

    Signed-off-by: Sakari Ailus
    Signed-off-by: Rafael J. Wysocki

    Sakari Ailus
     
  • Add documentation on how to refer to hierarchical data nodes in a
    generic way. This brings ACPI to feature parity with Device Tree in
    terms of being able to refer to any node in the tree.

    Signed-off-by: Sakari Ailus
    Signed-off-by: Rafael J. Wysocki

    Sakari Ailus
     

06 Jun, 2018

1 commit


24 Apr, 2018

1 commit


11 Oct, 2017

1 commit

  • Add functionality to read LPIT table, which provides:

    - Sysfs interface to read residency counters via
    /sys/devices/system/cpu/cpuidle/low_power_idle_cpu_residency_us
    /sys/devices/system/cpu/cpuidle/low_power_idle_system_residency_us

    Here the count "low_power_idle_cpu_residency_us" shows the time spent
    by CPU package in low power state. This is read via MSR interface,
    which points to MSR for PKG C10.

    Here the count "low_power_idle_system_residency_us" show the count the
    system was in low power state. This is read via MMIO interface. This
    is mapped to SLP_S0 residency on modern Intel systems. This residency
    is achieved only when CPU is in PKG C10 and all functional blocks are
    in low power state.

    It is possible that none of the above counters present or anyone of the
    counter present or all counters present.

    For example: On my Kabylake system both of the above counters present.
    After suspend to idle these counts updated and prints:

    6916179
    6998564

    This counter can be read by tools like turbostat to display. Or it can
    be used to debug, if modern systems are reaching desired low power state.

    - Provides an interface to read residency counter memory address

    This address can be used to get the base address of PMC memory
    mapped IO. This is utilized by intel_pmc_core driver to print
    more debug information.

    In addition, to avoid code duplication to read iomem, removed the read of
    iomem from acpi_os_read_memory() in osl.c and made a common function
    acpi_os_read_iomem(). This new function is used for reading iomem in
    in both osl.c and acpi_lpit.c.

    Link: http://www.uefi.org/sites/default/files/resources/Intel_ACPI_Low_Power_S0_Idle.pdf
    Signed-off-by: Srinivas Pandruvada
    Signed-off-by: Rafael J. Wysocki

    Srinivas Pandruvada
     

08 Jul, 2017

1 commit

  • Pull GPIO updates from Linus Walleij:
    "This is the bulk of GPIO changes for the v4.13 series.

    Some administrativa:

    I have a slew of 8250 serial patches and the new IOT2040 serial+GPIO
    driver coming in through this tree, along with a whole bunch of Exar
    8250 fixes. These are ACKed by Greg and also hit drivers/platform/*
    where they are ACKed by Andy Shevchenko.

    Speaking about drivers/platform/* there is also a bunch of ACPI stuff
    coming through that route, again ACKed by Andy.

    The MCP23S08 changes are coming in here as well. You already have the
    commits in your tree, so this is just a result of sharing an immutable
    branch between pin control and GPIO.

    Core:
    - Export add/remove for lookup tables so that modules can export GPIO
    descriptor tables.
    - Handle GPIO sleep states: it is now possible to flag that a GPIO
    line may loose its state during suspend/resume of the system to
    save power. This is used in the Wolfson Micro Arizona driver.
    - ACPI-based GPIO was tightened up a lot around the edges.
    - Use bitmap_fill() to speed up a loop.

    New drivers:
    - Exar XRA1403 SPI-based GPIO.
    - MVEBU driver now supports Armada 7K and 8K.
    - LP87565 PMIC GPIO.
    - Renesas R-CAR R8A7743 (RZ/G1M).
    - The new IOT2040 8250 serial/GPIO also comes in through this
    changeset.

    Substantial driver changes:
    - Seriously fix the Exar 8250 GPIO portions to work.
    - The MCP23S08 was moved out to a pin control driver.
    - Convert MEVEBU to use regmap for register access.
    - Drop Vulcan support from the Broadcom driver.
    - Serious cleanup and improvement of the mockup driver, giving us a
    better test coverage.

    Misc:
    - Lots of janitorial clean up.
    - A bunch of documentation fixes"

    * tag 'gpio-v4.13-1' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio: (70 commits)
    serial: exar: Add support for IOT2040 device
    gpio-exar/8250-exar: Make set of exported GPIOs configurable
    platform: Accept const properties
    serial: exar: Factor out platform hooks
    gpio-exar/8250-exar: Rearrange gpiochip parenthood
    gpio: exar: Fix iomap request
    gpio-exar/8250-exar: Do not even instantiate a GPIO device for Commtech cards
    serial: uapi: Add support for bus termination
    gpio: rcar: Add R8A7743 (RZ/G1M) support
    gpio: gpio-wcove: Fix GPIO control register offset calculation
    gpio: lp87565: Add support for GPIO
    gpio: dwapb: fix missing first irq for edgeboth irq type
    MAINTAINERS: Take maintainership for GPIO ACPI support
    gpio: exar: Fix reading of directions and values
    gpio: exar: Allocate resources on behalf of the platform device
    gpio-exar/8250-exar: Fix passing in of parent PCI device
    gpio: mockup: use devm_kcalloc() where applicable
    gpio: mockup: add myself as author
    gpio: mockup: improve the error message
    gpio: mockup: don't return magic numbers from probe()
    ...

    Linus Torvalds
     

29 May, 2017

1 commit