From: Peng Fan <peng.fan@nxp.com> To: Shawn Guo <shawn.gsc@gmail.com> Cc: "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, Abel Vesa <abel.vesa@nxp.com>, Anson Huang <anson.huang@nxp.com>, "ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>, Fabio Estevam <festevam@gmail.com>, Sascha Hauer <s.hauer@pengutronix.de>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, dl-linux-imx <linux-imx@nxp.com>, Sascha Hauer <kernel@pengutronix.de>, "git@andred.net" <git@andred.net>, Leonard Crestez <leonard.crestez@nxp.com>, "info@metux.net" <info@metux.net>, "allison@lohutok.net" <allison@lohutok.net> Subject: RE: [PATCH V2 0/3] ARM: imx: move cpu code to drivers/soc/imx Date: Wed, 20 May 2020 06:03:27 +0000 [thread overview] Message-ID: <DB6PR0402MB2760791698EADD705F5B2E6F88B60@DB6PR0402MB2760.eurprd04.prod.outlook.com> (raw) In-Reply-To: <CAJBJ56J-q7BreW9L4B7QbCkmxPEkpY6YMrBbzG3HWk3FL+wJwg@mail.gmail.com> Hi Shawn, > Subject: Re: [PATCH V2 0/3] ARM: imx: move cpu code to drivers/soc/imx > > On Wed, May 20, 2020 at 8:57 AM Shawn Guo <shawnguo@kernel.org> > wrote: > > > > On Wed, Apr 29, 2020 at 05:17:20PM +0800, peng.fan@nxp.com wrote: > > > From: Peng Fan <peng.fan@nxp.com> > > > > > > V2: > > > Keep i.MX1/2/3/5 cpu type for completness Correct return value in > > > patch 1/3 use CONFIG_ARM to guard compile soc-imx.c in patch 3/3 > > > > > > V1: > > > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpa > > > > tchwork.kernel.org%2Fcover%2F11433689%2F&data=02%7C01%7Cpen > g.fan > > > %40nxp.com%7C3fe49570a6824631476908d7fc6e5cd3%7C686ea1d3bc2 > b4c6fa92c > > > > d99c5c301635%7C0%7C0%7C637255423274738401&sdata=ELtEt3Nbg > kUg83w4 > > > UbCftkVMu0toYDUXJy4MgLc8qbQ%3D&reserved=0 > > > RFC version : > > > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpa > > > > tchwork.kernel.org%2Fcover%2F11336433%2F&data=02%7C01%7Cpen > g.fan > > > %40nxp.com%7C3fe49570a6824631476908d7fc6e5cd3%7C686ea1d3bc2 > b4c6fa92c > > > > d99c5c301635%7C0%7C0%7C637255423274738401&sdata=RE%2Fprw > CLb7fQpY > > > hmszlnXxTBKJVdEXsjMBrd2ZHmKc8%3D&reserved=0 > > > > > > Nothing changed in v1, just rename to formal patches > > > > > > Shawn, > > > The original concern has been eliminated in RFC discussion, so > > > this patchset is ready to be in next. > > > Thanks. > > > > > > Follow i.MX8, move the soc device register code to drivers/soc/imx > > > to simplify arch/arm/mach-imx/cpu.c > > > > > > I planned to use similar logic as soc-imx8m.c to restructure > > > soc-imx.c and merged the two files into one. But not sure, so still > > > keep the logic in cpu.c. > > > > > > There is one change is the platform devices are not under > > > /sys/devices/soc0 after patch 1/4. Actually ARM64 platform devices > > > are not under /sys/devices/soc0, such as i.MX8/8M. > > > So it should not hurt to let the platform devices under platform dir. > > > > > > Peng Fan (3): > > > ARM: imx: use device_initcall for imx_soc_device_init > > > ARM: imx: move cpu definitions into a header > > > soc: imx: move cpu code to drivers/soc/imx > > > > Applied all, thanks. > > Unfortunately, I have to drop this, as it turns out the series needs a rebase > onto for-next. The series conflicts with 'ARM: vf610: report soc info via soc > device' there. I just posted out v3 which rebased on latest next tree and resolved the conflicts. Thanks, Peng. > > Shawn
WARNING: multiple messages have this Message-ID (diff)
From: Peng Fan <peng.fan@nxp.com> To: Shawn Guo <shawn.gsc@gmail.com> Cc: "info@metux.net" <info@metux.net>, Abel Vesa <abel.vesa@nxp.com>, Anson Huang <anson.huang@nxp.com>, "ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>, "git@andred.net" <git@andred.net>, Sascha Hauer <s.hauer@pengutronix.de>, "allison@lohutok.net" <allison@lohutok.net>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, dl-linux-imx <linux-imx@nxp.com>, Sascha Hauer <kernel@pengutronix.de>, Leonard Crestez <leonard.crestez@nxp.com>, Fabio Estevam <festevam@gmail.com>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: RE: [PATCH V2 0/3] ARM: imx: move cpu code to drivers/soc/imx Date: Wed, 20 May 2020 06:03:27 +0000 [thread overview] Message-ID: <DB6PR0402MB2760791698EADD705F5B2E6F88B60@DB6PR0402MB2760.eurprd04.prod.outlook.com> (raw) In-Reply-To: <CAJBJ56J-q7BreW9L4B7QbCkmxPEkpY6YMrBbzG3HWk3FL+wJwg@mail.gmail.com> Hi Shawn, > Subject: Re: [PATCH V2 0/3] ARM: imx: move cpu code to drivers/soc/imx > > On Wed, May 20, 2020 at 8:57 AM Shawn Guo <shawnguo@kernel.org> > wrote: > > > > On Wed, Apr 29, 2020 at 05:17:20PM +0800, peng.fan@nxp.com wrote: > > > From: Peng Fan <peng.fan@nxp.com> > > > > > > V2: > > > Keep i.MX1/2/3/5 cpu type for completness Correct return value in > > > patch 1/3 use CONFIG_ARM to guard compile soc-imx.c in patch 3/3 > > > > > > V1: > > > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpa > > > > tchwork.kernel.org%2Fcover%2F11433689%2F&data=02%7C01%7Cpen > g.fan > > > %40nxp.com%7C3fe49570a6824631476908d7fc6e5cd3%7C686ea1d3bc2 > b4c6fa92c > > > > d99c5c301635%7C0%7C0%7C637255423274738401&sdata=ELtEt3Nbg > kUg83w4 > > > UbCftkVMu0toYDUXJy4MgLc8qbQ%3D&reserved=0 > > > RFC version : > > > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpa > > > > tchwork.kernel.org%2Fcover%2F11336433%2F&data=02%7C01%7Cpen > g.fan > > > %40nxp.com%7C3fe49570a6824631476908d7fc6e5cd3%7C686ea1d3bc2 > b4c6fa92c > > > > d99c5c301635%7C0%7C0%7C637255423274738401&sdata=RE%2Fprw > CLb7fQpY > > > hmszlnXxTBKJVdEXsjMBrd2ZHmKc8%3D&reserved=0 > > > > > > Nothing changed in v1, just rename to formal patches > > > > > > Shawn, > > > The original concern has been eliminated in RFC discussion, so > > > this patchset is ready to be in next. > > > Thanks. > > > > > > Follow i.MX8, move the soc device register code to drivers/soc/imx > > > to simplify arch/arm/mach-imx/cpu.c > > > > > > I planned to use similar logic as soc-imx8m.c to restructure > > > soc-imx.c and merged the two files into one. But not sure, so still > > > keep the logic in cpu.c. > > > > > > There is one change is the platform devices are not under > > > /sys/devices/soc0 after patch 1/4. Actually ARM64 platform devices > > > are not under /sys/devices/soc0, such as i.MX8/8M. > > > So it should not hurt to let the platform devices under platform dir. > > > > > > Peng Fan (3): > > > ARM: imx: use device_initcall for imx_soc_device_init > > > ARM: imx: move cpu definitions into a header > > > soc: imx: move cpu code to drivers/soc/imx > > > > Applied all, thanks. > > Unfortunately, I have to drop this, as it turns out the series needs a rebase > onto for-next. The series conflicts with 'ARM: vf610: report soc info via soc > device' there. I just posted out v3 which rebased on latest next tree and resolved the conflicts. Thanks, Peng. > > 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:[~2020-05-20 6:03 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-29 9:17 [PATCH V2 0/3] ARM: imx: move cpu code to drivers/soc/imx peng.fan 2020-04-29 9:17 ` peng.fan 2020-04-29 9:17 ` [PATCH V2 1/3] ARM: imx: use device_initcall for imx_soc_device_init peng.fan 2020-04-29 9:17 ` peng.fan 2020-04-29 9:17 ` [PATCH V2 2/3] ARM: imx: move cpu definitions into a header peng.fan 2020-04-29 9:17 ` peng.fan 2020-04-29 9:17 ` [PATCH V2 3/3] soc: imx: move cpu code to drivers/soc/imx peng.fan 2020-04-29 9:17 ` peng.fan 2020-05-20 0:56 ` [PATCH V2 0/3] ARM: " Shawn Guo 2020-05-20 0:56 ` Shawn Guo 2020-05-20 3:31 ` Shawn Guo 2020-05-20 3:31 ` Shawn Guo 2020-05-20 6:03 ` Peng Fan [this message] 2020-05-20 6:03 ` Peng Fan
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=DB6PR0402MB2760791698EADD705F5B2E6F88B60@DB6PR0402MB2760.eurprd04.prod.outlook.com \ --to=peng.fan@nxp.com \ --cc=abel.vesa@nxp.com \ --cc=allison@lohutok.net \ --cc=anson.huang@nxp.com \ --cc=ard.biesheuvel@linaro.org \ --cc=festevam@gmail.com \ --cc=git@andred.net \ --cc=info@metux.net \ --cc=kernel@pengutronix.de \ --cc=leonard.crestez@nxp.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-imx@nxp.com \ --cc=linux-kernel@vger.kernel.org \ --cc=s.hauer@pengutronix.de \ --cc=shawn.gsc@gmail.com \ /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.