On 17/08/2021 09:38:10+0200, Maxime Ripard wrote: > > > It's not entirely clear to me what those clocks are about though. If we > > > look at the clock output in the user manual, it looks like there's only > > > two clocks that are actually being output: the 32k "fanout" clock and > > > the losc. What are the 3 you're talking about?] > > > > I see three: the raw SYSTEM "CLK32K_LOSC", the RTC input + debounce > > clock (/32), and the multiplexed PAD. > > But the input and debounce clock is only for the RTC itself right? So it > should be local to the driver and doesn't need to be made available to > the other drivers > Shouldn't they be exposed to be able to use assigned-clock? -- Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
