From: karthik@techveda.org
To: bcousson@baylibre.com, tony@atomide.com, robh+dt@kernel.org,
mark.rutland@arm.com, linux@armlinux.org.uk
Cc: linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, sunil.m@techveda.org,
Karthik Tummala <karthik@techveda.org>
Subject: [PATCH] arm: dts: omap3: Remove interrupt-parent property
Date: Tue, 27 Jun 2017 11:03:10 +0530 [thread overview]
Message-ID: <1498541590-4550-1-git-send-email-karthik@techveda.org> (raw)
From: Karthik Tummala <karthik@techveda.org>
All nodes inhert "interrupt-parent" property from root
node. So removed that property from usbhsohci, usbhsehci,
ssi_port1, ssi_port2 nodes.
Signed-off-by: Karthik Tummala <karthik@techveda.org>
---
arch/arm/boot/dts/omap3.dtsi | 4 ----
1 file changed, 4 deletions(-)
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
index a3ff493..bdaf30c 100644
--- a/arch/arm/boot/dts/omap3.dtsi
+++ b/arch/arm/boot/dts/omap3.dtsi
@@ -713,14 +713,12 @@
usbhsohci: ohci@48064400 {
compatible = "ti,ohci-omap3";
reg = <0x48064400 0x400>;
- interrupt-parent = <&intc>;
interrupts = <76>;
};
usbhsehci: ehci@48064800 {
compatible = "ti,ehci-omap";
reg = <0x48064800 0x400>;
- interrupt-parent = <&intc>;
interrupts = <77>;
};
};
@@ -831,7 +829,6 @@
reg-names = "tx",
"rx";
- interrupt-parent = <&intc>;
interrupts = <67>,
<68>;
};
@@ -844,7 +841,6 @@
reg-names = "tx",
"rx";
- interrupt-parent = <&intc>;
interrupts = <69>,
<70>;
};
--
1.9.1
next reply other threads:[~2017-06-27 5:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 5:33 karthik [this message]
[not found] ` <1498541590-4550-1-git-send-email-karthik-fINqtvHxh+hg9hUCZPvPmw@public.gmane.org>
2017-06-27 5:46 ` [PATCH] arm: dts: omap3: Remove interrupt-parent property Suniel Mahesh
2017-06-27 6:47 ` [PATCH v2] arm: dts: omap3: Remove needless " karthik
2017-08-10 16:38 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1498541590-4550-1-git-send-email-karthik@techveda.org \
--to=karthik@techveda.org \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sunil.m@techveda.org \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).