From: Sascha Hauer <s.hauer@pengutronix.de>
To: "A.s. Dong" <aisheng.dong@nxp.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"dongas86@gmail.com" <dongas86@gmail.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will.deacon@arm.com" <will.deacon@arm.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support
Date: Mon, 15 Oct 2018 10:27:51 +0200 [thread overview]
Message-ID: <20181015082751.ytuleg67p5pgtnov@pengutronix.de> (raw)
In-Reply-To: <AM0PR04MB42117867A50BB18D8127BE8080FD0@AM0PR04MB4211.eurprd04.prod.outlook.com>
On Mon, Oct 15, 2018 at 08:08:31AM +0000, A.s. Dong wrote:
> > > + imx8qx-pm {
> > > + compatible = "fsl,scu-pd";
> >
> > I missed this earlier, but there should be a i.MX8qp specific compatible as the
> > SCU API might change for future SoCs.
> >
>
> We still do not see that requirement up till now. Not sure if it would be
> possible in the future. I see low possibilities.
> SCU IPC is designed to be generic to all MX8 SCU firmwares.
And i.MX9? i.MX10?
> Even it changes, SCU firmware version control may helps.
It's not the first time that the position of the version field changes with
a newer version.
>
> > > + compatible = "fsl,imx7ulp-lpuart";
> > > + compatible = "fsl,imx7ulp-lpi2c";
> > > + compatible = "fsl,imx7d-usdhc";
> >
> > All these lack the most specific imx8qp compatible.
> >
>
> Adding them requires binding doc update as well.
> S I suppose they could be added later when the QXP specific features are
> really supported by the drivers.
> Do you think it's okay?
Newer Kernels should work with older device trees, so once you roll out
these compatibles it's too late already.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2018-10-15 8:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1539527419-23613-1-git-send-email-aisheng.dong@nxp.com>
2018-10-14 14:34 ` [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support A.s. Dong
2018-10-14 23:13 ` Fabio Estevam
2018-10-15 6:27 ` Daniel Baluta
2018-10-15 7:30 ` Leonard Crestez
2018-10-15 9:29 ` A.s. Dong
2018-10-15 7:57 ` A.s. Dong
2018-10-18 0:51 ` Rob Herring
2018-10-18 2:32 ` A.s. Dong
2018-10-15 6:58 ` Sascha Hauer
2018-10-15 8:08 ` A.s. Dong
2018-10-15 8:27 ` Sascha Hauer [this message]
2018-10-15 9:03 ` A.s. Dong
2018-10-15 9:40 ` Sascha Hauer
2018-10-15 16:09 ` A.s. Dong
2018-10-16 7:08 ` Sascha Hauer
2018-10-14 14:34 ` [PATCH V2 3/4] arm64: dts: imx: add imx8qxp mek support A.s. Dong
2018-10-15 7:01 ` Sascha Hauer
2018-10-15 8:40 ` A.s. Dong
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=20181015082751.ytuleg67p5pgtnov@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=aisheng.dong@nxp.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dongas86@gmail.com \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=will.deacon@arm.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 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).