Received: by 2002:a25:86ce:0:0:0:0:0 with SMTP id y14csp488320ybm; Wed, 22 May 2019 06:43:36 -0700 (PDT) X-Google-Smtp-Source: APXvYqx5jDKttIEgKDBnL7GA60xKuxNUfppIU4h3cmCrC14pssLe8TeI1r1qO3m2JS2EexoD/c6m X-Received: by 2002:a63:1354:: with SMTP id 20mr88530208pgt.356.1558532616039; Wed, 22 May 2019 06:43:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558532616; cv=none; d=google.com; s=arc-20160816; b=epNlVXEluurPJwuHcrjyARvzt12rvh4504KXUIyupXG5HoVapdo5A4uJe5tCoJByBH OCMf4uhesTpsCf+3G+Cy5HEfDnKnjzHZysXj3m5biozTwDcqCFRTZtATTnkPHlIz+E0Q AKDyTwhGI7bXYru6xwygltLg2z92XjfkFmrcuaP/wkqVUVL/fd/ZGwjqdu4mW0ohobuo fkCCA67ngl4aplk/c0aZ9sINnTWaAdyRxxdH89b7TSkcFKW4SN8g7+jGuuptyy3WLAcU 5QEN8pGDtBsdbsY8vdy5WuKIIIWuc28J+rC89DaPWen2Az5BHYHiZYoOt0uNHsgG824H lyRw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id; bh=vngcfN9kZ/TFITK4KZs73hnwL7V/rcS98rYkDik474Y=; b=Q7ywTR65Mi/xY+CtK9hW0C4ibNDhXOO6t4h2bjahIOg67ELdh10zEAEOOY/CUVQZQ8 +ExPpkT0hS1Q/KoZMVhcWgtKQZEnV/opl/ZnE6BNJVdM+zYrJm54PDEynN0bPkrK0CM6 uXbe5fYMFtKyLvke9Dy1Rg8kD480aeDfRPT4UETP8LTkCAA6nEVwAB5KtfTyL2WmKGyk mmpBpZQFBEaO8oiB0W5+nGhy/ssEez+laRFzFnuA0wGvJqsD30fbIYnowBS9y3/SojSq 0InKvJUWsCDWYy9yxmpJbL/KxH3mVAtUJnuJAwGlSOB1yI7qtkJmfsmp8hJjz23jKy07 C4sQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u16si14806354plq.75.2019.05.22.06.43.20; Wed, 22 May 2019 06:43:36 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729412AbfEVNkz (ORCPT + 99 others); Wed, 22 May 2019 09:40:55 -0400 Received: from metis.ext.pengutronix.de ([85.220.165.71]:40677 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729071AbfEVNkz (ORCPT ); Wed, 22 May 2019 09:40:55 -0400 Received: from kresse.hi.pengutronix.de ([2001:67c:670:100:1d::2a]) by metis.ext.pengutronix.de with esmtp (Exim 4.89) (envelope-from ) id 1hTRUB-0002PK-69; Wed, 22 May 2019 15:40:51 +0200 Message-ID: <1558532450.2624.44.camel@pengutronix.de> Subject: Re: [RFC PATCH] soc: imx: Try harder to get imq8mq SoC revisions From: Lucas Stach To: Leonard Crestez , Guido =?ISO-8859-1?Q?G=FCnther?= , Abel Vesa Cc: Jacky Bai , Anson Huang , Fabio Estevam , Sascha Hauer , "linux-kernel@vger.kernel.org" , dl-linux-imx , Pengutronix Kernel Team , Shawn Guo , "linux-arm-kernel@lists.infradead.org" Date: Wed, 22 May 2019 15:40:50 +0200 In-Reply-To: References: <20190522131304.GA5692@bogon.m.sigxcpu.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6-1+deb9u1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-SA-Exim-Connect-IP: 2001:67c:670:100:1d::2a X-SA-Exim-Mail-From: l.stach@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Mittwoch, den 22.05.2019, 13:30 +0000 schrieb Leonard Crestez: > On 22.05.2019 16:13, Guido Günther wrote: > > Subject: Re: [RFC PATCH] soc: imx: Try harder to get imq8mq SoC revisions > > Fixed subject > > > On Wed, May 08, 2019 at 02:40:18PM +0200, Guido Günther wrote: > > > Thanks for your comments. Let's try s.th. different then: identify by > > > bootrom, ocotop and anatop and fall back to ATF afterwards (I'll split > > > out the DT part and add binding docs if this makes sense). I'm also > > > happy to drop the whole ATF logic until mailine ATF catched up: > > > > > > The mainline ATF doesn't currently support the FSL_SIP_GET_SOC_INFO call > > > nor does it have the code to identify different imx8mq SOC revisions so > > > mimic what NXPs ATF does here. > > > > Does this makes sense? If so I'll send this out as a series. > > Mainline ATF has recently caught up: > > https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/tree/plat/imx/imx8m/imx8mq/imx8mq_bl31_setup.c#n52 > > > > As a fallback use ATF so we can identify new revisions once it gains > > > support or when using NXPs ATF. > > > > I'm also fine with dropping the ATF part if we don't want to depend on > > it in mainline. > > Linux arm64 depends on ATF to implement power management via PSCI:  > hotplug cpuidle and suspend. > > It is not clear why Linux would avoid other services and insist on  > reimplementing hardware workarounds. I fully agree. We should not duplicate functionality between ATF and Linux kernel. If the mainline ATF provides the facilities to do the SoC identification the kernel should use them as the sole source to get this information. Regards, Lucas