On Wed, Oct 11, 2017 at 4:09 AM, Linus Walleij <linus.walleij@xxxxxxxxxx> wrote: > On Sat, Aug 12, 2017 at 8:43 PM, Linus Walleij <linus.walleij@xxxxxxxxxx> wrote: > >> This adds the PCLK clock to the Aspeed watchdog blocks. >> I am not directly familiar with the Aspeed clocking, but >> since the IP is derived from Faraday FTWDT010 it probably >> has the ability to run the watchdog on the PCLK if >> desired so to obtain the frequency from it, it needs to >> be present in the device tree, and for completeness the >> PCLK should also be referenced and enabled anyways. >> >> Take this opportunity to add the "faraday,ftwdt010" >> compatible as fallback to the watchdog IP blocks. >> >> Signed-off-by: Linus Walleij <linus.walleij@xxxxxxxxxx> > > Joel could you merge this through the Aspeed tree? I think > the compatible string is completely uncontroversial > (binding ACKed) to add and all should just work fine so we > can slap in "EXTCLK" later as well. How do the clock-names work? I have been writing the aspeed clk driver and updating the bindings without clock names, and instead using a identifier in phandle to reference which clock the device wants. eg: clocks = <&syscon 10>; (I'm travelling over the next few weeks so my replies might be delayed) Cheers, Joel -- To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
