Commit 6909c70c authored by Bjorn Helgaas's avatar Bjorn Helgaas Committed by Luis Henriques

of/irq: Drop obsolete 'interrupts' vs 'interrupts-extended' text

commit 66865de4 upstream.

a9ecdc0f ("of/irq: Fix lookup to use 'interrupts-extended' property
first") updated the description to say that:

  - Both 'interrupts' and 'interrupts-extended' may be present
  - Software should prefer 'interrupts-extended'
  - Software that doesn't comprehend 'interrupts-extended' may use
    'interrupts'

But there is still a paragraph at the end that prohibits having both and
says 'interrupts' should be preferred.

Remove the contradictory text.

Fixes: a9ecdc0f ("of/irq: Fix lookup to use 'interrupts-extended' property first")
Signed-off-by: default avatarBjorn Helgaas <bhelgaas@google.com>
Acked-by: default avatarBrian Norris <computersforpeace@gmail.com>
Acked-by: default avatarMark Rutland <mark.rutland@arm.com>
Signed-off-by: default avatarRob Herring <robh@kernel.org>
Signed-off-by: default avatarLuis Henriques <luis.henriques@canonical.com>
parent 411bd23e
...@@ -30,10 +30,6 @@ should only be used when a device has multiple interrupt parents. ...@@ -30,10 +30,6 @@ should only be used when a device has multiple interrupt parents.
Example: Example:
interrupts-extended = <&intc1 5 1>, <&intc2 1 0>; interrupts-extended = <&intc1 5 1>, <&intc2 1 0>;
A device node may contain either "interrupts" or "interrupts-extended", but not
both. If both properties are present, then the operating system should log an
error and use only the data in "interrupts".
2) Interrupt controller nodes 2) Interrupt controller nodes
----------------------------- -----------------------------
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment