From: troy.kisky@boundarydevices.com (Troy Kisky)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 7/7] ARM: dts: imx6q-arm2: use GPIO_6 for FEC interrupt.
Date: Fri, 20 Dec 2013 11:47:13 -0700 [thread overview]
Message-ID: <1387565233-16144-8-git-send-email-troy.kisky@boundarydevices.com> (raw)
In-Reply-To: <1387565233-16144-1-git-send-email-troy.kisky@boundarydevices.com>
This works around a hardware bug.
Signed-off-by: Troy Kisky <troy.kisky@boundarydevices.com>
---
This has not been tested
---
arch/arm/boot/dts/imx6q-arm2.dts | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/imx6q-arm2.dts b/arch/arm/boot/dts/imx6q-arm2.dts
index 9c00b73..631a426 100644
--- a/arch/arm/boot/dts/imx6q-arm2.dts
+++ b/arch/arm/boot/dts/imx6q-arm2.dts
@@ -75,7 +75,7 @@
};
pinctrl_enet: enetgrp {
- fsl,pins = <MX6QDL_ENET_PINGRP2>;
+ fsl,pins = <MX6QDL_ENET_PINGRP2_GPIO6>;
};
pinctrl_gpmi_nand: gpminandgrp {
@@ -115,6 +115,8 @@
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_enet>;
phy-mode = "rgmii";
+ interrupts-extended = <&gpio1 6 IRQ_TYPE_LEVEL_HIGH>,
+ <&intc 0 119 IRQ_TYPE_LEVEL_HIGH>;
status = "okay";
};
--
1.8.1.2
prev parent reply other threads:[~2013-12-20 18:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 18:47 [PATCH V2 0/7] Fix imx6 fec interrupts Troy Kisky
2013-12-20 18:47 ` [PATCH V2 1/7] ARM: dts: imx: pinfunc: add MX6QDL_PAD_GPIO_6__ENET_IRQ Troy Kisky
2013-12-20 18:47 ` [PATCH V2 2/7] ARM: dts: imx6qdl: add pingroups for enet with GPIO6 interrupt Troy Kisky
2013-12-20 18:47 ` [PATCH V2 3/7] ARM: dts: imx6qdl-sabrelite: use MX6QDL_ENET_PINGRP_RGMII_MD Troy Kisky
2013-12-20 18:47 ` [PATCH V2 4/7] ARM: dts: imx6qdl: use interrupts-extended for fec Troy Kisky
2013-12-20 18:47 ` [PATCH V2 5/7] ARM: dts: imx6qdl-sabrelite: use GPIO_6 for FEC interrupt Troy Kisky
2013-12-20 19:02 ` Troy Kisky
2013-12-23 7:28 ` Shawn Guo
2013-12-20 18:47 ` [PATCH V2 6/7] ARM: dts: imx6qdl-sabreauto: " Troy Kisky
2013-12-20 18:47 ` Troy Kisky [this message]
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=1387565233-16144-8-git-send-email-troy.kisky@boundarydevices.com \
--to=troy.kisky@boundarydevices.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).