From: Aisheng Dong <aisheng.dong@nxp.com> To: Shawn Guo <shawnguo@kernel.org> Cc: "sboyd@kernel.org" <sboyd@kernel.org>, "mturquette@baylibre.com" <mturquette@baylibre.com>, dl-linux-imx <linux-imx@nxp.com>, "kernel@pengutronix.de" <kernel@pengutronix.de>, Fabio Estevam <fabio.estevam@nxp.com>, "linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: RE: [PATCH V12 0/5] clk: imx: add imx8qxp clock support Date: Fri, 14 Dec 2018 05:38:08 +0000 [thread overview] Message-ID: <AM0PR04MB421136352C4D0A3A0A543BBF80A10@AM0PR04MB4211.eurprd04.prod.outlook.com> (raw) In-Reply-To: <20181214053033.GF13243@dragon> > -----Original Message----- > From: Shawn Guo [mailto:shawnguo@kernel.org] > On Fri, Dec 14, 2018 at 04:57:46AM +0000, Aisheng Dong wrote: > > > -----Original Message----- > > > From: Shawn Guo [mailto:shawnguo@kernel.org] On Fri, Dec 14, 2018 at > > > 03:37:47AM +0000, Aisheng Dong wrote: > > > > > -----Original Message----- > > > > > From: Shawn Guo [mailto:shawnguo@kernel.org] On Fri, Dec 14, > > > > > 2018 at 02:17:04AM +0000, Aisheng Dong wrote: > > > > > > [...] > > > > > > > > Note: It depends on SCU driver which has already been > > > > > > > > merged by > > > > > Shawn. > > > > > > > > So this patch series could go through Shawn's tree as well. > > > > > > > > > > > > > > To be clear, I'm not going to take this via my tree, and it > > > > > > > definitely needs to go through clk tree. If there is a > > > > > > > dependency on my tree, you will likely need to wait for the > > > > > > > dependency to land on > > > > > mainline and then retry. > > > > > > > > > > > > > > > > > > > Sorry, I should have corrected that comment. > > > > > > It's not depend on SCU driver which is already in the Stephen's tree. > > > > > > It actually depends on the resource ID definitions[1] and the > > > > > > centralized PM related service definitions headifle in in > > > > > > power domain series which is already in your tree. > > > > > > > > > > > > [2] can be fixed by defining them in clock driver. > > > > > > But [1] seems can't be fixed as resource ID is shared by power > > > > > > domain and possible many other SCU client drivers. > > > > > > > > > > > > Any suggestion? > > > > > > > > > > After [1] and [2] land on v4.21-rc1, you rebase the series on that. > > > > > The dependency will be gone, right? This is what I suggested above. > > > > > > > > > > > > > Okay, that may need a few more weeks. > > > > BTW, after v4.21-rc1 is out, can the mx8qxp CLK and DTS hit the > > > > final v4.21 > > > release? > > > > As I understand, usually we don't receive new feature patch after > > > > the first RC, right? > > > > > > Yes, they will have to land on 4.22 then. > > > > That's unfortunately and may need wait 3 more months. > > I really wish we can hit v4.21-rc1, then other modules driver can > > start their work based on it. > > You can not always expect all the pieces get in with one merge window. > It's very usual in upstreaming process that the dependant parts lands in > mainline with multiple release cycles. > Yes, i understand. Thanks for the clarification. > > Stephen, > > What's your option? > > > > Can we try the same way as Shawn did for arch and dts part? > > In case Stephen is fine by pulling dependency from my tree, it's all on branch > below, which has been pulled/queued by arm-soc folks for 4.21 merge window. > > git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git imx/drivers > Thanks Regards Dong Aisheng > Shawn
WARNING: multiple messages have this Message-ID (diff)
From: Aisheng Dong <aisheng.dong@nxp.com> To: Shawn Guo <shawnguo@kernel.org> Cc: "sboyd@kernel.org" <sboyd@kernel.org>, "mturquette@baylibre.com" <mturquette@baylibre.com>, dl-linux-imx <linux-imx@nxp.com>, "kernel@pengutronix.de" <kernel@pengutronix.de>, Fabio Estevam <fabio.estevam@nxp.com>, "linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: RE: [PATCH V12 0/5] clk: imx: add imx8qxp clock support Date: Fri, 14 Dec 2018 05:38:08 +0000 [thread overview] Message-ID: <AM0PR04MB421136352C4D0A3A0A543BBF80A10@AM0PR04MB4211.eurprd04.prod.outlook.com> (raw) In-Reply-To: <20181214053033.GF13243@dragon> > -----Original Message----- > From: Shawn Guo [mailto:shawnguo@kernel.org] > On Fri, Dec 14, 2018 at 04:57:46AM +0000, Aisheng Dong wrote: > > > -----Original Message----- > > > From: Shawn Guo [mailto:shawnguo@kernel.org] On Fri, Dec 14, 2018 at > > > 03:37:47AM +0000, Aisheng Dong wrote: > > > > > -----Original Message----- > > > > > From: Shawn Guo [mailto:shawnguo@kernel.org] On Fri, Dec 14, > > > > > 2018 at 02:17:04AM +0000, Aisheng Dong wrote: > > > > > > [...] > > > > > > > > Note: It depends on SCU driver which has already been > > > > > > > > merged by > > > > > Shawn. > > > > > > > > So this patch series could go through Shawn's tree as well. > > > > > > > > > > > > > > To be clear, I'm not going to take this via my tree, and it > > > > > > > definitely needs to go through clk tree. If there is a > > > > > > > dependency on my tree, you will likely need to wait for the > > > > > > > dependency to land on > > > > > mainline and then retry. > > > > > > > > > > > > > > > > > > > Sorry, I should have corrected that comment. > > > > > > It's not depend on SCU driver which is already in the Stephen's tree. > > > > > > It actually depends on the resource ID definitions[1] and the > > > > > > centralized PM related service definitions headifle in in > > > > > > power domain series which is already in your tree. > > > > > > > > > > > > [2] can be fixed by defining them in clock driver. > > > > > > But [1] seems can't be fixed as resource ID is shared by power > > > > > > domain and possible many other SCU client drivers. > > > > > > > > > > > > Any suggestion? > > > > > > > > > > After [1] and [2] land on v4.21-rc1, you rebase the series on that. > > > > > The dependency will be gone, right? This is what I suggested above. > > > > > > > > > > > > > Okay, that may need a few more weeks. > > > > BTW, after v4.21-rc1 is out, can the mx8qxp CLK and DTS hit the > > > > final v4.21 > > > release? > > > > As I understand, usually we don't receive new feature patch after > > > > the first RC, right? > > > > > > Yes, they will have to land on 4.22 then. > > > > That's unfortunately and may need wait 3 more months. > > I really wish we can hit v4.21-rc1, then other modules driver can > > start their work based on it. > > You can not always expect all the pieces get in with one merge window. > It's very usual in upstreaming process that the dependant parts lands in > mainline with multiple release cycles. > Yes, i understand. Thanks for the clarification. > > Stephen, > > What's your option? > > > > Can we try the same way as Shawn did for arch and dts part? > > In case Stephen is fine by pulling dependency from my tree, it's all on branch > below, which has been pulled/queued by arm-soc folks for 4.21 merge window. > > git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git imx/drivers > Thanks Regards Dong Aisheng > Shawn _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-12-14 5:38 UTC|newest] Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-12-13 15:42 [PATCH V12 0/5] clk: imx: add imx8qxp clock support Aisheng Dong 2018-12-13 15:42 ` Aisheng Dong 2018-12-13 15:42 ` [PATCH V12 1/5] clk: imx: add configuration option for mmio clks Aisheng Dong 2018-12-13 15:42 ` Aisheng Dong 2018-12-14 21:08 ` Stephen Boyd 2018-12-14 21:08 ` Stephen Boyd 2018-12-13 15:42 ` [PATCH V12 2/5] clk: imx: add scu clock common part Aisheng Dong 2018-12-13 15:42 ` Aisheng Dong 2018-12-14 21:08 ` Stephen Boyd 2018-12-14 21:08 ` Stephen Boyd 2018-12-13 15:42 ` [PATCH V12 3/5] clk: imx: add imx8qxp clk driver Aisheng Dong 2018-12-13 15:42 ` Aisheng Dong 2018-12-14 21:09 ` Stephen Boyd 2018-12-14 21:09 ` Stephen Boyd 2018-12-13 15:43 ` [PATCH V12 4/5] clk: imx: add lpcg clock support Aisheng Dong 2018-12-13 15:43 ` Aisheng Dong 2018-12-14 21:09 ` Stephen Boyd 2018-12-14 21:09 ` Stephen Boyd 2018-12-13 15:43 ` [PATCH V12 5/5] clk: imx: add imx8qxp lpcg driver Aisheng Dong 2018-12-13 15:43 ` Aisheng Dong 2018-12-14 21:09 ` Stephen Boyd 2018-12-14 21:09 ` Stephen Boyd 2018-12-14 2:05 ` [PATCH V12 0/5] clk: imx: add imx8qxp clock support Shawn Guo 2018-12-14 2:05 ` Shawn Guo 2018-12-14 2:17 ` Aisheng Dong 2018-12-14 2:17 ` Aisheng Dong 2018-12-14 3:19 ` Shawn Guo 2018-12-14 3:19 ` Shawn Guo 2018-12-14 3:37 ` Aisheng Dong 2018-12-14 3:37 ` Aisheng Dong 2018-12-14 3:56 ` Shawn Guo 2018-12-14 3:56 ` Shawn Guo 2018-12-14 4:57 ` Aisheng Dong 2018-12-14 4:57 ` Aisheng Dong 2018-12-14 5:30 ` Shawn Guo 2018-12-14 5:30 ` Shawn Guo 2018-12-14 5:38 ` Aisheng Dong [this message] 2018-12-14 5:38 ` Aisheng Dong 2018-12-14 6:07 ` Stephen Boyd 2018-12-14 6:07 ` Stephen Boyd 2018-12-14 6:15 ` Stephen Boyd 2018-12-14 6:15 ` Stephen Boyd 2018-12-14 6:16 ` Aisheng Dong 2018-12-14 6:16 ` Aisheng Dong 2018-12-14 6:15 ` Aisheng Dong 2018-12-14 6:15 ` Aisheng Dong 2018-12-14 5:44 ` Stephen Boyd 2018-12-14 5:44 ` 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=AM0PR04MB421136352C4D0A3A0A543BBF80A10@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.