From: "A.s. Dong" <aisheng.dong@nxp.com> To: Stephen Boyd <sboyd@kernel.org>, "linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org> Cc: "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "mturquette@baylibre.com" <mturquette@baylibre.com>, "shawnguo@kernel.org" <shawnguo@kernel.org>, Fabio Estevam <fabio.estevam@nxp.com>, dl-linux-imx <linux-imx@nxp.com>, "kernel@pengutronix.de" <kernel@pengutronix.de> Subject: RE: [PATCH V5 9/9] clk: imx: add imx8qxp clk driver Date: Thu, 25 Oct 2018 14:43:06 +0000 [thread overview] Message-ID: <AM0PR04MB4211CE37D05973D6CE521D7080F70@AM0PR04MB4211.eurprd04.prod.outlook.com> (raw) In-Reply-To: <AM0PR04MB42112BEEF4DB939F13D6AF1680F90@AM0PR04MB4211.eurprd04.prod.outlook.com> Hi Stephen, > -----Original Message----- > From: A.s. Dong > Sent: Friday, October 19, 2018 5:05 PM [...] > > -----Original Message----- > > From: Stephen Boyd [mailto:sboyd@kernel.org] > > Sent: Friday, October 19, 2018 4:46 AM > > To: A.s. Dong <aisheng.dong@nxp.com>; linux-clk@vger.kernel.org > > Cc: linux-arm-kernel@lists.infradead.org; mturquette@baylibre.com; > > shawnguo@kernel.org; Fabio Estevam <fabio.estevam@nxp.com>; > > dl-linux-imx <linux-imx@nxp.com>; kernel@pengutronix.de > > Subject: RE: [PATCH V5 9/9] clk: imx: add imx8qxp clk driver > > > > Quoting A.s. Dong (2018-10-18 11:13:39) > > > > -----Original Message----- > > > > From: Stephen Boyd [mailto:sboyd@kernel.org] > > > > Sent: Friday, October 19, 2018 1:38 AM > > > > To: A.s. Dong <aisheng.dong@nxp.com>; linux-clk@vger.kernel.org > > > > Cc: linux-arm-kernel@lists.infradead.org; mturquette@baylibre.com; > > > > shawnguo@kernel.org; Fabio Estevam <fabio.estevam@nxp.com>; > > > > dl-linux-imx <linux-imx@nxp.com>; kernel@pengutronix.de; A.s. Dong > > > > <aisheng.dong@nxp.com> > > > > Subject: Re: [PATCH V5 9/9] clk: imx: add imx8qxp clk driver > > > > > > > > Quoting A.s. Dong (2018-10-18 09:54:15) > > > > > + > > > > > +#include <dt-bindings/clock/imx8qxp-clock.h> > > > > > +#include <linux/clk.h> > > > > > +#include <linux/err.h> > > > > > +#include <linux/io.h> > > > > > +#include <linux/of.h> > > > > > +#include <linux/of_address.h> > > > > > +#include <linux/platform_device.h> #include <linux/slab.h> > > > > > + > > > > > +#include <soc/imx/imx8qxp/lpcg.h> > > > > > + > > > > > +#include "clk-scu.h" > > > > > + > > > > > +static struct clk_hw_onecell_data *imx8qxp_clk_data; > > > > > + > > > > > +static const char * const enet_sels[] = { "enet_25MHz", > > > > > +"enet_125MHz", }; static const char * const > > > > > +enet0_rmii_tx_sels[] = { "enet0_ref_div", "dummy", }; static > > > > > +const char * const enet1_rmii_tx_sels[] = { "enet1_ref_div", > > > > > +"dummy", }; > > > > > + > > > > > +static int imx8qxp_clk_probe(struct platform_device *pdev) { > > > > > + struct device_node *ccm_node = pdev->dev.of_node; > > > > > > > > Where's the DT binding for this device? > > > > > > Sorry for missed to mention this. > > > It's been merged into scu binding doc per Rob's request which has > > > already been in Shawn's tree. > > > > > > Please take a look at here: > [...] > > > > Ok I ask because it's odd to hardcode physical addresses in a clk > > driver when those should come from DT in reg properties. Was Rob aware > > that this clk node was combining I/O memory and message passing? > > Yes, I agree with you. That seems like a special to i.MX case. > The problem is not all clocks having a LPCG gate. And those LPCGs are also not > continuous and may be shared by many clocks which make things more > complicated. > I'm not sure parsing from device tree could be better way to do it. > Probably need huge changes. > > How would you suggest? > Do you think we can workaround this due to the special iMX? > Do you have any suggestion about this? Regards Dong Aisheng
WARNING: multiple messages have this Message-ID (diff)
From: aisheng.dong@nxp.com (A.s. Dong) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH V5 9/9] clk: imx: add imx8qxp clk driver Date: Thu, 25 Oct 2018 14:43:06 +0000 [thread overview] Message-ID: <AM0PR04MB4211CE37D05973D6CE521D7080F70@AM0PR04MB4211.eurprd04.prod.outlook.com> (raw) In-Reply-To: <AM0PR04MB42112BEEF4DB939F13D6AF1680F90@AM0PR04MB4211.eurprd04.prod.outlook.com> Hi Stephen, > -----Original Message----- > From: A.s. Dong > Sent: Friday, October 19, 2018 5:05 PM [...] > > -----Original Message----- > > From: Stephen Boyd [mailto:sboyd at kernel.org] > > Sent: Friday, October 19, 2018 4:46 AM > > To: A.s. Dong <aisheng.dong@nxp.com>; linux-clk at vger.kernel.org > > Cc: linux-arm-kernel at lists.infradead.org; mturquette at baylibre.com; > > shawnguo at kernel.org; Fabio Estevam <fabio.estevam@nxp.com>; > > dl-linux-imx <linux-imx@nxp.com>; kernel at pengutronix.de > > Subject: RE: [PATCH V5 9/9] clk: imx: add imx8qxp clk driver > > > > Quoting A.s. Dong (2018-10-18 11:13:39) > > > > -----Original Message----- > > > > From: Stephen Boyd [mailto:sboyd at kernel.org] > > > > Sent: Friday, October 19, 2018 1:38 AM > > > > To: A.s. Dong <aisheng.dong@nxp.com>; linux-clk at vger.kernel.org > > > > Cc: linux-arm-kernel at lists.infradead.org; mturquette at baylibre.com; > > > > shawnguo at kernel.org; Fabio Estevam <fabio.estevam@nxp.com>; > > > > dl-linux-imx <linux-imx@nxp.com>; kernel at pengutronix.de; A.s. Dong > > > > <aisheng.dong@nxp.com> > > > > Subject: Re: [PATCH V5 9/9] clk: imx: add imx8qxp clk driver > > > > > > > > Quoting A.s. Dong (2018-10-18 09:54:15) > > > > > + > > > > > +#include <dt-bindings/clock/imx8qxp-clock.h> > > > > > +#include <linux/clk.h> > > > > > +#include <linux/err.h> > > > > > +#include <linux/io.h> > > > > > +#include <linux/of.h> > > > > > +#include <linux/of_address.h> > > > > > +#include <linux/platform_device.h> #include <linux/slab.h> > > > > > + > > > > > +#include <soc/imx/imx8qxp/lpcg.h> > > > > > + > > > > > +#include "clk-scu.h" > > > > > + > > > > > +static struct clk_hw_onecell_data *imx8qxp_clk_data; > > > > > + > > > > > +static const char * const enet_sels[] = { "enet_25MHz", > > > > > +"enet_125MHz", }; static const char * const > > > > > +enet0_rmii_tx_sels[] = { "enet0_ref_div", "dummy", }; static > > > > > +const char * const enet1_rmii_tx_sels[] = { "enet1_ref_div", > > > > > +"dummy", }; > > > > > + > > > > > +static int imx8qxp_clk_probe(struct platform_device *pdev) { > > > > > + struct device_node *ccm_node = pdev->dev.of_node; > > > > > > > > Where's the DT binding for this device? > > > > > > Sorry for missed to mention this. > > > It's been merged into scu binding doc per Rob's request which has > > > already been in Shawn's tree. > > > > > > Please take a look at here: > [...] > > > > Ok I ask because it's odd to hardcode physical addresses in a clk > > driver when those should come from DT in reg properties. Was Rob aware > > that this clk node was combining I/O memory and message passing? > > Yes, I agree with you. That seems like a special to i.MX case. > The problem is not all clocks having a LPCG gate. And those LPCGs are also not > continuous and may be shared by many clocks which make things more > complicated. > I'm not sure parsing from device tree could be better way to do it. > Probably need huge changes. > > How would you suggest? > Do you think we can workaround this due to the special iMX? > Do you have any suggestion about this? Regards Dong Aisheng
next prev parent reply other threads:[~2018-10-25 14:43 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-18 16:53 [PATCH V5 0/9] clk: imx: add imx8qxp clock support A.s. Dong 2018-10-18 16:53 ` A.s. Dong 2018-10-18 16:53 ` [PATCH V5 1/9] clk: imx: add configuration option for mmio clks A.s. Dong 2018-10-18 16:53 ` A.s. Dong 2018-10-18 16:53 ` [PATCH V5 2/9] clk: imx: scu: add scu clock common part A.s. Dong 2018-10-18 16:53 ` A.s. Dong 2018-10-18 16:53 ` [PATCH V5 3/9] clk: imx: scu: add scu clock divider A.s. Dong 2018-10-18 16:53 ` A.s. Dong 2018-10-18 16:53 ` [PATCH V5 4/9] clk: imx: scu: add scu clock gpr divider A.s. Dong 2018-10-18 16:53 ` A.s. Dong 2018-10-18 16:54 ` [PATCH V5 5/9] clk: imx: scu: add scu clock gate A.s. Dong 2018-10-18 16:54 ` A.s. Dong 2018-10-18 16:54 ` [PATCH V5 6/9] clk: imx: scu: add scu clock gpr gate A.s. Dong 2018-10-18 16:54 ` A.s. Dong 2018-10-18 16:54 ` [PATCH V5 7/9] clk: imx: scu: add scu clock mux A.s. Dong 2018-10-18 16:54 ` A.s. Dong 2018-10-18 16:54 ` [PATCH V5 8/9] clk: imx: scu: add scu clock gpr mux A.s. Dong 2018-10-18 16:54 ` A.s. Dong 2018-10-18 16:54 ` [PATCH V5 9/9] clk: imx: add imx8qxp clk driver A.s. Dong 2018-10-18 16:54 ` A.s. Dong 2018-10-18 17:38 ` Stephen Boyd 2018-10-18 17:38 ` Stephen Boyd 2018-10-18 18:13 ` A.s. Dong 2018-10-18 18:13 ` A.s. Dong 2018-10-18 20:46 ` Stephen Boyd 2018-10-18 20:46 ` Stephen Boyd 2018-10-19 9:05 ` A.s. Dong 2018-10-19 9:05 ` A.s. Dong 2018-10-25 14:43 ` A.s. Dong [this message] 2018-10-25 14:43 ` A.s. Dong 2018-11-10 15:58 ` A.s. Dong 2018-11-10 15:58 ` A.s. Dong 2018-11-14 23:23 ` Stephen Boyd 2018-11-14 23:23 ` Stephen Boyd
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=AM0PR04MB4211CE37D05973D6CE521D7080F70@AM0PR04MB4211.eurprd04.prod.outlook.com \ --to=aisheng.dong@nxp.com \ --cc=fabio.estevam@nxp.com \ --cc=kernel@pengutronix.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-clk@vger.kernel.org \ --cc=linux-imx@nxp.com \ --cc=mturquette@baylibre.com \ --cc=sboyd@kernel.org \ --cc=shawnguo@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.