On Mon, Mar 27, 2023 at 10:51:38AM +0200, Konrad Dybcio wrote: > On 27.03.2023 07:43, Vinod Koul wrote: > > On 25-03-23, 13:40, Konrad Dybcio wrote: > >> On 25.03.2023 13:24, Vinod Koul wrote: > >>> From: Bjorn Andersson <bjorn.andersson@xxxxxxxxxx> [..] > >>> +&dispcc { > >>> + status = "okay"; > >> Any reason for disabling dispcc by default? > > > > I think that is a good question. I would prefer disabling and enabling > > in places it is required, we might have a headless system or a dev board > > where we dont have display..? > It's a double-edged sword: on one side we could disable clocks that were > mistakenly enabled, but on the other hand we do keep some some clocks > always-on within that driver.. > > Perhaps leave it on by default and shut it off per-board if need be. > There is a little bit of overhead in keeping the clock controllers enabled at all times, but I expect it to benefit us in that it would ensure that any clocks that the bootloader might have left on will be disabled. So, I think we should go with enable by default and leave enabled. Regards, Bjorn