From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: ohad@wizery.com, o.rempel@pengutronix.de,
linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH 1/2] remoteproc: imx: Broaden the Kconfig selection logic
Date: Mon, 3 Jun 2019 22:01:21 -0700 [thread overview]
Message-ID: <20190604050121.GA23094@builder> (raw)
In-Reply-To: <20190603234628.10924-1-festevam@gmail.com>
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
>
prev parent reply other threads:[~2019-06-04 5:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 23:46 [PATCH 1/2] remoteproc: imx: Broaden the Kconfig selection logic Fabio Estevam
2019-06-03 23:46 ` [PATCH 2/2] remoteproc: imx: Fix typo in "failed" Fabio Estevam
2019-06-04 4:19 ` Oleksij Rempel
2019-06-04 4:18 ` [PATCH 1/2] remoteproc: imx: Broaden the Kconfig selection logic Oleksij Rempel
2019-06-04 5:01 ` Bjorn Andersson [this message]
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=20190604050121.GA23094@builder \
--to=bjorn.andersson@linaro.org \
--cc=festevam@gmail.com \
--cc=linux-remoteproc@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=ohad@wizery.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: link
Be 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.