Re: [PATCH 1/3] clk: exynos5420: Add 5800 specific clocks
Hi Tomasz,
Thanks for the review.
On Fri, May 2, 2014 at 10:53 PM, Tomasz Figa tomasz.f...@gmail.com wrote:
Hi Arun, Alim,
On 02.05.2014 15:03, Arun Kumar K wrote:
From: Alim Akhtar alim.akh...@samsung.com
Exynos5800 clock structure is mostly similar to 5420 with only
a small delta changes. So the 5420 clock file is re-used for
5800 also. The common clocks for both are seggreagated and few
clocks which are different for both are separately initialized.
Let's start with a general comment to this patch first. Have you consulted
this with Shaik and Rahul (on CC) who are currently doing a quite heavy
lifting of this driver to make sure that your work don't cause conflicts?
Yes I am aware of that series and I can post another version
which is based on that series if that is almost ready to be taken.
Also please see some more specific comments inline.
Signed-off-by: Alim Akhtar alim.akh...@samsung.com
Signed-off-by: Arun Kumar K arun...@samsung.com
---
.../devicetree/bindings/clock/exynos5420-clock.txt |3 +-
drivers/clk/samsung/clk-exynos5420.c | 192
+++-
include/dt-bindings/clock/exynos5420.h |1 +
3 files changed, 150 insertions(+), 46 deletions(-)
diff --git a/Documentation/devicetree/bindings/clock/exynos5420-clock.txt
b/Documentation/devicetree/bindings/clock/exynos5420-clock.txt
index ca88c97..d54f42c 100644
--- a/Documentation/devicetree/bindings/clock/exynos5420-clock.txt
+++ b/Documentation/devicetree/bindings/clock/exynos5420-clock.txt
@@ -1,12 +1,13 @@
* Samsung Exynos5420 Clock Controller
The Exynos5420 clock controller generates and supplies clock to various
-controllers within the Exynos5420 SoC.
+controllers within the Exynos5420 SoC and for the Exynos5800 SoC.
Required Properties:
- compatible: should be one of the following.
- samsung,exynos5420-clock - controller compatible with Exynos5420
SoC.
+ - samsung,exynos5800-clock - controller compatible with Exynos5800
SoC.
- reg: physical base address of the controller and length of memory
mapped
region.
diff --git a/drivers/clk/samsung/clk-exynos5420.c
b/drivers/clk/samsung/clk-exynos5420.c
index 60b2681..0543cb7 100644
--- a/drivers/clk/samsung/clk-exynos5420.c
+++ b/drivers/clk/samsung/clk-exynos5420.c
@@ -51,6 +51,7 @@
#define SRC_TOP5 0x10214
#define SRC_TOP6 0x10218
#define SRC_TOP7 0x1021c
+#define SRC_TOP9 0x10224 /* 5800 specific */
#define SRC_DISP100x1022c
#define SRC_MAU 0x10240
#define SRC_FSYS 0x10244
@@ -59,6 +60,7 @@
#define SRC_TOP10 0x10280
#define SRC_TOP11 0x10284
#define SRC_TOP12 0x10288
+#define SRC_TOP13 0x1028c /* 5800 specific */
#define SRC_MASK_DISP10 0x1032c
#define SRC_MASK_FSYS 0x10340
#define SRC_MASK_PERIC0 0x10350
@@ -66,6 +68,7 @@
#define DIV_TOP0 0x10500
#define DIV_TOP1 0x10504
#define DIV_TOP2 0x10508
+#define DIV_TOP9 0x10524 /* 5800 specific */
#define DIV_DISP100x1052c
#define DIV_MAU 0x10544
#define DIV_FSYS0 0x10548
@@ -102,8 +105,14 @@
#define SRC_KFC 0x28200
#define DIV_KFC0 0x28500
+/* Exynos5x SoC type */
+enum exynos5x_soc {
+ EXYNOS5420,
+ EXYNOS5800,
+};
+
/* list of PLLs */
-enum exynos5420_plls {
+enum exynos5x_plls {
apll, cpll, dpll, epll, rpll, ipll, spll, vpll, mpll,
bpll, kpll,
nr_plls /* number of PLLs */
@@ -112,13 +121,13 @@ enum exynos5420_plls {
static void __iomem *reg_base;
#ifdef CONFIG_PM_SLEEP
-static struct samsung_clk_reg_dump *exynos5420_save;
+static struct samsung_clk_reg_dump *exynos5x_save;
/*
* list of controller registers to be saved and restored during a
* suspend/resume cycle.
*/
-static unsigned long exynos5420_clk_regs[] __initdata = {
+static unsigned long exynos5x_clk_regs[] __initdata = {
SRC_CPU,
DIV_CPU0,
DIV_CPU1,
@@ -182,16 +191,16 @@ static unsigned long exynos5420_clk_regs[]
__initdata = {
static int exynos5420_clk_suspend(void)
{
- samsung_clk_save(reg_base, exynos5420_save,
- ARRAY_SIZE(exynos5420_clk_regs));
+ samsung_clk_save(reg_base, exynos5x_save,
+ ARRAY_SIZE(exynos5x_clk_regs));
Don't you need to handle save and restore of 5800-specific registers as
well? You can see Exynos4 clock driver for an example of handling such
setup.
Ok will make the change.
return 0;
}
static void exynos5420_clk_resume(void)
{
- samsung_clk_restore(reg_base, exynos5420_save,
-
Re: [PATCH 1/3] clk: exynos5420: Add 5800 specific clocks
Hi Andrew,
On Fri, May 2, 2014 at 11:21 PM, Andrew Bresticker abres...@google.com wrote:
Hi Arun,
On Fri, May 2, 2014 at 6:03 AM, Arun Kumar K arun...@samsung.com wrote:
From: Alim Akhtar alim.akh...@samsung.com
Exynos5800 clock structure is mostly similar to 5420 with only
a small delta changes. So the 5420 clock file is re-used for
5800 also. The common clocks for both are seggreagated and few
clocks which are different for both are separately initialized.
As Tomasz mentioned, this will certainly conflict with Shaik and
Rahul's 5420 clock cleanup series. That series adds/fixes the MAU,
WCORE, and ISP blocks which also have differences from 5420 to 5800.
Yes I will rebase on that series. I dropped many of the changes
in 5800 as it doesnt have the common terminating GATES as of now.
If rebased on Shaik/Rahul cleanup series, I can put all of them
back again.
Signed-off-by: Alim Akhtar alim.akh...@samsung.com
Signed-off-by: Arun Kumar K arun...@samsung.com
---
.../devicetree/bindings/clock/exynos5420-clock.txt |3 +-
drivers/clk/samsung/clk-exynos5420.c | 192
+++-
include/dt-bindings/clock/exynos5420.h |1 +
3 files changed, 150 insertions(+), 46 deletions(-)
[snip]
+struct samsung_mux_clock exynos5800_mux_clks[] __initdata = {
+ MUX(0, mout_aclk400_mscl, mout_group3_5800_p, SRC_TOP0, 4, 3),
+
+ MUX(0, mout_aclk333_432_gscl, mout_group6_5800_p, SRC_TOP1, 0, 2),
+ MUX(0, mout_aclk266, mout_group5_5800_p, SRC_TOP1, 20, 2),
+ MUX(0, mout_aclk333, mout_group1_5800_p, SRC_TOP1, 28, 2),
+
+ MUX(0, mout_aclk333_g2d, mout_group5_5800_p, SRC_TOP2, 8, 2),
+ MUX(0, mout_aclk266_g2d, mout_group5_5800_p, SRC_TOP2, 12, 2),
+ MUX(0, mout_aclk300_jpeg, mout_group5_5800_p, SRC_TOP2, 20, 2),
+ MUX(0, mout_aclk300_disp1, mout_group5_5800_p, SRC_TOP2, 24, 2),
+ MUX(0, mout_aclk300_gscl, mout_group5_5800_p, SRC_TOP2, 28, 2),
+
+ MUX(0, sclk_bpll, bpll_p, SRC_TOP7, 24, 1),
+ MUX(0, mout_epll2, mout_epll2_5800_p, SRC_TOP7, 28, 1),
+
+ MUX(0, mout_user_aclk432_scaler, mout_group9_5800_p,
+ SRC_TOP9, 28, 1),
+ MUX(0, mout_sw_aclk432_scaler, mout_group8_5800_p,
+ SRC_TOP13, 28, 1),
The aclk432_scaler tree is incomplete - you're missing
mout_aclk432_scaler and dout_aclk432_scaler. The rest of the CAM
block (aclk432_cam, aclkfl1_550_cam, and aclk550_cam) is also missing,
though I suppose that could go in a later patch.
The CAM gates you mentioned are omitted as I found that there
are some issues caused by it during S2R sequences and I have
to leave it as CLK_IGNORE_UNUSED for proper functionality.
[snip]
Regards
Arun
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 1/3] clk: exynos5420: Add 5800 specific clocks
Hi Arun, Alim,
On 02.05.2014 15:03, Arun Kumar K wrote:
From: Alim Akhtar alim.akh...@samsung.com
Exynos5800 clock structure is mostly similar to 5420 with only
a small delta changes. So the 5420 clock file is re-used for
5800 also. The common clocks for both are seggreagated and few
clocks which are different for both are separately initialized.
Let's start with a general comment to this patch first. Have you
consulted this with Shaik and Rahul (on CC) who are currently doing a
quite heavy lifting of this driver to make sure that your work don't
cause conflicts?
Also please see some more specific comments inline.
Signed-off-by: Alim Akhtar alim.akh...@samsung.com
Signed-off-by: Arun Kumar K arun...@samsung.com
---
.../devicetree/bindings/clock/exynos5420-clock.txt |3 +-
drivers/clk/samsung/clk-exynos5420.c | 192 +++-
include/dt-bindings/clock/exynos5420.h |1 +
3 files changed, 150 insertions(+), 46 deletions(-)
diff --git a/Documentation/devicetree/bindings/clock/exynos5420-clock.txt
b/Documentation/devicetree/bindings/clock/exynos5420-clock.txt
index ca88c97..d54f42c 100644
--- a/Documentation/devicetree/bindings/clock/exynos5420-clock.txt
+++ b/Documentation/devicetree/bindings/clock/exynos5420-clock.txt
@@ -1,12 +1,13 @@
* Samsung Exynos5420 Clock Controller
The Exynos5420 clock controller generates and supplies clock to various
-controllers within the Exynos5420 SoC.
+controllers within the Exynos5420 SoC and for the Exynos5800 SoC.
Required Properties:
- compatible: should be one of the following.
- samsung,exynos5420-clock - controller compatible with Exynos5420 SoC.
+ - samsung,exynos5800-clock - controller compatible with Exynos5800 SoC.
- reg: physical base address of the controller and length of memory mapped
region.
diff --git a/drivers/clk/samsung/clk-exynos5420.c
b/drivers/clk/samsung/clk-exynos5420.c
index 60b2681..0543cb7 100644
--- a/drivers/clk/samsung/clk-exynos5420.c
+++ b/drivers/clk/samsung/clk-exynos5420.c
@@ -51,6 +51,7 @@
#define SRC_TOP5 0x10214
#define SRC_TOP6 0x10218
#define SRC_TOP7 0x1021c
+#define SRC_TOP9 0x10224 /* 5800 specific */
#define SRC_DISP100x1022c
#define SRC_MAU 0x10240
#define SRC_FSYS 0x10244
@@ -59,6 +60,7 @@
#define SRC_TOP10 0x10280
#define SRC_TOP11 0x10284
#define SRC_TOP12 0x10288
+#define SRC_TOP13 0x1028c /* 5800 specific */
#define SRC_MASK_DISP10 0x1032c
#define SRC_MASK_FSYS 0x10340
#define SRC_MASK_PERIC0 0x10350
@@ -66,6 +68,7 @@
#define DIV_TOP0 0x10500
#define DIV_TOP1 0x10504
#define DIV_TOP2 0x10508
+#define DIV_TOP9 0x10524 /* 5800 specific */
#define DIV_DISP100x1052c
#define DIV_MAU 0x10544
#define DIV_FSYS0 0x10548
@@ -102,8 +105,14 @@
#define SRC_KFC 0x28200
#define DIV_KFC0 0x28500
+/* Exynos5x SoC type */
+enum exynos5x_soc {
+ EXYNOS5420,
+ EXYNOS5800,
+};
+
/* list of PLLs */
-enum exynos5420_plls {
+enum exynos5x_plls {
apll, cpll, dpll, epll, rpll, ipll, spll, vpll, mpll,
bpll, kpll,
nr_plls /* number of PLLs */
@@ -112,13 +121,13 @@ enum exynos5420_plls {
static void __iomem *reg_base;
#ifdef CONFIG_PM_SLEEP
-static struct samsung_clk_reg_dump *exynos5420_save;
+static struct samsung_clk_reg_dump *exynos5x_save;
/*
* list of controller registers to be saved and restored during a
* suspend/resume cycle.
*/
-static unsigned long exynos5420_clk_regs[] __initdata = {
+static unsigned long exynos5x_clk_regs[] __initdata = {
SRC_CPU,
DIV_CPU0,
DIV_CPU1,
@@ -182,16 +191,16 @@ static unsigned long exynos5420_clk_regs[] __initdata = {
static int exynos5420_clk_suspend(void)
{
- samsung_clk_save(reg_base, exynos5420_save,
- ARRAY_SIZE(exynos5420_clk_regs));
+ samsung_clk_save(reg_base, exynos5x_save,
+ ARRAY_SIZE(exynos5x_clk_regs));
Don't you need to handle save and restore of 5800-specific registers as
well? You can see Exynos4 clock driver for an example of handling such
setup.
return 0;
}
static void exynos5420_clk_resume(void)
{
- samsung_clk_restore(reg_base, exynos5420_save,
- ARRAY_SIZE(exynos5420_clk_regs));
+ samsung_clk_restore(reg_base, exynos5x_save,
+ ARRAY_SIZE(exynos5x_clk_regs));
Ditto.
}
static struct syscore_ops exynos5420_clk_syscore_ops = {
@@ -201,9 +210,9 @@ static struct syscore_ops exynos5420_clk_syscore_ops = {
static void exynos5420_clk_sleep_init(void)
{
- exynos5420_save =
Re: [PATCH 1/3] clk: exynos5420: Add 5800 specific clocks
Hi Arun,
On Fri, May 2, 2014 at 6:03 AM, Arun Kumar K arun...@samsung.com wrote:
From: Alim Akhtar alim.akh...@samsung.com
Exynos5800 clock structure is mostly similar to 5420 with only
a small delta changes. So the 5420 clock file is re-used for
5800 also. The common clocks for both are seggreagated and few
clocks which are different for both are separately initialized.
As Tomasz mentioned, this will certainly conflict with Shaik and
Rahul's 5420 clock cleanup series. That series adds/fixes the MAU,
WCORE, and ISP blocks which also have differences from 5420 to 5800.
Signed-off-by: Alim Akhtar alim.akh...@samsung.com
Signed-off-by: Arun Kumar K arun...@samsung.com
---
.../devicetree/bindings/clock/exynos5420-clock.txt |3 +-
drivers/clk/samsung/clk-exynos5420.c | 192
+++-
include/dt-bindings/clock/exynos5420.h |1 +
3 files changed, 150 insertions(+), 46 deletions(-)
diff --git a/Documentation/devicetree/bindings/clock/exynos5420-clock.txt
b/Documentation/devicetree/bindings/clock/exynos5420-clock.txt
index ca88c97..d54f42c 100644
--- a/Documentation/devicetree/bindings/clock/exynos5420-clock.txt
+++ b/Documentation/devicetree/bindings/clock/exynos5420-clock.txt
@@ -1,12 +1,13 @@
* Samsung Exynos5420 Clock Controller
The Exynos5420 clock controller generates and supplies clock to various
-controllers within the Exynos5420 SoC.
+controllers within the Exynos5420 SoC and for the Exynos5800 SoC.
Required Properties:
- compatible: should be one of the following.
- samsung,exynos5420-clock - controller compatible with Exynos5420 SoC.
+ - samsung,exynos5800-clock - controller compatible with Exynos5800 SoC.
- reg: physical base address of the controller and length of memory mapped
region.
diff --git a/drivers/clk/samsung/clk-exynos5420.c
b/drivers/clk/samsung/clk-exynos5420.c
index 60b2681..0543cb7 100644
--- a/drivers/clk/samsung/clk-exynos5420.c
+++ b/drivers/clk/samsung/clk-exynos5420.c
@@ -51,6 +51,7 @@
#define SRC_TOP5 0x10214
#define SRC_TOP6 0x10218
#define SRC_TOP7 0x1021c
+#define SRC_TOP9 0x10224 /* 5800 specific */
#define SRC_DISP10 0x1022c
#define SRC_MAU0x10240
#define SRC_FSYS 0x10244
@@ -59,6 +60,7 @@
#define SRC_TOP10 0x10280
#define SRC_TOP11 0x10284
#define SRC_TOP12 0x10288
+#define SRC_TOP13 0x1028c /* 5800 specific */
#defineSRC_MASK_DISP10 0x1032c
#define SRC_MASK_FSYS 0x10340
#define SRC_MASK_PERIC00x10350
@@ -66,6 +68,7 @@
#define DIV_TOP0 0x10500
#define DIV_TOP1 0x10504
#define DIV_TOP2 0x10508
+#define DIV_TOP9 0x10524 /* 5800 specific */
#define DIV_DISP10 0x1052c
#define DIV_MAU0x10544
#define DIV_FSYS0 0x10548
@@ -102,8 +105,14 @@
#define SRC_KFC0x28200
#define DIV_KFC0 0x28500
+/* Exynos5x SoC type */
+enum exynos5x_soc {
+ EXYNOS5420,
+ EXYNOS5800,
+};
+
/* list of PLLs */
-enum exynos5420_plls {
+enum exynos5x_plls {
apll, cpll, dpll, epll, rpll, ipll, spll, vpll, mpll,
bpll, kpll,
nr_plls /* number of PLLs */
@@ -112,13 +121,13 @@ enum exynos5420_plls {
static void __iomem *reg_base;
#ifdef CONFIG_PM_SLEEP
-static struct samsung_clk_reg_dump *exynos5420_save;
+static struct samsung_clk_reg_dump *exynos5x_save;
/*
* list of controller registers to be saved and restored during a
* suspend/resume cycle.
*/
-static unsigned long exynos5420_clk_regs[] __initdata = {
+static unsigned long exynos5x_clk_regs[] __initdata = {
SRC_CPU,
DIV_CPU0,
DIV_CPU1,
@@ -182,16 +191,16 @@ static unsigned long exynos5420_clk_regs[] __initdata =
{
static int exynos5420_clk_suspend(void)
{
- samsung_clk_save(reg_base, exynos5420_save,
- ARRAY_SIZE(exynos5420_clk_regs));
+ samsung_clk_save(reg_base, exynos5x_save,
+ ARRAY_SIZE(exynos5x_clk_regs));
return 0;
}
static void exynos5420_clk_resume(void)
{
- samsung_clk_restore(reg_base, exynos5420_save,
- ARRAY_SIZE(exynos5420_clk_regs));
+ samsung_clk_restore(reg_base, exynos5x_save,
+ ARRAY_SIZE(exynos5x_clk_regs));
}
static struct syscore_ops exynos5420_clk_syscore_ops = {
@@ -201,9 +210,9 @@ static struct syscore_ops exynos5420_clk_syscore_ops = {
static void exynos5420_clk_sleep_init(void)
{
- exynos5420_save = samsung_clk_alloc_reg_dump(exynos5420_clk_regs,
- ARRAY_SIZE(exynos5420_clk_regs));
- if
Re: [PATCH 1/3] clk: exynos5420: Add 5800 specific clocks
On Friday 02 May 2014 18:33:39 Arun Kumar K wrote: From: Alim Akhtar alim.akh...@samsung.com Exynos5800 clock structure is mostly similar to 5420 with only a small delta changes. So the 5420 clock file is re-used for 5800 also. The common clocks for both are seggreagated and few clocks which are different for both are separately initialized. Signed-off-by: Alim Akhtar alim.akh...@samsung.com Signed-off-by: Arun Kumar K arun...@samsung.com This isn't about your specific patch, but every time I see a new exynos variant get supported, it comes with a clock driver patch that is at least as big as all the other patches combined. New variants come out all the time now, and we are starting to accumulate huge amounts of clock definitions both in the source and the binary. I think we should try to come up with a better way to represent the clocks. I don't think any other SoC family is nearly as bad as Exynos, either because they have much fewer models, or because they abstract their clocks more and put all the tables into DT. I'm definitely not saying no to the exynos5800 addition for this, but I'm starting to get a little annoyed, and I think it would be good to come up with a new clock binding before we see 64-bit Exynos variants. Arnd -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 1/3] clk: exynos5420: Add 5800 specific clocks
Arnd, On Fri, May 2, 2014 at 11:52 AM, Arnd Bergmann a...@arndb.de wrote: On Friday 02 May 2014 18:33:39 Arun Kumar K wrote: From: Alim Akhtar alim.akh...@samsung.com Exynos5800 clock structure is mostly similar to 5420 with only a small delta changes. So the 5420 clock file is re-used for 5800 also. The common clocks for both are seggreagated and few clocks which are different for both are separately initialized. Signed-off-by: Alim Akhtar alim.akh...@samsung.com Signed-off-by: Arun Kumar K arun...@samsung.com This isn't about your specific patch, but every time I see a new exynos variant get supported, it comes with a clock driver patch that is at least as big as all the other patches combined. New variants come out all the time now, and we are starting to accumulate huge amounts of clock definitions both in the source and the binary. I think we should try to come up with a better way to represent the clocks. I don't think any other SoC family is nearly as bad as Exynos, either because they have much fewer models, or because they abstract their clocks more and put all the tables into DT. I'm definitely not saying no to the exynos5800 addition for this, but I'm starting to get a little annoyed, and I think it would be good to come up with a new clock binding before we see 64-bit Exynos variants. One thing to note: your suggestion will almost certainly not be conducive to get stable device trees. IMHO there's pretty much a zero chance that you could properly describe all of the exynos clocks in the first, second, third, or twentieth attempt. That means that if anyone ever took it in their head to actually ship a device tree that wasn't bundled with the kernel that it would probably be wrong. Declaring just I have exynos5800 clocks means that you're not relying on the device tree. The clocks are pretty table-based as-is, and I think that's about the best you're going to get. NOTE: one could argue that possibly the 5420 and 5800 are different enough that they ought to have separate tables. I don't feel like I'm in enough of an ownership position to make that tradeoff either way, though. -Doug -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 1/3] clk: exynos5420: Add 5800 specific clocks
On 02.05.2014 21:35, Doug Anderson wrote: Arnd, On Fri, May 2, 2014 at 11:52 AM, Arnd Bergmann a...@arndb.de wrote: On Friday 02 May 2014 18:33:39 Arun Kumar K wrote: From: Alim Akhtar alim.akh...@samsung.com Exynos5800 clock structure is mostly similar to 5420 with only a small delta changes. So the 5420 clock file is re-used for 5800 also. The common clocks for both are seggreagated and few clocks which are different for both are separately initialized. Signed-off-by: Alim Akhtar alim.akh...@samsung.com Signed-off-by: Arun Kumar K arun...@samsung.com This isn't about your specific patch, but every time I see a new exynos variant get supported, it comes with a clock driver patch that is at least as big as all the other patches combined. New variants come out all the time now, and we are starting to accumulate huge amounts of clock definitions both in the source and the binary. I think we should try to come up with a better way to represent the clocks. I don't think any other SoC family is nearly as bad as Exynos, either because they have much fewer models, or because they abstract their clocks more and put all the tables into DT. I'm definitely not saying no to the exynos5800 addition for this, but I'm starting to get a little annoyed, and I think it would be good to come up with a new clock binding before we see 64-bit Exynos variants. One thing to note: your suggestion will almost certainly not be conducive to get stable device trees. IMHO there's pretty much a zero chance that you could properly describe all of the exynos clocks in the first, second, third, or twentieth attempt. That means that if anyone ever took it in their head to actually ship a device tree that wasn't bundled with the kernel that it would probably be wrong. Declaring just I have exynos5800 clocks means that you're not relying on the device tree. The clocks are pretty table-based as-is, and I think that's about the best you're going to get. +1 and similarly to pinctrl stuff. Both full-DT and table-based approaches were being discussed long time ago when moving Exynos to DT and generic frameworks and the conclusion was clearly in favor of the latter. Moreover, I don't think we should really be concerned about this, because we already have far less changes (not counting device tree sources) needed to support a SoC than we had before, in board file times. Not even saying that new SoCs are not being added that often. NOTE: one could argue that possibly the 5420 and 5800 are different enough that they ought to have separate tables. I don't feel like I'm in enough of an ownership position to make that tradeoff either way, though. I don't have the datasheets, but looking at the changes needed, they don't seem to be more different than Exynos4210 and Exynos4x12. The approach taken looks fine for me. Best regards, Tomasz -- To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
