Hi!
A few comments, but I didn't get to finish a thorough review yet.
On Thu, Jun 07, 2018 at 11:12:12AM -0700, Matthias Kaehlcke wrote:
> The purpose of the throttler is to provide support for non-thermal
> throttling. Throttling is triggered by external event, e.g. the
> detection of a high battery discharge current, close to the OCP limit
> of the battery. The throttler is only in charge of the throttling, not
> the monitoring, which is done by another (possibly platform specific)
> driver.
>
> Signed-off-by: Matthias Kaehlcke <mka@xxxxxxxxxxxx>
> ---
> Changes in v2:
> - completely reworked the driver to support configuration through OPPs, which
> requires a more dynamic handling
> - added sysfs attribute to set the level for debugging and testing
> - Makefile: depend on Kconfig option to traverse throttler directory
> - Kconfig: removed 'default n'
> - added SPDX line instead of license boiler-plate
> - added entry to MAINTAINERS file
>
>
> MAINTAINERS | 7 +
> drivers/misc/Kconfig | 1 +
> drivers/misc/Makefile | 1 +
> drivers/misc/throttler/Kconfig | 14 +
> drivers/misc/throttler/Makefile | 1 +
> drivers/misc/throttler/core.c | 642 ++++++++++++++++++++++++++++++++
> include/linux/throttler.h | 11 +
> 7 files changed, 677 insertions(+)
> create mode 100644 drivers/misc/throttler/Kconfig
> create mode 100644 drivers/misc/throttler/Makefile
> create mode 100644 drivers/misc/throttler/core.c
> create mode 100644 include/linux/throttler.h
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 92e47b5b0480..f9550e5680ce 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -13938,6 +13938,13 @@ T: git git://repo.or.cz/linux-2.6/linux-acpi-2.6/ibm-acpi-2.6.git
> S: Maintained
> F: drivers/platform/x86/thinkpad_acpi.c
>
> +THROTTLER DRIVERS
> +M: Matthias Kaehlcke <mka@xxxxxxxxxxxx>
> +L: linux-pm@xxxxxxxxxxxxxxx
> +S: Maintained
> +F: drivers/misc/throttler/
> +F: include/linux/throttler.h
> +
> THUNDERBOLT DRIVER
> M: Andreas Noever <andreas.noever@xxxxxxxxx>
> M: Michael Jamet <michael.jamet@xxxxxxxxx>
> diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
> index 5d713008749b..691d9625d83c 100644
> --- a/drivers/misc/Kconfig
> +++ b/drivers/misc/Kconfig
> @@ -513,4 +513,5 @@ source "drivers/misc/echo/Kconfig"
> source "drivers/misc/cxl/Kconfig"
> source "drivers/misc/ocxl/Kconfig"
> source "drivers/misc/cardreader/Kconfig"
> +source "drivers/misc/throttler/Kconfig"
> endmenu
> diff --git a/drivers/misc/Makefile b/drivers/misc/Makefile
> index 20be70c3f118..b549ccad5215 100644
> --- a/drivers/misc/Makefile
> +++ b/drivers/misc/Makefile
> @@ -57,3 +57,4 @@ obj-$(CONFIG_ASPEED_LPC_SNOOP) += aspeed-lpc-snoop.o
> obj-$(CONFIG_PCI_ENDPOINT_TEST) += pci_endpoint_test.o
> obj-$(CONFIG_OCXL) += ocxl/
> obj-$(CONFIG_MISC_RTSX) += cardreader/
> +obj-$(CONFIG_THROTTLER) += throttler/
> diff --git a/drivers/misc/throttler/Kconfig b/drivers/misc/throttler/Kconfig
> new file mode 100644
> index 000000000000..e561f1df5085
> --- /dev/null
> +++ b/drivers/misc/throttler/Kconfig
> @@ -0,0 +1,14 @@
> +# SPDX-License-Identifier: GPL-2.0
> +
> +menuconfig THROTTLER
> + bool "Throttler support"
> + depends on OF
> + select CPU_FREQ
> + select PM_DEVFREQ
I'm curious whether we're actually truly compile-time dependent on
{CPU,DEV}FREQ? It seems like those subsystems mostly stub out stuff so
they fall back to no-ops if not built in.
I know that's not very useful for your existing throttler, since it
wouldn't be very effective if one or both were disabled.
> + help
> + This option enables core support for non-thermal throttling of CPUs
> + and devfreq devices.
> +
> + Note that you also need a event monitor module usually called
> + *_throttler.
> +
> diff --git a/drivers/misc/throttler/Makefile b/drivers/misc/throttler/Makefile
> new file mode 100644
> index 000000000000..c8d920cee315
> --- /dev/null
> +++ b/drivers/misc/throttler/Makefile
> @@ -0,0 +1 @@
> +obj-$(CONFIG_THROTTLER) += core.o
> diff --git a/drivers/misc/throttler/core.c b/drivers/misc/throttler/core.c
> new file mode 100644
> index 000000000000..15b50c111032
> --- /dev/null
> +++ b/drivers/misc/throttler/core.c
> @@ -0,0 +1,642 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Core code for non-thermal throttling
> + *
> + * Copyright (C) 2018 Google, Inc.
> + */
> +
> +#include <linux/cpufreq.h>
> +#include <linux/cpumask.h>
> +#include <linux/devfreq.h>
> +#include <linux/kernel.h>
> +#include <linux/list.h>
> +#include <linux/mutex.h>
> +#include <linux/notifier.h>
> +#include <linux/of.h>
> +#include <linux/of_platform.h>
> +#include <linux/platform_device.h>
> +#include <linux/pm_opp.h>
> +#include <linux/sort.h>
> +#include <linux/slab.h>
> +#include <linux/throttler.h>
> +
> +/*
> + * Non-thermal throttling: throttling of system components in response to
> + * external events (e.g. high battery discharge current).
> + *
> + * The throttler supports throttling through cpufreq and devfreq. Multiple
> + * levels of throttling can be configured. At level 0 no throttling is
> + * active on behalf of the throttler, for values > 0 throttling is typically
> + * configured to be increasingly aggressive with each level.
> + * The number of throttling levels is not limited by the throttler (though
> + * it is likely limited by the throttling devices). It is not necessary to
> + * configure the same number of levels for all throttling devices. If the
> + * requested throttling level for a device is higher than the maximum level
> + * of the device the throttler will select the maximum throttling level of
> + * the device.
> + *
> + * Non-thermal throttling is split in two parts:
> + *
> + * - throttler core
> + * - parses the thermal policy
> + * - applies throttling settings for a requested level of throttling
> + *
> + * - event monitor driver
> + * - monitors events that trigger throttling
> + * - determines the throttling level (often limited to on/off)
> + * - asks throttler core to apply throttling settings
> + *
> + * It is possible for a system to have more than one throttler and the
> + * throttlers may make use of the same throttling devices, in case of
> + * conflicting settings for a device the more aggressive values will be
> + * applied.
> + *
> + */
> +
> +#define ci_to_throttler(ci) \
> + container_of(ci, struct throttler, devfreq.class_iface)
> +
> +// #define DEBUG_THROTTLER
Did you mean to leave your debug code in? Seems like you have some
related dead code under #ifdefs.
(If you do want this, maybe it'd be better under debugfs, until somebody
really wants to formalize and document it.)
> +
> +struct thr_freq_table {
> + uint32_t *freqs;
> + int n_entries;
> +};
> +
> +struct cpufreq_thrdev {
> + uint32_t cpu;
> + struct thr_freq_table freq_table;
> + struct list_head node;
> +};
> +
> +struct devfreq_thrdev {
> + struct devfreq *devfreq;
> + struct thr_freq_table freq_table;
> + struct throttler *thr;
> + struct notifier_block nb;
> + struct list_head node;
> +};
> +
> +struct __thr_cpufreq {
> + struct list_head list;
> + cpumask_t cm_initialized;
> + cpumask_t cm_ignore;
> + struct notifier_block nb;
> +};
> +
> +struct __thr_devfreq {
> + struct list_head list;
> + struct class_interface class_iface;
> +};
> +
> +struct throttler {
> + struct device *dev;
> + int level;
> + struct __thr_cpufreq cpufreq;
> + struct __thr_devfreq devfreq;
> + struct mutex lock;
> +};
> +
> +static inline int cmp_freqs(const void *a, const void *b)
> +{
> + const uint32_t *pa = a, *pb = b;
> +
> + if (*pa < *pb)
> + return 1;
> + else if (*pa > *pb)
> + return -1;
> +
> + return 0;
> +}
> +
> +static int thr_handle_devfreq_event(struct notifier_block *nb,
> + unsigned long event, void *data);
> +
> +static unsigned long thr_get_throttling_freq(struct thr_freq_table *ft,
> + int level)
> +{
> + if (level == 0) {
> + WARN(true, "level == 0");
> + return ULONG_MAX;
> + }
> +
> + if (level <= ft->n_entries)
> + return ft->freqs[level - 1];
> + else
> + return ft->freqs[ft->n_entries - 1];
> +}
> +
> +static int thr_init_freq_table(struct throttler *thr, struct device *opp_dev,
> + struct thr_freq_table *ft)
> +{
> + struct device_node *np_opp_desc, *np_opp;
> + int nchilds;
> + uint32_t *freqs;
> + int nfreqs = 0;
> + int err = 0;
> +
> + np_opp_desc = dev_pm_opp_of_get_opp_desc_node(opp_dev);
> + if (!np_opp_desc)
> + return -EINVAL;
> +
> + nchilds = of_get_child_count(np_opp_desc);
> + if (!nchilds) {
> + err = -EINVAL;
> + goto out_node_put;
> + }
> +
> + freqs = kzalloc(nchilds * sizeof(uint32_t), GFP_KERNEL);
> + if (!freqs) {
> + err = -ENOMEM;
> + goto out_node_put;
> + }
> +
> + /* determine which OPPs are used by this throttler (if any) */
> + for_each_child_of_node(np_opp_desc, np_opp) {
> + int num_thr;
> + int i;
> +
> + num_thr = of_property_count_u32_elems(np_opp, "opp-throttlers");
> + if (num_thr < 0)
> + continue;
> +
> + for (i = 0; i < num_thr; i++) {
> + struct device_node *np_thr;
> + struct platform_device *pdev;
> +
> + np_thr = of_parse_phandle(np_opp, "opp-throttlers", i);
> + if (!np_thr) {
> + dev_err(thr->dev,
> + "failed to parse phandle %d: %s\n", i,
> + np_opp->full_name);
> + continue;
> + }
> +
> + pdev = of_find_device_by_node(np_thr);
> + if (!pdev) {
> + dev_err(thr->dev,
> + "could not find throttler dev: %s\n",
> + np_thr->full_name);
> + of_node_put(np_thr);
> + continue;
> + }
> +
> + /* OPP is used by this throttler */
> + if (&pdev->dev == thr->dev) {
So you're assuming that all throttlers are platform devices? Seems
slightly shaky; I could easily imagine a similar device that's a SPI or
I2C device.
> + u64 rate;
> +
> + err = of_property_read_u64(np_opp, "opp-hz",
> + &rate);
> + if (!err) {
> + freqs[nfreqs] = rate;
> + nfreqs++;
> + } else {
> + dev_err(thr->dev,
> + "opp-hz not found: %s\n",
> + np_opp->full_name);
> + }
> + }
> +
> + of_node_put(np_thr);
> + put_device(&pdev->dev);
> + }
> + }
> +
> + if (nfreqs > 0) {
> + /* sort frequencies in descending order */
> + sort(freqs, nfreqs, sizeof(*freqs), cmp_freqs, NULL);
> +
> + ft->n_entries = nfreqs;
> + ft->freqs = devm_kzalloc(thr->dev,
> + nfreqs * sizeof(*freqs), GFP_KERNEL);
> + if (!ft->freqs) {
> + err = -ENOMEM;
> + goto out_free;
> + }
> +
> + memcpy(ft->freqs, freqs, nfreqs * sizeof(*freqs));
> + } else {
> + err = -ENODEV;
> + }
> +
> +out_free:
> + kfree(freqs);
> +
> +out_node_put:
> + of_node_put(np_opp_desc);
> +
> + return err;
> +}
[...]
Brian
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
