This patch adds posibility to choose what type of data should be counted by the PPMU counter. Now the type comes from DT where the event has been defined. When there is no 'event-data-type' the default value is used, which is 'read+write data in bytes'. It is needed when you want to know not only read+write data bytes but i.e. only write data in byte, or number of read requests, etc.
Showing the changes to include/linux (1 of 2 files). Show all
Unified · Split
| @@ -78,14 +78,20 @@ struct devfreq_event_ops { · 77 unmodified lines | ||
| 78 | 78 | * struct devfreq_event_desc - the descriptor of devfreq-event device |
| 79 | 79 | * |
| 80 | 80 | * @name : the name of devfreq-event device. |
| 81 | + * @event_type : the type of the event determined and used by driver | |
| 81 | 82 | * @driver_data : the private data for devfreq-event driver. |
| 82 | 83 | * @ops : the operation to control devfreq-event device. |
| 83 | 84 | * |
| 84 | 85 | * Each devfreq-event device is described with a this structure. |
| 85 | 86 | * This structure contains the various data for devfreq-event device. |
| 87 | + * The event_type describes what is going to be counted in the register. | |
| 88 | + * It might choose to count e.g. read requests, write data in bytes, etc. | |
| 89 | + * The full supported list of types is present in specyfic header in: | |
| 90 | + * include/dt-bindings/pmu/. | |
| 86 | 91 | */ |
| 87 | 92 | struct devfreq_event_desc { |
| 88 | 93 | const char *name; |
| 94 | + u32 event_type; | |
| 89 | 95 | void *driver_data; |
| 90 | 96 | |
| 91 | 97 | const struct devfreq_event_ops *ops; |