[PATCH 3/7] clk: imx-cpu: Add missing CLK_IS_CRITICAL

2020-08-19 Thread Sascha Hauer
The CPU clock should never be disabled, mark it as critical as done in the Kernel. Signed-off-by: Sascha Hauer --- drivers/clk/imx/clk-cpu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/clk/imx/clk-cpu.c b/drivers/clk/imx/clk-cpu.c index 13b2dfc9ad..f8d54ddba3 1006

[PATCH 7/7] clk: imx8mp: update clk driver from Linux kernel

2020-08-19 Thread Sascha Hauer
This updates the clock driver to the Linux driver as of v5.9-rc1. The patch is bigger than it needs to be, but this time care has been taken to minimize the diff against the Linux driver to make future updates easier. Signed-off-by: Sascha Hauer --- drivers/clk/imx/clk-imx8mp.c | 789 ++

[PATCH 1/7] clk: imx: make string arrays const char * const *

2020-08-19 Thread Sascha Hauer
arrays of pointers to strings should be of type const char * const *, so that not only the arrays of pointers are const, but also the strings. Signed-off-by: Sascha Hauer --- drivers/clk/imx/clk-composite-8m.c | 2 +- drivers/clk/imx/clk.h | 12 ++-- 2 files changed, 7 inse

[PATCH 4/7] clk: imx. clk-composite-8m: Update from Linux Kernel

2020-08-19 Thread Sascha Hauer
Update clk-composite-8m to Linux as of v5.9-rc2. This is a combination of Linux commits: 0e40198dc28b6 ("clk: imx: add imx8m_clk_hw_composite_bus") f90b68d6c8b00 ("clk: imx: add mux ops for i.MX8M composite clk") 62668b68dc8e7 ("clk: imx: composite-8m: add imx8m_clk_hw_composite_core") Signed-off

[PATCH 5/7] clk: imx: Add imx_clk_gate4_flags

2020-08-19 Thread Sascha Hauer
Needed for further clock driver updates, taken from Linux Kernel. Signed-off-by: Sascha Hauer --- drivers/clk/imx/clk.h | 6 ++ 1 file changed, 6 insertions(+) diff --git a/drivers/clk/imx/clk.h b/drivers/clk/imx/clk.h index 32e7c5cbb7..02270cdf0f 100644 --- a/drivers/clk/imx/clk.h +++ b/dr

[PATCH 2/7] clk: imx: clk-pll14xx: remove debug leftover

2020-08-19 Thread Sascha Hauer
The printfs were never meant to go upstream. Remove them. Signed-off-by: Sascha Hauer --- drivers/clk/imx/clk-pll14xx.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/clk/imx/clk-pll14xx.c b/drivers/clk/imx/clk-pll14xx.c index 91e9624a60..6ba519516b 100644 --- a/dr

[PATCH 6/7] clk: imx: Add Linux function names

2020-08-19 Thread Sascha Hauer
Add some function names used in Linux as define to the corresponding functions in barebox. This is done to be able to use the Linux function names in barebox in order to reduce the diff size between the barebox and Linux clock drivers. Signed-off-by: Sascha Hauer --- drivers/clk/imx/clk.h | 22 +

[PATCH] clk: imx-imx8mp: Mark arm_a53_core clk as critical

2020-08-19 Thread Sascha Hauer
Changes in imx8mp.dtsi for v5.8-rc1 added some clock reparenting to the device tree. IMX8MP_CLK_A53_CORE is reparented to IMX8MP_ARM_PLL_OUT. The latter is not enabled in hardware, so the CPU clock is disabled locking up the system. Mark IMX8MP_CLK_A53_CORE as critical so that the new parent gets e

Re: [PATCH v3] bootm: add global.bootm.root_dev env var for booting via PARTUUID

2020-08-19 Thread Robert Karszniewicz
What's the status on this, please? Greetings. On 8/10/20 2:20 PM, Robert Karszniewicz wrote: Introduces a new env var which specifies which device is the rootfs device to be used in Linux, passed to Linux via bootargs, identified by the rootfs partition's PARTUUID. global.bootm.root_dev supple

[PATCH v2] watchdog: fix watchdog_set_timeout breakage for drivers like imxwd

2020-08-19 Thread Ahmad Fatoum
Commit 0b944fce55f4 ("watchdog: permit `wd 0` for non-stoppable, but inactive, watchdogs") silently broke use of watchdogs, that report being inactive at driver probe time, altogether. Because those always had watchdog_hw_running evaluating to false, it early exited without a chance to ever actuall

Re: [PATCH v4 5/7] ARM: protonic-imx6: port Protonic specific board code

2020-08-19 Thread David Jander
On Wed, 19 Aug 2020 08:27:41 +0200 Sascha Hauer wrote: > On Mon, Aug 17, 2020 at 10:19:27AM +0200, Oleksij Rempel wrote: > > +static int prt_imx6_set_mac(struct prt_imx6_priv *priv, > > + struct prti6q_rfid_contents *rfid) > > +{ > > + struct device_d *dev = priv->dev; > >

Re: [PATCH] watchdog: fix watchdog_set_timeout breakage for drivers like imxwd

2020-08-19 Thread Sascha Hauer
On Tue, Aug 18, 2020 at 03:18:16PM +0200, Ahmad Fatoum wrote: > Commit 0b944fce55f4 ("watchdog: permit `wd 0` for non-stoppable, but > inactive, watchdogs") silently broke use of non-stoppable, but inactive, > watchdogs altogether. Because those always had watchdog_hw_running > evaluating to false,

Re: [PATCH] watchdog: fix watchdog_set_timeout breakage for drivers like imxwd

2020-08-19 Thread Sascha Hauer
On Wed, Aug 19, 2020 at 09:18:44AM +0200, Ahmad Fatoum wrote: > On 8/19/20 8:59 AM, Sascha Hauer wrote: > > Hi Ahmad, > > > > On Tue, Aug 18, 2020 at 03:18:16PM +0200, Ahmad Fatoum wrote: > >> Commit 0b944fce55f4 ("watchdog: permit `wd 0` for non-stoppable, but > >> inactive, watchdogs") silently

[PATCH v2] Documentation: update for loongson1 board

2020-08-19 Thread Du Huanpeng
after migrating to multi-image support the image path was changed. Signed-off-by: Du Huanpeng --- Documentation/boards/mips/loongson_ls1b.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/boards/mips/loongson_ls1b.rst b/Documentation/boards/mips/loongson_ls1b

Re: [PATCH] watchdog: fix watchdog_set_timeout breakage for drivers like imxwd

2020-08-19 Thread Ahmad Fatoum
On 8/19/20 8:59 AM, Sascha Hauer wrote: > Hi Ahmad, > > On Tue, Aug 18, 2020 at 03:18:16PM +0200, Ahmad Fatoum wrote: >> Commit 0b944fce55f4 ("watchdog: permit `wd 0` for non-stoppable, but >> inactive, watchdogs") silently broke use of non-stoppable, but inactive, >> watchdogs altogether. > > Di

Re: [PATCH] watchdog: fix watchdog_set_timeout breakage for drivers like imxwd

2020-08-19 Thread Sascha Hauer
Hi Ahmad, On Tue, Aug 18, 2020 at 03:18:16PM +0200, Ahmad Fatoum wrote: > Commit 0b944fce55f4 ("watchdog: permit `wd 0` for non-stoppable, but > inactive, watchdogs") silently broke use of non-stoppable, but inactive, > watchdogs altogether. Didn't this commit break *all* watchdogs? With 0b944fce