From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id ADE04C433EF for ; Fri, 11 Feb 2022 03:39:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=NtemQWGJ/c+CLNtNphzciD7nT56UkIwUvLoVdGL6EOk=; b=WQJh13zdCXcQnh V0FmLcJxDdNaignQpOdxlxDBCAKytb8DiswnroDmrL61VVLU/drQFKH4ESDWh6TXc2LiAi2/NIL2j xUUSnh8STYlqw38jN/nEvzET7tAjdrQ3h9HUPHkZpLBCUDWQ7+SHYlb546zC3+oL54nCx4S4coMKF vMEVQNccLlYtvSjnRtrE0h3dHZi5LphCcbymA1yTZz+wv0d8bGx0LoofU/BOsXS45aPpCGfvVAoPh QSDLy0syUqqDgT805MsLFK1A0NiwiB1jO3PZPsEXUp5EsTZXGXPGye+9oTpTrkbYrN4WlD/3IybEi 5RIUzSOsvSU3e2MBuphQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nIMku-005azx-62; Fri, 11 Feb 2022 03:37:56 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nIMkq-005azd-9G for linux-arm-kernel@lists.infradead.org; Fri, 11 Feb 2022 03:37:53 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id AD56D6130C; Fri, 11 Feb 2022 03:37:50 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 93C8CC004E1; Fri, 11 Feb 2022 03:37:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1644550670; bh=cTC0oL8FxdRoFWpgWRcoS99Tl2LILqmYFNkHW7a4k2Y=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=k8U4QKPGRie6PhqDJjqzjM15V2Xv1Z3rDXAVkkNTaSN7KTKBefwXR7s5G5KZOrlDd gdrJphA2Cnk4jvNOB+LdGQcWvNj2nOTfI7hgQm2PfiqWAVYh3eGE2LuyIBUF5YBBK6 PZye2uKtM3iPNWFVatfwBW1yWrFLa+1MY0XZqQ8nVN6wAZs9ppSGxZGUjA49gMk9gf GyLHyCSU5bMvIb2CNCzeiGI/52wP0+lmDzBxuxhuKi5u+nBIMwLGia5Sf4Lbq1uoqc q7Rt+d1NmAwgnZrK0k9NQyz2Ad61cb203g/NSC482rgYZuj6QzeMumQE7BphKqliM4 SPL5YO1SJX41A== Date: Fri, 11 Feb 2022 11:37:43 +0800 From: Shawn Guo To: Alexander Stein Cc: Rob Herring , Sascha Hauer , Fabio Estevam , Pengutronix Kernel Team , NXP Linux Team , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 0/8] various imx6ul DT fixes Message-ID: <20220211033743.GI4909@dragon> References: <20220125135014.3041002-1-alexander.stein@ew.tq-group.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20220125135014.3041002-1-alexander.stein@ew.tq-group.com> User-Agent: Mutt/1.9.4 (2018-02-28) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220210_193752_411842_0DB479D2 X-CRM114-Status: GOOD ( 20.34 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Jan 25, 2022 at 02:50:06PM +0100, Alexander Stein wrote: > This patch set fixes several, but not all, dt_binding_check warnings. Some are > missing properties or their format, others address issues regarding to > compatible names. I only touched those where compatibles are stated in the yaml > bindings. > There are several imx6ul compatible names used by imx6ul.dtsi, but which are > not listed in the bindings. Namely: > * "fsl,imx6ul-gpt", "fsl,imx6sx-gpt" > * "fsl,imx6ul-tempmon", "fsl,imx6sx-tempmon" > * "fsl,imx6ul-gpc", "fsl,imx6q-gpc" > * "fsl,imx6ul-usdhc", "fsl,imx6sx-usdhc" > > Despite GPC, the others are apperently compatible to imx6sx. I'm not sure how > to fix the DTB check warning. Add the imx6ul compatible to bindings and drivers? Add the compatible to bindings, I would say. Shawn > Or change the .dtsi to use only the imx6sx compatible. > > The GPC on imx6ul apparently does only support power gating for ARM CPU, so > this would require actually a new compatible which supports only 1 domain. > > Alexander Stein (8): > ARM: dts: imx6ul: add missing properties for sram > ARM: dts: imx6ul: change operating-points to uint32-matrix > ARM: dts: imx6ul: fix keypad compatible > ARM: dts: imx6ul: fix adc node compatible > ARM: dts: imx6ul: remove unsupported adc property > ARM: dts: imx6ul: fix csi node compatible > ARM: dts: imx6ul: fix lcdif node compatible > ARM: dts: imx6ul: fix qspi node compatible > > arch/arm/boot/dts/imx6ul.dtsi | 36 +++++++++++++++++------------------ > 1 file changed, 18 insertions(+), 18 deletions(-) > > -- > 2.25.1 > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel