Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Leonard Crestez <leonard.crestez@nxp.com>
To:     =?iso-8859-1?Q?Guido_G=FCnther?= <agx@sigxcpu.org>,
        Abel Vesa <abel.vesa@nxp.com>,
        Lucas Stach <l.stach@pengutronix.de>
CC:     Jacky Bai <ping.bai@nxp.com>, Anson Huang <anson.huang@nxp.com>,
        Fabio Estevam <festevam@gmail.com>,
        Sascha Hauer <s.hauer@pengutronix.de>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        dl-linux-imx <linux-imx@nxp.com>,
        Pengutronix Kernel Team <kernel@pengutronix.de>,
        Shawn Guo <shawnguo@kernel.org>,
        "linux-arm-kernel@lists.infradead.org" 
        <linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC PATCH] soc: imx: Try harder to get imq8mq SoC revisions
Thread-Topic: [RFC PATCH] soc: imx: Try harder to get imq8mq SoC revisions
Thread-Index: AQHVEKAZarE5OuVeAEC7HAm8UuJafQ==
Date:   Wed, 22 May 2019 13:30:54 +0000
Message-ID: <AM0PR04MB6434B72679CD26C22FFB420BEE000@AM0PR04MB6434.eurprd04.prod.outlook.com>
References: <20190522131304.GA5692@bogon.m.sigxcpu.org>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: nxp.com does not designate
 permitted sender hosts)
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: fd638ae9-b715-46ad-ab60-08d6deb9b720
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 May 2019 13:30:54.1471
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 686ea1d3-bc2b-4c6f-a92c-d99c5c301635
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR04MB4404
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 22.05.2019 16:13, Guido G=FCnther wrote:=0A=
> Subject: Re: [RFC PATCH] soc: imx: Try harder to get imq8mq SoC revisions=
=0A=
=0A=
Fixed subject=0A=
=0A=
> On Wed, May 08, 2019 at 02:40:18PM +0200, Guido G=FCnther wrote:=0A=
>> Thanks for your comments. Let's try s.th. different then: identify by=0A=
>> bootrom, ocotop and anatop and fall back to ATF afterwards (I'll split=
=0A=
>> out the DT part and add binding docs if this makes sense). I'm also=0A=
>> happy to drop the whole ATF logic until mailine ATF catched up:=0A=
>>=0A=
>> The mainline ATF doesn't currently support the FSL_SIP_GET_SOC_INFO call=
=0A=
>> nor does it have the code to identify different imx8mq SOC revisions so=
=0A=
>> mimic what NXPs ATF does here.=0A=
> =0A=
> Does this makes sense? If so I'll send this out as a series.=0A=
=0A=
Mainline ATF has recently caught up:=0A=
=0A=
https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/tree/plat/imx/i=
mx8m/imx8mq/imx8mq_bl31_setup.c#n52=0A=
=0A=
>> As a fallback use ATF so we can identify new revisions once it gains=0A=
>> support or when using NXPs ATF.=0A=
> =0A=
> I'm also fine with dropping the ATF part if we don't want to depend on=0A=
> it in mainline.=0A=
=0A=
Linux arm64 depends on ATF to implement power management via PSCI: =0A=
hotplug cpuidle and suspend.=0A=
=0A=
It is not clear why Linux would avoid other services and insist on =0A=
reimplementing hardware workarounds.=0A=
=0A=
--=0A=
Regards,=0A=
Leonard=0A=