Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1230426 > unrolled thread
| Started by | Nishanth Menon <nm@ti.com> |
|---|---|
| First post | 2015-09-22 18:20 +0200 |
| Last post | 2015-10-04 02:20 +0200 |
| Articles | 7 — 2 participants |
Back to article view | Back to linux.kernel
[PATCH 0/3] ARM: dts/keystone: Introduce SoC specific compatible matches Nishanth Menon <nm@ti.com> - 2015-09-22 18:20 +0200
[PATCH 2/3] ARM: keystone: Update compatible to have SoC specific matches Nishanth Menon <nm@ti.com> - 2015-09-22 18:20 +0200
[PATCH V2 2/3] ARM: keystone: Update compatible to have SoC specific matches Nishanth Menon <nm@ti.com> - 2015-10-04 01:40 +0200
[PATCH V2 0/3] ARM: dts/keystone: Introduce SoC specific compatible matches Nishanth Menon <nm@ti.com> - 2015-10-04 01:50 +0200
[PATCH V2 1/3] Documentation: dt: keystone: provide SoC specific compatible flags Nishanth Menon <nm@ti.com> - 2015-10-04 01:50 +0200
[PATCH V2 3/3] ARM: dts: keystone: Update SoC specific compatible flags Nishanth Menon <nm@ti.com> - 2015-10-04 01:50 +0200
Re: [PATCH V2 0/3] ARM: dts/keystone: Introduce SoC specific compatible matches "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com> - 2015-10-04 02:20 +0200
| From | Nishanth Menon <nm@ti.com> |
|---|---|
| Date | 2015-09-22 18:20 +0200 |
| Subject | [PATCH 0/3] ARM: dts/keystone: Introduce SoC specific compatible matches |
| Message-ID | <qbyiK-1PH-41@gated-at.bofh.it> |
Hi, Here is a series that introduces keystone SoC specific compatible flags Series based on v4.3-rc1. Test log(merge on master): http://paste.ubuntu.org.cn/3462285 (note netcp seems to freezeup after a while into boot. debug not complete on that yet - boots fine with a minimal system..) Nishanth Menon (3): Documentation: dt: keystone: provide SoC specific compatible flags ARM: keystone: Update compatible to have SoC specific matches ARM: dts: keystone: Update SoC specific compatible flags .../devicetree/bindings/arm/keystone/keystone.txt | 20 +++++++++++++++++--- arch/arm/boot/dts/k2e-evm.dts | 2 +- arch/arm/boot/dts/k2e.dtsi | 3 +++ arch/arm/boot/dts/k2hk-evm.dts | 2 +- arch/arm/boot/dts/k2hk.dtsi | 3 +++ arch/arm/boot/dts/k2l-evm.dts | 2 +- arch/arm/boot/dts/k2l.dtsi | 3 +++ arch/arm/boot/dts/keystone.dtsi | 1 + arch/arm/mach-keystone/keystone.c | 3 +++ 9 files changed, 33 insertions(+), 6 deletions(-) -- 2.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [next] | [standalone]
| From | Nishanth Menon <nm@ti.com> |
|---|---|
| Date | 2015-09-22 18:20 +0200 |
| Subject | [PATCH 2/3] ARM: keystone: Update compatible to have SoC specific matches |
| Message-ID | <qbysr-219-37@gated-at.bofh.it> |
| In reply to | #1230426 |
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>
---
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [next] | [standalone]
| From | Nishanth Menon <nm@ti.com> |
|---|---|
| Date | 2015-10-04 01:40 +0200 |
| Subject | [PATCH V2 2/3] ARM: keystone: Update compatible to have SoC specific matches |
| Message-ID | <qfEzg-8j3-1@gated-at.bofh.it> |
| In reply to | #1230426 |
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [next] | [standalone]
| From | Nishanth Menon <nm@ti.com> |
|---|---|
| Date | 2015-10-04 01:50 +0200 |
| Subject | [PATCH V2 0/3] ARM: dts/keystone: Introduce SoC specific compatible matches |
| Message-ID | <qfEzg-8j3-3@gated-at.bofh.it> |
| In reply to | #1230426 |
Hi, Round 2 of the series with updated patch #1. This series introduces SoC specific dt compatible property to allow for future SoCs to be handled and for userspace applications that can introduce features based on SoC they are functioning on. V1 of the series: http://marc.info/?l=devicetree&m=144309031109988&w=2 V2 of the series has the following changes: - updated commit message in patch #1 - picked up acked-by for patch #1 Series based on v4.3-rc1 Tested on v4.3-rc3: http://pastebin.ubuntu.com/12659000/ Nishanth Menon (3): Documentation: dt: keystone: provide SoC specific compatible flags ARM: keystone: Update compatible to have SoC specific matches ARM: dts: keystone: Update SoC specific compatible flags .../devicetree/bindings/arm/keystone/keystone.txt | 20 +++++++++++++++++--- arch/arm/boot/dts/k2e-evm.dts | 2 +- arch/arm/boot/dts/k2e.dtsi | 3 +++ arch/arm/boot/dts/k2hk-evm.dts | 2 +- arch/arm/boot/dts/k2hk.dtsi | 3 +++ arch/arm/boot/dts/k2l-evm.dts | 2 +- arch/arm/boot/dts/k2l.dtsi | 3 +++ arch/arm/boot/dts/keystone.dtsi | 1 + arch/arm/mach-keystone/keystone.c | 3 +++ 9 files changed, 33 insertions(+), 6 deletions(-) -- 2.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [next] | [standalone]
| From | Nishanth Menon <nm@ti.com> |
|---|---|
| Date | 2015-10-04 01:50 +0200 |
| Subject | [PATCH V2 1/3] Documentation: dt: keystone: provide SoC specific compatible flags |
| Message-ID | <qfEIV-8ui-7@gated-at.bofh.it> |
| In reply to | #1239015 |
Keystone2 devices are used on more platforms than just Texas
Instruments reference evaluation platforms called EVMs. Providing a
generic compatible "ti,keystone" is not sufficient to differentiate
various SoC definitions possible on various platforms for the
following reasons:
a) Userspace applications have no way of knowing which SoC they are
functioning, providing the compatible matches provide a mechanism for
them to enable SoC specific functionality. Such userspace applications
are typically automated test framework or SoC custom hardware
acceleration entitlement from a common file system.
b) Provides an accurate hardware description. This allows
SoC specific logic to be run time handled based on
of_machine_is_compatible("ti,k2hk") or as needed for the dependent
processor instead of needing to use board dependent compatibles that
are needed now.
Hence, provide compatible matches for each SoC in the Keystone family.
Acked-By: Murali Karicheri <m-karicheri2@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
---
Changes since V2:
- elaborated reasoning why this change is useful - highlighted
potential userspace usage as well.
- picked up Acked-by from Murali
V1: https://patchwork.kernel.org/patch/7240891/
.../devicetree/bindings/arm/keystone/keystone.txt | 20 +++++++++++++++++---
1 file changed, 17 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/keystone/keystone.txt b/Documentation/devicetree/bindings/arm/keystone/keystone.txt
index 59d7a46f85eb..800d2d02e27b 100644
--- a/Documentation/devicetree/bindings/arm/keystone/keystone.txt
+++ b/Documentation/devicetree/bindings/arm/keystone/keystone.txt
@@ -9,12 +9,26 @@ Required properties:
the form "ti,keystone-*". Generic devices like gic, arch_timers, ns16550
type UART should use the specified compatible for those devices.
+SoC families:
+
+- Keystone 2 generic SoC:
+ compatible = "ti,keystone"
+
+SoCs:
+
+- Keystone 2 Hawking/Kepler
+ compatible = ti,k2hk", "ti,keystone"
+- Keystone 2 Lamarr
+ compatible = ti,k2l", "ti,keystone"
+- Keystone 2 Edison
+ compatible = ti,k2e", "ti,keystone"
+
Boards:
- Keystone 2 Hawking/Kepler EVM
- compatible = "ti,k2hk-evm","ti,keystone"
+ compatible = "ti,k2hk-evm", "ti,k2hk", "ti,keystone"
- Keystone 2 Lamarr EVM
- compatible = "ti,k2l-evm","ti,keystone"
+ compatible = "ti,k2l-evm", "ti, k2l", "ti,keystone"
- Keystone 2 Edison EVM
- compatible = "ti,k2e-evm","ti,keystone"
+ compatible = "ti,k2e-evm", "ti,k2e", "ti,keystone"
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [next] | [standalone]
| From | Nishanth Menon <nm@ti.com> |
|---|---|
| Date | 2015-10-04 01:50 +0200 |
| Subject | [PATCH V2 3/3] ARM: dts: keystone: Update SoC specific compatible flags |
| Message-ID | <qfEIV-8ui-11@gated-at.bofh.it> |
| In reply to | #1239015 |
Update the compatible flags to allow specific SoC identification.
Signed-off-by: Nishanth Menon <nm@ti.com>
---
V2: No change
V1: https://patchwork.kernel.org/patch/7240911/
arch/arm/boot/dts/k2e-evm.dts | 2 +-
arch/arm/boot/dts/k2e.dtsi | 3 +++
arch/arm/boot/dts/k2hk-evm.dts | 2 +-
arch/arm/boot/dts/k2hk.dtsi | 3 +++
arch/arm/boot/dts/k2l-evm.dts | 2 +-
arch/arm/boot/dts/k2l.dtsi | 3 +++
arch/arm/boot/dts/keystone.dtsi | 1 +
7 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/k2e-evm.dts b/arch/arm/boot/dts/k2e-evm.dts
index 50c83c21d911..b7e99807f5c2 100644
--- a/arch/arm/boot/dts/k2e-evm.dts
+++ b/arch/arm/boot/dts/k2e-evm.dts
@@ -13,7 +13,7 @@
#include "k2e.dtsi"
/ {
- compatible = "ti,k2e-evm","ti,keystone";
+ compatible = "ti,k2e-evm", "ti,k2e", "ti,keystone";
model = "Texas Instruments Keystone 2 Edison EVM";
soc {
diff --git a/arch/arm/boot/dts/k2e.dtsi b/arch/arm/boot/dts/k2e.dtsi
index 675fb8e492c6..1097dada56d2 100644
--- a/arch/arm/boot/dts/k2e.dtsi
+++ b/arch/arm/boot/dts/k2e.dtsi
@@ -9,6 +9,9 @@
*/
/ {
+ compatible = "ti,k2e", "ti,keystone";
+ model = "Texas Instruments Keystone 2 Edison SoC";
+
cpus {
#address-cells = <1>;
#size-cells = <0>;
diff --git a/arch/arm/boot/dts/k2hk-evm.dts b/arch/arm/boot/dts/k2hk-evm.dts
index 660ebf58d547..8161bf53271b 100644
--- a/arch/arm/boot/dts/k2hk-evm.dts
+++ b/arch/arm/boot/dts/k2hk-evm.dts
@@ -13,7 +13,7 @@
#include "k2hk.dtsi"
/ {
- compatible = "ti,k2hk-evm","ti,keystone";
+ compatible = "ti,k2hk-evm", "ti,k2hk", "ti,keystone";
model = "Texas Instruments Keystone 2 Kepler/Hawking EVM";
soc {
diff --git a/arch/arm/boot/dts/k2hk.dtsi b/arch/arm/boot/dts/k2hk.dtsi
index d0810a5f2968..ada4c7ac96e7 100644
--- a/arch/arm/boot/dts/k2hk.dtsi
+++ b/arch/arm/boot/dts/k2hk.dtsi
@@ -9,6 +9,9 @@
*/
/ {
+ compatible = "ti,k2hk", "ti,keystone";
+ model = "Texas Instruments Keystone 2 Kepler/Hawking SoC";
+
cpus {
#address-cells = <1>;
#size-cells = <0>;
diff --git a/arch/arm/boot/dts/k2l-evm.dts b/arch/arm/boot/dts/k2l-evm.dts
index 9a69a6b55374..00861244d788 100644
--- a/arch/arm/boot/dts/k2l-evm.dts
+++ b/arch/arm/boot/dts/k2l-evm.dts
@@ -13,7 +13,7 @@
#include "k2l.dtsi"
/ {
- compatible = "ti,k2l-evm","ti,keystone";
+ compatible = "ti,k2l-evm", "ti,k2l", "ti,keystone";
model = "Texas Instruments Keystone 2 Lamarr EVM";
soc {
diff --git a/arch/arm/boot/dts/k2l.dtsi b/arch/arm/boot/dts/k2l.dtsi
index 49fd414f680c..4446da72b0ae 100644
--- a/arch/arm/boot/dts/k2l.dtsi
+++ b/arch/arm/boot/dts/k2l.dtsi
@@ -9,6 +9,9 @@
*/
/ {
+ compatible = "ti,k2l", "ti,keystone";
+ model = "Texas Instruments Keystone 2 Lamarr SoC";
+
cpus {
#address-cells = <1>;
#size-cells = <0>;
diff --git a/arch/arm/boot/dts/keystone.dtsi b/arch/arm/boot/dts/keystone.dtsi
index 72816d65f7ec..ff91f703d371 100644
--- a/arch/arm/boot/dts/keystone.dtsi
+++ b/arch/arm/boot/dts/keystone.dtsi
@@ -12,6 +12,7 @@
#include "skeleton.dtsi"
/ {
+ compatible = "ti,keystone";
model = "Texas Instruments Keystone 2 SoC";
#address-cells = <2>;
#size-cells = <2>;
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [next] | [standalone]
| From | "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com> |
|---|---|
| Date | 2015-10-04 02:20 +0200 |
| Subject | Re: [PATCH V2 0/3] ARM: dts/keystone: Introduce SoC specific compatible matches |
| Message-ID | <qfFbX-PH-15@gated-at.bofh.it> |
| In reply to | #1239015 |
On 10/3/15 4:38 PM, Nishanth Menon wrote: > Hi, > > Round 2 of the series with updated patch #1. This series introduces > SoC specific dt compatible property to allow for future SoCs to be > handled and for userspace applications that can introduce features > based on SoC they are functioning on. > > V1 of the series: http://marc.info/?l=devicetree&m=144309031109988&w=2 > V2 of the series has the following changes: > - updated commit message in patch #1 > - picked up acked-by for patch #1 > > Series based on v4.3-rc1 > Queued up for 4.4. Thanks !! Regards, Santosh -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web