Hi, miquel.raynal@xxxxxxxxxxx wrote on Fri, 13 May 2022 12:49:55 +0200: > There was a small mistake when first introducing this controller driver: > the power-domain property was missing in the device tree because there > was only one controller supported at this time (UART) and this is a > Synopsis IP which did not support power domains. The idea is to always > use these power domains when available, so let's add it to the bindings, > the DT and use it from the driver through the runtimpe PM API instead of > doing raw clk API calls. > > Changes in v4: > * Use pm_runtime_resume_and_get() instead of pm_runtime_get_sync(). > > Changes in v3: > * Moved the pm_runtime calls earlier in the probe to avoid possible > register accesses while the clocks have not yet been enabled. > > Changes in v2: > * Dropped the DT patch merged by Geert. > * Used devm_pm_runtime_enable() instead of pm_runtime_enable() and > dropped the pm_runtime_disable() calls. > * Used pm_runtime_resume_and_get() instead of pm_runtime_get_sync(). > * Collected the tags on the bindings. > > Miquel Raynal (2): > dt-bindings: mtd: renesas: Fix the NAND controller description > mtd: rawnand: renesas: Use runtime PM instead of the raw clock API > > .../bindings/mtd/renesas-nandc.yaml | 5 ++ > .../mtd/nand/raw/renesas-nand-controller.c | 51 +++++++++---------- > 2 files changed, 28 insertions(+), 28 deletions(-) > Series applied on nand/next. Thanks, Miquèl
