[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <AM6PR04MB49660EE02F2C41C5320C1F2080B60@AM6PR04MB4966.eurprd04.prod.outlook.com>
Date: Wed, 20 May 2020 06:50:40 +0000
From: Aisheng Dong <aisheng.dong@....com>
To: Fabio Estevam <festevam@...il.com>, Peng Fan <peng.fan@....com>
CC: Shawn Guo <shawnguo@...nel.org>,
Fabio Estevam <fabio.estevam@....com>,
Sascha Hauer <kernel@...gutronix.de>,
Rob Herring <robh+dt@...nel.org>,
Stephen Boyd <sboyd@...nel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
dl-linux-imx <linux-imx@....com>,
Leonard Crestez <leonard.crestez@....com>,
Daniel Baluta <daniel.baluta@....com>,
Lucas Stach <l.stach@...gutronix.de>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>, linux-clk <linux-clk@...r.kernel.org>
Subject: RE: [PATCH 3/3] arm64: dts: imx8mp: add mu node
> From: Fabio Estevam <festevam@...il.com>
> Sent: Wednesday, May 20, 2020 11:07 AM
>
> Hi Peng,
>
> On Wed, May 20, 2020 at 12:01 AM Peng Fan <peng.fan@....com> wrote:
>
> > Nothing specific in i.MX8MP for the mu part, so do we really need add
> > "fsl,imx8mp-mu"?
>
> It is good practice to add a more specific option.
>
> Let's say in future a bug is found that affects imx8mp MU, then you could fix the
> MU driver and keep the dtb compatibility.
+1
Powered by blists - more mailing lists