Hi Geert, On Friday, March 17, 2017, Geert Uytterhoeven wrote: > So in the absence of an "rtc0" clock in the device node (you don't have > "clock-names" properties in the rtc devvice node yet), it will fall back > to clk_get_sys(), and will find the global "rtc0" clock. Unless you call > it "rtc"... > > Most drivers using a single clock just pass NULL instead of a name, so it > will match the first clock found. > > I think the simplest solution is to check if your device is instantiated > from DT (pdev->dev.of_node != NULL), and pass NULL (or "fck", when you add > multiple clocks to the DT bindings) to devm_clk_get() if that's the case.
OK, so leave current SuperH code the way it is, but add the case for (pdev->dev.of_node != NULL) and do things the 'new way' so I can have an RTC clock name of "rtc". Question: Is your idea to add all the clocks (X1, X3, EXTAL), but put the first one as the peripheral clock (the one that runs the register interface 'p0')? Chris -- You received this message because you are subscribed to "rtc-linux". Membership options at http://groups.google.com/group/rtc-linux . Please read http://groups.google.com/group/rtc-linux/web/checklist before submitting a driver. --- You received this message because you are subscribed to the Google Groups "rtc-linux" group. To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
