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 53A37C25B0E for ; Tue, 16 Aug 2022 12:35:28 +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:MIME-Version:In-Reply-To:References: Message-ID:Date:Subject:CC:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=mZBSwepwBb6lu9u0yG9Do58jKMy+2DojY7XwkCT4SDs=; b=m8WlQDcmaDRd/d kSKDAT30KnRlutiP55cMNSNG+NtPnDSoYOYrFkCuDw2vN2DtvFomXhQhZxAS2fYJnTsVd8d43gO+7 McOJ+V5jAC05wi7sIBn/PcBzLjhpHJe9WVqLfnf987Q+MG6RAsbXJ5tv3bMCHpfqD1zhoLzCG0twd BDptHz/MgawScAGTD/uyqGTwp5YcUeVY+Rz5JDybOQ56flJ52ezvDiPkmGYxra3ElRzDBQWTSK4OZ c8HGXzKxOD/9kPedEmSNytx5aHlluKRQiC+K9QqnQTO12mtLh2g5wRNqCkN74hSr5vW2Kg4ePYGzO +tgYqSG+oA+tf5/ye7iQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oNvlt-002Kv3-B7; Tue, 16 Aug 2022 12:34:13 +0000 Received: from mx3.securetransport.de ([116.203.31.6]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oNvlp-002KrN-Ex for linux-arm-kernel@lists.infradead.org; Tue, 16 Aug 2022 12:34:11 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dh-electronics.com; s=dhelectronicscom; t=1660653214; bh=C1zTRuVFXtyP4gfS/vKBZA7K/TBllo971xEahCV48h0=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=w4GhNKLhn8qbrm4u6TQx87+cDBrpuWzCJYkWnqvQo8H6t8lv4jlHZVM8P53FIX0u5 VvpCgS9Hm1D46TUfIxOTBDZDhuUOomLaIr5qXQ0NDNVmPDzVuXut9UWN3prn7ni4wd 4+sobELUQ5y6hEyV8U5P2s4eMfOU6aFvLo/tK1HFsQtlNTzlUHBC5EQXd1H/tu2TYd jr8SYpiCV72EUnBNswpO00l46cDvCvZXqdXQVZkAfJiS9uL8RRn2yZgkCUXhN3v9mG aFW4P32xpX1xSlCpvfR7QnFizWVaMebbc3Sgeh7V91Bb7S3I7cp39drlanqBR/LGMO zv91JhFUHFnVg== X-secureTransport-forwarded: yes From: Christoph Niedermaier Complaints-To: abuse@cubewerk.de To: Krzysztof Kozlowski , Marek Vasut , "linux-arm-kernel@lists.infradead.org" CC: Shawn Guo , Fabio Estevam , "NXP Linux Team" , kernel Subject: RE: [PATCH] ARM: dts: imx6qdl-dhcom: Move IPU iomux node from PDK2 to SoM file Thread-Topic: [PATCH] ARM: dts: imx6qdl-dhcom: Move IPU iomux node from PDK2 to SoM file Thread-Index: AQHYrkOUWaJ8ARgMQEKb+JMk9bzGRK2rH/aAgABDgICAAAPBgIAGFFBQ Date: Tue, 16 Aug 2022 12:33:25 +0000 Message-ID: <76d76020d72f4682b21e4c5c1cc50bed@dh-electronics.com> References: <20220812120337.5580-1-cniedermaier@dh-electronics.com> <141a5b76-7164-6744-9c83-333b3d2d3313@linaro.org> <143da4b5-56b8-4752-2716-7df0720bf88d@denx.de> In-Reply-To: Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220816_053409_781281_724E182A X-CRM114-Status: GOOD ( 15.47 ) 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 From: Krzysztof Kozlowski [mailto:krzysztof.kozlowski@linaro.org] Sent: Friday, August 12, 2022 7:41 PM > On 12/08/2022 20:27, Marek Vasut wrote: >> On 8/12/22 15:25, Krzysztof Kozlowski wrote: >>> On 12/08/2022 15:03, Christoph Niedermaier wrote: >>>> To have a variant (imx6dl/imx6q) independent access to the IPU >>>> iomux node move them to the SoM file. >>> >>> There is no such variant using them, so the "possibility" is not a >>> reason for such change. The change by itself, without proper users, does >>> not make any sense. >> >> I think it does make sense to move the IPUv3 RGB/DPI interface pinmux >> description from PDK2 carrier board DT into the common SoM DTSI, but for >> a different reason entirely. >> >> The SoM specification states there is such an interface on the SoM pins: >> >> " >> https://wiki.dh-electronics.com/images/2/2e/DOC_DHCOM-Standard-Specification_R01_2016-11-17.pdf >> >> Page 20 >> >> 5.1.14 RGB Display >> The DHCOM standard provides a parallel 24-bit RGB interface for driving >> displays. >> " >> >> And from what I can tell, for a carrier board to be compatible with the >> SoM standard above, those pins have to be used as the RGB/DPI interface >> or not used at all. >> >> So rather than duplicate the pinmux settings in every carrier board DT, >> better move/deduplicate them into the SoM DTSI. >> >> But it seems the commit message should be updated to reflect that. >> >> btw. there are also downstream DTOs which do reference that pinmux >> settings label, but maybe those DTOs are not really interesting with >> regards to this specific change. > > That's much better reasoning and it makes sense. I will improve the commit message in V2. Regards, Christoph _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel