Thread (24 messages) 24 messages, 4 authors, 2015-10-04
STALE3904d
Revisions (2)
  1. v1 [diff vs current]
  2. v2 current

[PATCH V2 2/3] ARM: keystone: Update compatible to have SoC specific matches

From: nm@ti.com (Nishanth Menon)
Date: 2015-10-03 23:39:48
Also in: linux-devicetree, lkml
Subsystem: arm port, arm/texas instrument keystone architecture, the rest · Maintainers: Russell King, Nishanth Menon, Santosh Shilimkar, Linus Torvalds

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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help