Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 3a4358cd authored by Pankaj Gupta's avatar Pankaj Gupta
Browse files

dt-bindings: Add victims_table bindings for cx_ipeak driver 

Victim table support for client to register and throttle freq
based on the cx-ipeak interrupt notifier callbacks to clients.

Change-Id: I9717056e638ed70f5bf848f99f07a0b2c6919938
parent a3114cca

bindings/soc/qcom/qcom,cx_ipeak.txt

+15 −0
Original line number Diff line number Diff line
@@ -5,6 +5,8 @@ blocks on Cx power rail. Each client needs to set their bit in tcsr register 
if it is going to cross its own threshold. If all clients are going to cross

their thresholds then Cx ipeak hw module will raise an interrupt to cDSP block

to throttle cDSP's fmax.

There are SOC like SCUBA in which Cx ipeak HW module raise interrupt to throttle

frequency of other victim clients.



Required properties:
@@ -14,9 +16,22 @@ Required properties: 
- reg : physical base address and length of the register set(s), SRAM and XPU

	of the component.



Optional properties:

- interrupts : Danger and Safe interrupts details having interrupt number and

	type of interrupt.



- interrupt-names : Identifier names for Danger and Safe interrupts.



- victims_table : Victim clients details having client ID, victim ID and limit

	frequency to be applied in case of danger interrupt.



Example:



	cx_ipeak_lm: cx_ipeak@1fe5040 {

		compatible = "qcom,cx-ipeak-v1";

		reg = <0x01fe5040 0x28>;

	interrupts = <0 415 IRQ_TYPE_EDGE_RISING>,

		     <0 416 IRQ_TYPE_EDGE_RISING>;

		interrupt-names = "cx_ipeak_danger", "cx_ipeak_safe";

		victims_table = <1 0 844800000>;

	};