From: Liu Gang <Gang.Liu@nxp.com>
To: linus.walleij@linaro.org, linux-gpio@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, khilman@linaro.org
Cc: Liu Gang <Gang.Liu@nxp.com>,
robh+dt@kernel.org, leoyang.li@nxp.com, mingkai.hu@nxp.com,
scott.wood@nxp.com
Subject: [PATCH v2] gpio/ls1043a: Add compatible "fsl, qoriq-gpio" for ls1043a gpio nodes
Date: Wed, 23 Mar 2016 17:47:21 +0800 [thread overview]
Message-ID: <1458726442-1851-3-git-send-email-Gang.Liu@nxp.com> (raw)
In-Reply-To: <1458726442-1851-1-git-send-email-Gang.Liu@nxp.com>
The compatible "fsl,qoriq-gpio" is used by gpio driver:
drivers/gpio/gpio-mpc8xxx.c to implement general gpio
functionalities.
The chip-specific compatible "fsl,ls1043a-gpio" may be
used to fix potential gpio IP block errata or other
chip-specific gpio issues.
Signed-off-by: Liu Gang <Gang.Liu@nxp.com>
---
v2 changes:
Add chip-specific compatible based on Scott's
comment.
arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi b/arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi
index be72bf5..bf70b27 100644
--- a/arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi
+++ b/arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi
@@ -284,7 +284,7 @@
};
gpio1: gpio@2300000 {
- compatible = "fsl,ls1043a-gpio";
+ compatible = "fsl,ls1043a-gpio", "fsl,qoriq-gpio";
reg = <0x0 0x2300000 0x0 0x10000>;
interrupts = <0 66 0x4>;
gpio-controller;
@@ -294,7 +294,7 @@
};
gpio2: gpio@2310000 {
- compatible = "fsl,ls1043a-gpio";
+ compatible = "fsl,ls1043a-gpio", "fsl,qoriq-gpio";
reg = <0x0 0x2310000 0x0 0x10000>;
interrupts = <0 67 0x4>;
gpio-controller;
@@ -304,7 +304,7 @@
};
gpio3: gpio@2320000 {
- compatible = "fsl,ls1043a-gpio";
+ compatible = "fsl,ls1043a-gpio", "fsl,qoriq-gpio";
reg = <0x0 0x2320000 0x0 0x10000>;
interrupts = <0 68 0x4>;
gpio-controller;
@@ -314,7 +314,7 @@
};
gpio4: gpio@2330000 {
- compatible = "fsl,ls1043a-gpio";
+ compatible = "fsl,ls1043a-gpio", "fsl,qoriq-gpio";
reg = <0x0 0x2330000 0x0 0x10000>;
interrupts = <0 134 0x4>;
gpio-controller;
--
2.1.0.27.g96db324
next prev parent reply other threads:[~2016-03-23 9:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 9:47 [PATCH] dt-bindings: Add new platforms GPIO node description Liu Gang
2016-03-23 9:47 ` [PATCH v2] gpio/ls1021a: Add gpio support for ls1021a platform Liu Gang
2016-03-31 8:32 ` Linus Walleij
2016-04-13 4:48 ` Shawn Guo
2016-03-23 9:47 ` Liu Gang [this message]
2016-03-31 3:36 ` [PATCH v2] gpio/ls1043a: Add compatible "fsl,qoriq-gpio" for ls1043a gpio nodes Gang Liu
2016-04-01 12:53 ` Linus Walleij
2016-04-13 5:03 ` [PATCH v2] gpio/ls1043a: Add compatible "fsl, qoriq-gpio" " Shawn Guo
2016-03-23 9:47 ` [PATCH] gpio/ls2080a: Add compatible "fsl, ls2080a-gpio" for ls2080a " Liu Gang
2016-03-31 8:29 ` [PATCH] gpio/ls2080a: Add compatible "fsl,ls2080a-gpio" " Linus Walleij
2016-03-31 19:40 ` Li Yang
2016-04-13 5:04 ` [PATCH] gpio/ls2080a: Add compatible "fsl, ls2080a-gpio" " Shawn Guo
2016-03-31 8:30 ` [PATCH] dt-bindings: Add new platforms GPIO node description Linus Walleij
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=1458726442-1851-3-git-send-email-Gang.Liu@nxp.com \
--to=gang.liu@nxp.com \
--cc=khilman@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mingkai.hu@nxp.com \
--cc=robh+dt@kernel.org \
--cc=scott.wood@nxp.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).