| Message ID | 20190603234628.10924-1-festevam@gmail.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | [1/2] remoteproc: imx: Broaden the Kconfig selection logic | expand |
On Mon, Jun 03, 2019 at 08:46:27PM -0300, Fabio Estevam wrote: > Besides i.MX6SX and i.MX7D, there are other i.MX devices that contain > Cortex M4 and could make use of the imx remoteproc driver, such as > i.MX7ULP, i.MX8M, etc. > > Instead of adding new SoC entries in the Kconfig logic, make it > broader by using the more generic ARCH_MXC, which encompasses > all the 32-bit and 64-bit i.MX devices. Reviewed-by: Oleksij Rempel <o.rempel@pengutronix.de> > Signed-off-by: Fabio Estevam <festevam@gmail.com> > --- > drivers/remoteproc/Kconfig | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/remoteproc/Kconfig b/drivers/remoteproc/Kconfig > index 18be41b8aa7e..0df301be6d9a 100644 > --- a/drivers/remoteproc/Kconfig > +++ b/drivers/remoteproc/Kconfig > @@ -16,7 +16,7 @@ if REMOTEPROC > > config IMX_REMOTEPROC > tristate "IMX6/7 remoteproc support" > - depends on SOC_IMX6SX || SOC_IMX7D > + depends on ARCH_MXC > help > Say y here to support iMX's remote processors (Cortex M4 > on iMX7D) via the remote processor framework. > -- > 2.17.1 > >
On Mon 03 Jun 16:46 PDT 2019, Fabio Estevam wrote: > Besides i.MX6SX and i.MX7D, there are other i.MX devices that contain > Cortex M4 and could make use of the imx remoteproc driver, such as > i.MX7ULP, i.MX8M, etc. > > Instead of adding new SoC entries in the Kconfig logic, make it > broader by using the more generic ARCH_MXC, which encompasses > all the 32-bit and 64-bit i.MX devices. > Patches applied with Oleksij's review. Thanks, Bjorn > Signed-off-by: Fabio Estevam <festevam@gmail.com> > --- > drivers/remoteproc/Kconfig | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/remoteproc/Kconfig b/drivers/remoteproc/Kconfig > index 18be41b8aa7e..0df301be6d9a 100644 > --- a/drivers/remoteproc/Kconfig > +++ b/drivers/remoteproc/Kconfig > @@ -16,7 +16,7 @@ if REMOTEPROC > > config IMX_REMOTEPROC > tristate "IMX6/7 remoteproc support" > - depends on SOC_IMX6SX || SOC_IMX7D > + depends on ARCH_MXC > help > Say y here to support iMX's remote processors (Cortex M4 > on iMX7D) via the remote processor framework. > -- > 2.17.1 >
diff --git a/drivers/remoteproc/Kconfig b/drivers/remoteproc/Kconfig index 18be41b8aa7e..0df301be6d9a 100644 --- a/drivers/remoteproc/Kconfig +++ b/drivers/remoteproc/Kconfig @@ -16,7 +16,7 @@ if REMOTEPROC config IMX_REMOTEPROC tristate "IMX6/7 remoteproc support" - depends on SOC_IMX6SX || SOC_IMX7D + depends on ARCH_MXC help Say y here to support iMX's remote processors (Cortex M4 on iMX7D) via the remote processor framework.
Besides i.MX6SX and i.MX7D, there are other i.MX devices that contain Cortex M4 and could make use of the imx remoteproc driver, such as i.MX7ULP, i.MX8M, etc. Instead of adding new SoC entries in the Kconfig logic, make it broader by using the more generic ARCH_MXC, which encompasses all the 32-bit and 64-bit i.MX devices. Signed-off-by: Fabio Estevam <festevam@gmail.com> --- drivers/remoteproc/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)