Re: [PATCH v1] clk: Keep clocks in their initial state until clk_disable_unused() is called

2017-08-21 Thread Boris Brezillon
+Doug Le Wed, 9 Aug 2017 15:37:29 +0800, Elaine Zhang a écrit : > ome drivers are briefly preparing+enabling the clock in their *Some > ->probe() hook and disable+unprepare them before leaving the function. > > This can be problem if a clock is shared between

Re: [PATCH v1] clk: Keep clocks in their initial state until clk_disable_unused() is called

2017-08-21 Thread Boris Brezillon
+Doug Le Wed, 9 Aug 2017 15:37:29 +0800, Elaine Zhang a écrit : > ome drivers are briefly preparing+enabling the clock in their *Some > ->probe() hook and disable+unprepare them before leaving the function. > > This can be problem if a clock is shared between different devices, and > one

[RESEND PATCH v1] clk: Keep clocks in their initial state until clk_disable_unused() is called

2017-08-09 Thread Elaine Zhang
From: Boris Brezillon Some drivers are briefly preparing+enabling the clock in their ->probe() hook and disable+unprepare them before leaving the function. This can be problem if a clock is shared between different devices, and one of these devices is

[RESEND PATCH v1] clk: Keep clocks in their initial state until clk_disable_unused() is called

2017-08-09 Thread Elaine Zhang
From: Boris Brezillon Some drivers are briefly preparing+enabling the clock in their ->probe() hook and disable+unprepare them before leaving the function. This can be problem if a clock is shared between different devices, and one of these devices is critical to the system. If this clock is

[PATCH v1] clk: Keep clocks in their initial state until clk_disable_unused() is called

2017-08-09 Thread Elaine Zhang
ome drivers are briefly preparing+enabling the clock in their ->probe() hook and disable+unprepare them before leaving the function. This can be problem if a clock is shared between different devices, and one of these devices is critical to the system. If this clock is enabled/disabled by a

[PATCH v1] clk: Keep clocks in their initial state until clk_disable_unused() is called

2017-08-09 Thread Elaine Zhang
ome drivers are briefly preparing+enabling the clock in their ->probe() hook and disable+unprepare them before leaving the function. This can be problem if a clock is shared between different devices, and one of these devices is critical to the system. If this clock is enabled/disabled by a