ARM: keystone: Update compatible to have SoC specific matches
authorNishanth Menon <nm@ti.com>
Sun, 4 Oct 2015 00:02:56 +0000 (17:02 -0700)
committerSantosh Shilimkar <ssantosh@kernel.org>
Tue, 6 Oct 2015 16:51:08 +0000 (09:51 -0700)
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>
Signed-off-by: Santosh Shilimkar <ssantosh@kernel.org>
arch/arm/mach-keystone/keystone.c

index e288010522f9a6972ecebcd2b256746c9be98738..c279293f084cb87c2e0cc4cbf4ada1e2984e83f2 100644 (file)
@@ -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,
 };