+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
+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
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
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
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
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
6 matches
Mail list logo