From: Shawn Guo <shawnguo@kernel.org>
To: Anson Huang <Anson.Huang@nxp.com>
Cc: aisheng.dong@nxp.com, peng.fan@nxp.com, geert+renesas@glider.be,
will@kernel.org, catalin.marinas@arm.com, s.hauer@pengutronix.de,
linux-kernel@vger.kernel.org, daniel.baluta@nxp.com,
bjorn.andersson@linaro.org, franck.lenormand@nxp.com,
vkoul@kernel.org, arnd@arndb.de, krzk@kernel.org,
kernel@pengutronix.de, olof@lixom.net, leoyang.li@nxp.com,
festevam@gmail.com, linux-arm-kernel@lists.infradead.org,
Linux-imx@nxp.com
Subject: Re: [PATCH V3] firmware: imx: Move i.MX SCU soc driver into imx firmware folder
Date: Mon, 13 Jul 2020 10:02:29 +0800 [thread overview]
Message-ID: <20200713020228.GT21277@dragon> (raw)
In-Reply-To: <1593119647-30951-1-git-send-email-Anson.Huang@nxp.com>
On Fri, Jun 26, 2020 at 05:14:07AM +0800, Anson Huang wrote:
> The i.MX SCU soc driver depends on SCU firmware driver, so it has to
> use platform driver model for proper defer probe operation, since
> it has no device binding in DT file, a simple platform device is
> created together inside the platform driver. To make it more clean,
> we can just move the entire SCU soc driver into imx firmware folder
> and initialized by i.MX SCU firmware driver.
>
> Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
Applied, thanks.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-07-13 2:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 21:14 [PATCH V3] firmware: imx: Move i.MX SCU soc driver into imx firmware folder Anson Huang
2020-06-29 2:49 ` Aisheng Dong
2020-07-13 2:02 ` Shawn Guo [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=20200713020228.GT21277@dragon \
--to=shawnguo@kernel.org \
--cc=Anson.Huang@nxp.com \
--cc=Linux-imx@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=daniel.baluta@nxp.com \
--cc=festevam@gmail.com \
--cc=franck.lenormand@nxp.com \
--cc=geert+renesas@glider.be \
--cc=kernel@pengutronix.de \
--cc=krzk@kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=vkoul@kernel.org \
--cc=will@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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).