0x10000040 0 l=J a,jfn\m1h 53_ub &=LyZof5 +WM3֯HNOϩO.JM,IO+I(3! l4( (  fB- 0 ?_I|+//* SPDX-License-Identifier: GPL-2.0-only */ /* * powercap.h: Data types and headers for sysfs power capping interface * Copyright (c) 2013, Intel Corporation. */ #ifndef __POWERCAP_H__ #define __POWERCAP_H__ #include #include /* * A power cap class device can contain multiple powercap control_types. * Each control_type can have multiple power zones, which can be independently * controlled. Each power zone can have one or more constraints. */ struct powercap_control_type; struct powercap_zone; struct powercap_zone_constraint; /** * struct powercap_control_type_ops - Define control type callbacks * @set_enable: Enable/Disable whole control type. * Default is enabled. But this callback allows all zones * to be in disable state and remove any applied power * limits. If disabled power zone can only be monitored * not controlled. * @get_enable: get Enable/Disable status. * @release: Callback to inform that last reference to this * control type is closed. So it is safe to free data * structure associated with this control type. * This callback is mandatory if the client own memory * for the control type. * * This structure defines control type callbacks to be implemented by client * drivers */ struct powercap_control_type_ops { int (*set_enable) (struct powercap_control_type *, bool mode); int (*get_enable) (struct powercap_control_type *, bool *mode); int (*release) (struct powercap_control_type *); }; /** * struct powercap_control_type - Defines a powercap control_type * @dev: device for this control_type * @idr: idr to have unique id for its child * @nr_zones: counter for number of zones of this type * @ops: Pointer to callback struct * @lock: mutex for control type * @allocated: This is possible that client owns the memory * used by this structure. In this case * this flag is set to false by framework to * prevent deallocation during release process. * Otherwise this flag is set to true. * @node: linked-list node * * Defines powercap control_type. This acts as a container for power * zones, which use same method to control power. E.g. RAPL, RAPL-PCI etc. * All fields are private and should not be used by client drivers. */ struct powercap_control_type { struct device dev; struct idr idr; int nr_zones; const struct powercap_control_type_ops *ops; struct mutex lock; bool allocated; struct list_head node; }; /** * struct powercap_zone_ops - Define power zone callbacks * @get_max_energy_range_uj: Get maximum range of energy counter in * micro-joules. * @get_energy_uj: Get current energy counter in micro-joules. * @reset_energy_uj: Reset micro-joules energy counter. * @get_max_power_range_uw: Get maximum range of power counter in * micro-watts. * @get_power_uw: Get current power counter in micro-watts. * @set_enable: Enable/Disable power zone controls. * Default is enabled. * @get_enable: get Enable/Disable status. * @release: Callback to inform that last reference to this * control type is closed. So it is safe to free * data structure associated with this * control type. Mandatory, if client driver owns * the power_zone memory. * * This structure defines zone callbacks to be implemented by client drivers. * Client drives can define both energy and power related callbacks. But at * the least one type (either power or energy) is mandatory. Client drivers * should handle mutual exclusion, if required in callbacks. */ struct powercap_zone_ops { int (*get_max_energy_range_uj) (struct powercap_zone *, u64 *); int (*get_energy_uj) (struct powercap_zone *, u64 *); int (*reset_energy_uj) (struct powercap_zone *); int (*get_max_power_range_uw) (struct powercap_zone *, u64 *); int (*get_power_uw) (struct powercap_zone *, u64 *); int (*set_enable) (struct p