Hi, Stephen

-----Original Message-----
From: Stephen Boyd <sboyd@kernel.org>
Sent: Saturday, June 8, 2019 2:01 AM
To: bjorn.andersson@linaro.org; catalin.marinas@arm.com;
devicetree@vger.kernel.org; dinguyen@kernel.org;
enric.balletbo@collabora.com; festevam@gmail.com;
horms+renesas@verge.net.au; jagan@amarulasolutions.com;
kernel@pengutronix.de; l.stach@pengutronix.de; linux-arm-
kernel@lists.infradead.org; linux-clk@vger.kernel.org; linux-
kernel@vger.kernel.org; mark.rutland@arm.com;
maxime.ripard@bootlin.com; mturquette@baylibre.com; olof@lixom.net;
robh+dt@kernel.org; s.hauer@pengutronix .de [off-list ref];
shawnguo@kernel.org; will.deacon@arm.com; Abel Vesa
[off-list ref]; Aisheng Dong [off-list ref]; Anson
Huang [off-list ref]; Jacky Bai [off-list ref]; Leonard
Crestez [off-list ref]
Cc: dl-linux-imx <redacted>
Subject: RE: [PATCH V3 3/4] clk: imx: Add support for i.MX8MN clock driver

Quoting Anson Huang (2019-06-06 17:50:28)

quoted

I will use devm_platform_ioremap_resource() instead of ioremap(), and
can you be more specific about devmified clk registration?

I mean using things like devm_clk_hw_register().

Sorry, I am still a little confused, all the clock register(clk_register()) are via each different
clock types like imx_clk_gate4/imx_clk_pll14xx, if using clk_hw_register, means we need
to re-write the clock driver using different clk register method, that will make the driver
completely different from i.mx8mq/i.mx8mm, they are actually same series of SoC as i.mx8mn,
it will introduce many confusion, is my understanding correct? And is it OK to just keep what
it is and make them all aligned?

Thanks,
Anson.


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel