修改led为gpio

hc

2024-10-12 a5969cabbb4660eab42b6ef0412cbbd1200cf14d

 kernel/Documentation/devicetree/bindings/devfreq/event/exynos-ppmu.txt
..
..
@@ -10,13 +10,22 @@
10
10
 to various devfreq devices. The devfreq devices would use the event data when
11
11
 derterming the current state of each IP.
12
12
 
13
-Required properties:
13
+Required properties for PPMU device:
14
14
 - compatible: Should be "samsung,exynos-ppmu" or "samsung,exynos-ppmu-v2.
15
15
 - reg: physical base address of each PPMU and length of memory mapped region.
16
16
 
17
-Optional properties:
17
+Optional properties for PPMU device:
18
18
 - clock-names : the name of clock used by the PPMU, "ppmu"
19
19
 - clocks : phandles for clock specified in "clock-names" property
20
+
21
+Required properties for 'events' child node of PPMU device:
22
+- event-name : the unique event name among PPMU device
23
+Optional properties for 'events' child node of PPMU device:
24
+- event-data-type : Define the type of data which shell be counted
25
+by the counter. You can check include/dt-bindings/pmu/exynos_ppmu.h for
26
+all possible type, i.e. count read requests, count write data in bytes,
27
+etc. This field is optional and when it is missing, the driver code
28
+will use default data type.
20
29
 
21
30
 Example1 : PPMUv1 nodes in exynos3250.dtsi are listed below.
22
31
 
..
..
@@ -145,3 +154,16 @@
145
154
 			reg = <0x104d0000 0x2000>;
146
155
 			status = "disabled";
147
156
 		};
157
+
158
+Example4 : 'event-data-type' in exynos4412-ppmu-common.dtsi are listed below.
159
+
160
+	&ppmu_dmc0 {
161
+		status = "okay";
162
+		events {
163
+			ppmu_dmc0_3: ppmu-event3-dmc0 {
164
+			event-name = "ppmu-event3-dmc0";
165
+			event-data-type = <(PPMU_RO_DATA_CNT |
166
+					PPMU_WO_DATA_CNT)>;
167
+			};
168
+		};
169
+	};