29 Sep, 2020

1 commit

  • Previously, devfreq core support 'devfreq-events' property in order to get
    the devfreq-event device by phandle. But, 'devfreq-events' property name is
    not proper on devicetree binding because this name doesn't mean
    the any h/w attribute.

    The devfreq-event core hand over the rights to decide the property name
    for getting the devfreq-event device on devicetree. Each devfreq-event driver
    will decide the property name on devicetree binding and then pass
    the their own property name to devfreq_event_get_edev_by_phandle function.

    And change the prototype of devfreq_event_get_edev_count function
    because of used deprecated 'devfreq-events' property.

    Acked-by: Krzysztof Kozlowski
    Signed-off-by: Chanwoo Choi

    Chanwoo Choi
     

30 Jul, 2020

1 commit


30 Dec, 2019

1 commit


19 Jun, 2019

1 commit

  • Based on 2 normalized pattern(s):

    this program is free software you can redistribute it and or modify
    it under the terms of the gnu general public license version 2 as
    published by the free software foundation

    this program is free software you can redistribute it and or modify
    it under the terms of the gnu general public license version 2 as
    published by the free software foundation #

    extracted by the scancode license scanner the SPDX license identifier

    GPL-2.0-only

    has been chosen to replace the boilerplate/reference in 4122 file(s).

    Signed-off-by: Thomas Gleixner
    Reviewed-by: Enrico Weigelt
    Reviewed-by: Kate Stewart
    Reviewed-by: Allison Randal
    Cc: linux-spdx@vger.kernel.org
    Link: https://lkml.kernel.org/r/20190604081206.933168790@linutronix.de
    Signed-off-by: Greg Kroah-Hartman

    Thomas Gleixner
     

16 Apr, 2019

1 commit

  • Convert string compares of DT node names to use of_node_name_eq helper
    instead. This removes direct access to the node name pointer.

    For instances using of_node_cmp, this has the side effect of now using
    case sensitive comparisons. This should not matter for any FDT based
    system which all of these are.

    Cc: Chanwoo Choi
    Cc: MyungJoo Ham
    Cc: Kyungmin Park
    Cc: Kukjin Kim
    Cc: Krzysztof Kozlowski
    Cc: linux-pm@vger.kernel.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: linux-samsung-soc@vger.kernel.org
    Signed-off-by: Rob Herring
    Signed-off-by: MyungJoo Ham

    Rob Herring
     

28 Aug, 2017

1 commit

  • Now that we have a custom printf format specifier, convert users of
    full_name to use %pOF instead. This is preparation to remove storing
    of the full path string for each node.

    Signed-off-by: Rob Herring
    Reviewed-by: Chanwoo Choi
    Signed-off-by: MyungJoo Ham
    Cc: Kyungmin Park
    Cc: linux-pm@vger.kernel.org

    Rob Herring
     

31 Jan, 2017

1 commit

  • This patch just removes '.' character from the sysfs name of devfreq-event
    device as following. Usually, the subsystem uses the similiar naming style
    such as {framework name}{Number}.
    - old : /sys/class/devfreq-event/event.(X)
    - new : /sys/class/devfreq-event/event(X)

    And this patch initializes the value of 'event_no' with -1
    in order to remove the unneeded operation (-1) when calling
    the atomic_inc_return(&event_no).

    Lastly, this patch adds the ABI document for devfreq-event class.

    Signed-off-by: Chanwoo Choi
    Signed-off-by: MyungJoo Ham

    Chanwoo Choi
     

06 Jul, 2016

1 commit

  • The Kconfig currently controlling compilation of this code is:

    menuconfig PM_DEVFREQ_EVENT
    bool "DEVFREQ-Event device Support"

    ...meaning that it currently is not being built as a module by anyone.

    Lets remove the modular code that is essentially orphaned, so that
    when reading the driver there is no doubt it is builtin-only.

    This code wasn't using module_init, so we don't need to be concerned
    with altering the initcall level here.

    We don't replace module.h with init.h since the file already has that.
    But we do add export.h since this file does export some symbols.

    We also delete the MODULE_LICENSE tag etc. since all that information
    is already contained at the top of the file in the comments.

    Signed-off-by: Paul Gortmaker
    Acked-by: Chanwoo Choi
    Signed-off-by: MyungJoo Ham

    Paul Gortmaker
     

03 May, 2016

1 commit

  • This patch use the phandle to find the instance of devfreq-event device in
    Device Tree when calling the devfreq_event_get_edev_by_phandle() because there
    is two type devfreq-event devices as following:

    First case, exynos-ppmu.c driver provides the maximum four event of each PPMU.
    So, when getting the instance of devfreq-event device, using the unique name of
    struct devfreq_event_desc.

    Second case, exynos-nocp.c driver provide the only one event of each NoC Probe
    device. So, when getting the instance of devfreq-event device, using the
    phandle of each NoC probe device.

    Signed-off-by: Chanwoo Choi
    Acked-by: MyungJoo Ham

    Chanwoo Choi
     

13 Jan, 2016

2 commits


30 Jan, 2015

1 commit

  • This patch adds a new class in devfreq, devfreq_event, which provides
    raw data (e.g., memory bus utilization, GPU utilization) for devfreq
    governors.

    - devfreq_event device : Provides raw data for a governor of a devfreq device
    - devfreq device : Monitors device state and changes frequency/voltage
    of the device using the raw data from its
    devfreq_event device.

    A devfreq device dertermines performance states (normally the frequency
    and the voltage vlues) based on the results its designtated devfreq governor:
    e.g., ondemand, performance, powersave.

    In order to give such results required by a devfreq device, the devfreq
    governor requires data that indicates the performance requirement given
    to the devfreq device. The conventional (previous) implementatino of
    devfreq subsystem requires a devfreq device driver to implement its own
    mechanism to acquire performance requirement for its governor. However,
    there had been issues with such requirements:

    1. Although performance requirement of such devices is usually acquired
    from common devices (PMU/PPMU), we do not have any abstract structure to
    represent them properly.
    2. Such performance requirement devices (PMU/PPMU) are actual hardware
    pieces that may be represented by Device Tree directly while devfreq device
    itself is a virtual entity that are not considered to be represented by
    Device Tree according to Device Tree folks.

    In order to address such issues, a devferq_event device (represented by
    this patch) provides a template for device drivers representing
    performance monitoring unit, which gives the basic or raw data for
    preformance requirement, which in turn, is required by devfreq governors.

    The following description explains the feature of two kind of devfreq class:
    - devfreq class (existing)
    : devfreq consumer device use raw data from devfreq_event device for
    determining proper current system state and change voltage/frequency
    dynamically using various governors.

    - devfreq_event class (new)
    : Provide measured raw data to devfreq device for governor

    Cc: MyungJoo Ham
    Cc: Kyungmin Park
    Signed-off-by: Chanwoo Choi
    [Commit message rewritten & conflict resolved by MyungJoo]
    Signed-off-by: MyungJoo Ham

    Chanwoo Choi