19 Jun, 2017

1 commit

  • Since all second level thermal IRQs are consumed by the same
    device(bxt_wcove_thermal), there is no need to expose them as separate
    interrupts. We can just export only the first level IRQs for thermal and
    let the device(bxt_wcove_thermal) driver handle the second level IRQs
    based on thermal interrupt status register. Also, just using only the
    first level IRQ will eliminate the bug involved in requesting only the
    second level IRQ and not explicitly enable the first level IRQ. For
    more info on this issue please read the details at,

    https://lkml.org/lkml/2017/2/27/148

    This patch also makes relevant change in bxt_wcove_thermal driver to use
    only first level PMIC thermal IRQ.

    Signed-off-by: Kuppuswamy Sathyanarayanan
    Acked-by: Zhang Rui
    Reviewed-by: Andy Shevchenko
    Signed-off-by: Lee Jones

    Kuppuswamy Sathyanarayanan
     

27 Sep, 2016

1 commit

  • Added one additional parameter to thermal_zone_device_update() to provide
    caller with an optional capability to specify reason.
    Currently this event is used by user space governor to trigger different
    processing based on event code. Also it saves an additional call to read
    temperature when the event is received.
    The following events are cuurently defined:
    - Unspecified event
    - New temperature sample
    - Trip point violated
    - Trip point changed
    - thermal device up and down
    - thermal device power capability changed

    Signed-off-by: Srinivas Pandruvada
    Signed-off-by: Zhang Rui

    Srinivas Pandruvada
     

06 Sep, 2016

1 commit

  • This change adds support for Intel BXT Whiskey Cove PMIC thermal
    driver which is intended to handle the alert interrupts triggered
    upon thermal trip point cross and notify the thermal framework
    appropriately with the zone, temp, crossed trip and event details.

    Signed-off-by: Yegnesh S Iyer
    Signed-off-by: Bin Gao
    Signed-off-by: Zhang Rui

    Bin Gao