Skip to contentSkip to conversation

mfd: palmas: support IRQ inversion at the board level

PATCH Superseded Stephen Warren 3 participants 8 messages Feb 14, 2014 – Feb 25, 2014

Subsystems (4)

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore
#0 lore raw

PATCH 1/2 mfd: palmas: support IRQ inversion at the board level

From: Stephen Warren <[email protected]>

Some boards or SoCs have an inverter between the PMIC IRQ output pin and the IRQ controller input signal.

The IRQ specifier in DT is meant to represent the IRQ flags at the input to the IRQ controller.

The Palmas HW's IRQ output has configurable polarity. The driver currently selects the output polarity by querying the input polarity at the IRQ controller. This works fine if the IRQ signal is routed directly from the PMIC to the IRQ controller with no intervening logic. However, if the signal is inverted between the two, this automatic polarity selection gets the wrong answer.

Add an additional optional DT and platform data parameter which indicates that such an inversion occurs. If this option is enabled, the Palmas driver will configure its IRQ output to the opposite polarity of the IRQ controller's input.

An alternative would have been to add a new non-optional DT parameter to indicate the exact desired output polarity. However, this would have been an incompatible change to the DT binding.

---
If this patch could be applied to its own branch (w/ signed tag) in the MFD tree, that would great; then I can pull patch 1/2 into the Tegra tree so that I can apply patch 2/2 to the Tegra tree. Thanks.

---
 Documentation/devicetree/bindings/mfd/palmas.txt | 6 ++++++
 drivers/mfd/palmas.c                             | 4 ++++
 include/linux/mfd/palmas.h                       | 1 +
 3 files changed, 11 insertions(+)
Documentation/devicetree/bindings/mfd/palmas.txt +6 -0
index e5f0f8303461..76ec509d5f87 100644
@@ -18,6 +18,12 @@ Required properties:
   ti,tps659038
 and also the generic series names
   ti,palmas
+- interrupts : Should contain a single entry for the IRQ output.
+- ti,irq-externally-inverted : If missing, the polarity of the Palmas IRQ
+  output should be set to the opposite of the polarity indicated by the IRQ
+  specifier in the interrupts property. If absent, the polarity should be
+  configured to match. This allows the representation of an inverter between
+  the Palmas IRQ output and the interrupt parent's IRQ input.
 - interrupt-controller : palmas has its own internal IRQs
 - #interrupt-cells : should be set to 2 for IRQ number and flags
   The first cell is the IRQ number.
drivers/mfd/palmas.c +4 -0
index d280d789e55a..f4ea932adf8d 100644
@@ -293,6 +293,8 @@ static int palmas_set_pdata_irq_flag(struct i2c_client *i2c,
 	}
 
 	pdata->irq_flags = irqd_get_trigger_type(irq_data);
+	pdata->irq_external_inversion = of_property_read_bool(i2c->dev.of_node,
+						"ti,irq-externally-inverted");
 	dev_info(&i2c->dev, "Irq flag is 0x%08x\n", pdata->irq_flags);
 	return 0;
 }
@@ -447,6 +449,8 @@ static int palmas_i2c_probe(struct i2c_client *i2c,
 		reg = PALMAS_POLARITY_CTRL_INT_POLARITY;
 	else
 		reg = 0;
+	if (pdata->irq_external_inversion)
+		reg ^= PALMAS_POLARITY_CTRL_INT_POLARITY;
 	ret = palmas_update_bits(palmas, PALMAS_PU_PD_OD_BASE,
 			PALMAS_POLARITY_CTRL, PALMAS_POLARITY_CTRL_INT_POLARITY,
 			reg);
include/linux/mfd/palmas.h +1 -0
index 9974e387e483..2fdf08c50a48 100644
@@ -292,6 +292,7 @@ struct palmas_clk_platform_data {
 
 struct palmas_platform_data {
 	int irq_flags;
+	bool irq_external_inversion;
 	int gpio_base;
 
 	/* bit value to be loaded to the POWER_CTRL register */
Signature · 1 line
1.8.1.5
#1 lore raw

PATCH 2/2 ARM: tegra: fix Dalmore PMIC IRQ polarity

From: Stephen Warren <[email protected]>

The Tegra PMC's resume-from-sleep logic wants an active-low IRQ input from the PMIC. However, the PMIC IRQ is also routed to the GIC, which only supports active high IRQs (or rising edge). Hence, the signal must be inverted in the PMC before being routed to the GIC. This implies that the PMC DT property nvidia,invert-interrupt must be set, and it is.

The PMIC's DT interrupts property must represent the IRQ level at the GIC, since that is the PMIC's parent IRQ controller. Fix the PMIC's interrupts property to correctly describe the GIC input polarity.

However, the PMIC IRQ output's polarity is programmable in HW, and by default follows the parent IRQ controller's input polarity. We need to have an active-low output due to the inversion inside the Tegra PMC. Hence, add the ti,irq-externally-inverted property to the PMIC.

---
 arch/arm/boot/dts/tegra114-dalmore.dts | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
arch/arm/boot/dts/tegra114-dalmore.dts +2 -1
index 8de543777882..2977206cafc9 100644
@@ -893,7 +893,8 @@
 		palmas: tps65913 at 58 {
 			compatible = "ti,palmas";
 			reg = <0x58>;
-			interrupts = <0 86 IRQ_TYPE_LEVEL_LOW>;
+			interrupts = <0 86 IRQ_TYPE_LEVEL_HIGH>;
+			ti,irq-externally-inverted;
 
 			#interrupt-cells = <2>;
 			interrupt-controller;
Signature · 1 line
1.8.1.5
#2 lore raw

PATCH 2/2 ARM: tegra: fix Dalmore PMIC IRQ polarity

Quoted 8 lines · Stephen Warren

From: Stephen Warren <[email protected]>

The Tegra PMC's resume-from-sleep logic wants an active-low IRQ input from the PMIC. However, the PMIC IRQ is also routed to the GIC, which only supports active high IRQs (or rising edge). Hence, the signal must be inverted in the PMC before being routed to the GIC. This implies that the PMC DT property nvidia,invert-interrupt must be set, and it is.

Quoted 9 lines

The PMIC's DT interrupts property must represent the IRQ level at the GIC, since that is the PMIC's parent IRQ controller. Fix the PMIC's interrupts property to correctly describe the GIC input polarity.

However, the PMIC IRQ output's polarity is programmable in HW, and by default follows the parent IRQ controller's input polarity. We need to have an active-low output due to the inversion inside the Tegra PMC. Hence, add the ti,irq-externally-inverted property to the PMIC.

Looks good to me.

#4 lore raw

PATCH 1/2 mfd: palmas: support IRQ inversion at the board level

In reply to Stephen Warren
Quoted 29 lines

From: Stephen Warren <[email protected]>

Some boards or SoCs have an inverter between the PMIC IRQ output pin and the IRQ controller input signal.

The IRQ specifier in DT is meant to represent the IRQ flags at the input to the IRQ controller.

The Palmas HW's IRQ output has configurable polarity. The driver currently selects the output polarity by querying the input polarity at the IRQ controller. This works fine if the IRQ signal is routed directly from the PMIC to the IRQ controller with no intervening logic. However, if the signal is inverted between the two, this automatic polarity selection gets the wrong answer.

Add an additional optional DT and platform data parameter which indicates that such an inversion occurs. If this option is enabled, the Palmas driver will configure its IRQ output to the opposite polarity of the IRQ controller's input.

An alternative would have been to add a new non-optional DT parameter to indicate the exact desired output polarity. However, this would have been an incompatible change to the DT binding.

---
If this patch could be applied to its own branch (w/ signed tag) in the MFD tree, that would great; then I can pull patch 1/2 into the Tegra tree so that I can apply patch 2/2 to the Tegra tree. Thanks.

Quoted 5 lines
---
 Documentation/devicetree/bindings/mfd/palmas.txt | 6 ++++++
 drivers/mfd/palmas.c                             | 4 ++++
 include/linux/mfd/palmas.h                       | 1 +
 3 files changed, 11 insertions(+)

For the core changes:

NB: The DT guys prefer documentation to be submitted in a separate patch these days.

Signature · 4 lines
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
#5 lore raw

PATCH 1/2 mfd: palmas: support IRQ inversion at the board level

Quoted 35 lines · Lee Jones
Quoted 29 lines

From: Stephen Warren <[email protected]>

Some boards or SoCs have an inverter between the PMIC IRQ output pin and the IRQ controller input signal.

The IRQ specifier in DT is meant to represent the IRQ flags at the input to the IRQ controller.

The Palmas HW's IRQ output has configurable polarity. The driver currently selects the output polarity by querying the input polarity at the IRQ controller. This works fine if the IRQ signal is routed directly from the PMIC to the IRQ controller with no intervening logic. However, if the signal is inverted between the two, this automatic polarity selection gets the wrong answer.

Add an additional optional DT and platform data parameter which indicates that such an inversion occurs. If this option is enabled, the Palmas driver will configure its IRQ output to the opposite polarity of the IRQ controller's input.

An alternative would have been to add a new non-optional DT parameter to indicate the exact desired output polarity. However, this would have been an incompatible change to the DT binding.

---
If this patch could be applied to its own branch (w/ signed tag) in the MFD tree, that would great; then I can pull patch 1/2 into the Tegra tree so that I can apply patch 2/2 to the Tegra tree. Thanks.

Quoted 5 lines
---
 Documentation/devicetree/bindings/mfd/palmas.txt | 6 ++++++
 drivers/mfd/palmas.c                             | 4 ++++
 include/linux/mfd/palmas.h                       | 1 +
 3 files changed, 11 insertions(+)
Quoted 2 lines

For the core changes:

Thanks. Since you ack'd this and are an MFD maintainer, was that an indication that I should take this patch through the Tegra tree?

#6 lore raw

PATCH 1/2 mfd: palmas: support IRQ inversion at the board level

Quoted 35 lines
Quoted 35 lines
Quoted 34 lines

From: Stephen Warren <[email protected]>

Some boards or SoCs have an inverter between the PMIC IRQ output pin and the IRQ controller input signal.

The IRQ specifier in DT is meant to represent the IRQ flags at the input to the IRQ controller.

The Palmas HW's IRQ output has configurable polarity. The driver currently selects the output polarity by querying the input polarity at the IRQ controller. This works fine if the IRQ signal is routed directly from the PMIC to the IRQ controller with no intervening logic. However, if the signal is inverted between the two, this automatic polarity selection gets the wrong answer.

Add an additional optional DT and platform data parameter which indicates that such an inversion occurs. If this option is enabled, the Palmas driver will configure its IRQ output to the opposite polarity of the IRQ controller's input.

An alternative would have been to add a new non-optional DT parameter to indicate the exact desired output polarity. However, this would have been an incompatible change to the DT binding.

---
If this patch could be applied to its own branch (w/ signed tag) in the MFD tree, that would great; then I can pull patch 1/2 into the Tegra tree so that I can apply patch 2/2 to the Tegra tree. Thanks.

---
 Documentation/devicetree/bindings/mfd/palmas.txt | 6 ++++++
 drivers/mfd/palmas.c                             | 4 ++++
 include/linux/mfd/palmas.h                       | 1 +
 3 files changed, 11 insertions(+)
Quoted 5 lines
Quoted 2 lines

For the core changes:

Thanks. Since you ack'd this and are an MFD maintainer, was that an indication that I should take this patch through the Tegra tree?

No, it was an indication that we still require more Acks. :)

Signature · 4 lines
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
#7 lore raw

PATCH 1/2 mfd: palmas: support IRQ inversion at the board level

In reply to Stephen Warren

Mark,

Quoted 24 lines

From: Stephen Warren <[email protected]>

Some boards or SoCs have an inverter between the PMIC IRQ output pin and the IRQ controller input signal.

The IRQ specifier in DT is meant to represent the IRQ flags at the input to the IRQ controller.

The Palmas HW's IRQ output has configurable polarity. The driver currently selects the output polarity by querying the input polarity at the IRQ controller. This works fine if the IRQ signal is routed directly from the PMIC to the IRQ controller with no intervening logic. However, if the signal is inverted between the two, this automatic polarity selection gets the wrong answer.

Add an additional optional DT and platform data parameter which indicates that such an inversion occurs. If this option is enabled, the Palmas driver will configure its IRQ output to the opposite polarity of the IRQ controller's input.

An alternative would have been to add a new non-optional DT parameter to indicate the exact desired output polarity. However, this would have been an incompatible change to the DT binding.

Quoted 7 lines

---
If this patch could be applied to its own branch (w/ signed tag) in the MFD tree, that would great; then I can pull patch 1/2 into the Tegra tree so that I can apply patch 2/2 to the Tegra tree. Thanks.

---
 Documentation/devicetree/bindings/mfd/palmas.txt | 6 ++++++

Would you care to review this for Stephen please?

Quoted 55 lines
 drivers/mfd/palmas.c                             | 4 ++++
 include/linux/mfd/palmas.h                       | 1 +
 3 files changed, 11 insertions(+)
Documentation/devicetree/bindings/mfd/palmas.txt +6 -0
index e5f0f8303461..76ec509d5f87 100644
@@ -18,6 +18,12 @@ Required properties:
   ti,tps659038
 and also the generic series names
   ti,palmas
+- interrupts : Should contain a single entry for the IRQ output.
+- ti,irq-externally-inverted : If missing, the polarity of the Palmas IRQ
+  output should be set to the opposite of the polarity indicated by the IRQ
+  specifier in the interrupts property. If absent, the polarity should be
+  configured to match. This allows the representation of an inverter between
+  the Palmas IRQ output and the interrupt parent's IRQ input.
 - interrupt-controller : palmas has its own internal IRQs
 - #interrupt-cells : should be set to 2 for IRQ number and flags
   The first cell is the IRQ number.
drivers/mfd/palmas.c +4 -0
index d280d789e55a..f4ea932adf8d 100644
@@ -293,6 +293,8 @@ static int palmas_set_pdata_irq_flag(struct i2c_client *i2c,
 	}
 
 	pdata->irq_flags = irqd_get_trigger_type(irq_data);
+	pdata->irq_external_inversion = of_property_read_bool(i2c->dev.of_node,
+						"ti,irq-externally-inverted");
 	dev_info(&i2c->dev, "Irq flag is 0x%08x\n", pdata->irq_flags);
 	return 0;
 }
@@ -447,6 +449,8 @@ static int palmas_i2c_probe(struct i2c_client *i2c,
 		reg = PALMAS_POLARITY_CTRL_INT_POLARITY;
 	else
 		reg = 0;
+	if (pdata->irq_external_inversion)
+		reg ^= PALMAS_POLARITY_CTRL_INT_POLARITY;
 	ret = palmas_update_bits(palmas, PALMAS_PU_PD_OD_BASE,
 			PALMAS_POLARITY_CTRL, PALMAS_POLARITY_CTRL_INT_POLARITY,
 			reg);
include/linux/mfd/palmas.h +1 -0
index 9974e387e483..2fdf08c50a48 100644
@@ -292,6 +292,7 @@ struct palmas_clk_platform_data {
 
 struct palmas_platform_data {
 	int irq_flags;
+	bool irq_external_inversion;
 	int gpio_base;
 
 	/* bit value to be loaded to the POWER_CTRL register */
Signature · 4 lines
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog