From: Nishanth Menon <nm@ti.com>
To: Santosh Shilimkar <ssantosh@kernel.org>
Cc: Murali Karicheri <m-karicheri2@ti.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Nishanth Menon <nm@ti.com>
Subject: [PATCH V2 2/3] ARM: keystone: Update compatible to have SoC specific matches
Date: Sat, 3 Oct 2015 18:38:49 -0500 [thread overview]
Message-ID: <1443915530-15035-3-git-send-email-nm@ti.com> (raw)
In-Reply-To: <1443915530-15035-1-git-send-email-nm@ti.com>
With future SoCs of keystone2 family, the generic compatible match
may not be sufficient to handle SoC specific handling. So introduce
matches based on SoC compatiblity.
Signed-off-by: Nishanth Menon <nm@ti.com>
---
Changes in V2:
- reformatting of commit message. no functional change
V1: https://patchwork.kernel.org/patch/7240901/
arch/arm/mach-keystone/keystone.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/mach-keystone/keystone.c b/arch/arm/mach-keystone/keystone.c
index e288010522f9..c279293f084c 100644
--- a/arch/arm/mach-keystone/keystone.c
+++ b/arch/arm/mach-keystone/keystone.c
@@ -97,6 +97,9 @@ static long long __init keystone_pv_fixup(void)
}
static const char *const keystone_match[] __initconst = {
+ "ti,k2hk",
+ "ti,k2e",
+ "ti,k2l",
"ti,keystone",
NULL,
};
--
2.1.4
next prev parent reply other threads:[~2015-10-03 23:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 16:08 [PATCH 0/3] ARM: dts/keystone: Introduce SoC specific compatible matches Nishanth Menon
2015-09-22 16:08 ` [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags Nishanth Menon
2015-09-23 18:05 ` Murali Karicheri
2015-09-23 19:15 ` Nishanth Menon
2015-09-23 18:19 ` santosh shilimkar
2015-09-24 14:05 ` Murali Karicheri
2015-09-24 14:20 ` Nishanth Menon
2015-09-24 15:54 ` Murali Karicheri
2015-09-25 14:50 ` Nishanth Menon
2015-09-25 15:18 ` santosh shilimkar
2015-09-25 16:01 ` Nishanth Menon
2015-09-25 16:15 ` santosh shilimkar
2015-09-25 17:38 ` Nishanth Menon
2015-10-02 16:09 ` santosh shilimkar
2015-10-03 23:44 ` Nishanth Menon
2015-10-04 0:16 ` santosh.shilimkar
2015-09-30 14:31 ` Murali Karicheri
2015-09-22 16:08 ` [PATCH 2/3] ARM: keystone: Update compatible to have SoC specific matches Nishanth Menon
2015-09-22 16:08 ` [PATCH 3/3] ARM: dts: keystone: Update SoC specific compatible flags Nishanth Menon
2015-10-03 23:38 ` [PATCH V2 0/3] ARM: dts/keystone: Introduce SoC specific compatible matches Nishanth Menon
2015-10-03 23:38 ` [PATCH V2 1/3] Documentation: dt: keystone: provide SoC specific compatible flags Nishanth Menon
2015-10-03 23:38 ` Nishanth Menon [this message]
2015-10-03 23:38 ` [PATCH V2 3/3] ARM: dts: keystone: Update " Nishanth Menon
2015-10-04 0:13 ` [PATCH V2 0/3] ARM: dts/keystone: Introduce SoC specific compatible matches santosh.shilimkar
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=1443915530-15035-3-git-send-email-nm@ti.com \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=ssantosh@kernel.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
Powered by JetHome