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 E5A6AC00140 for ; Fri, 12 Aug 2022 17:42:32 +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:From:References:Cc:To: Subject:MIME-Version:Date:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=wyfrVs6DRSiC7FGAnZTiVZ+QtYeg+gzJbPbK7Bg65dU=; b=3/Ra52YZA0QOj4 3ntFiS1xaYzucwWtEHYGwnC+zkCqoslgYZi5iS03fIPoiLyICM6QlIGrl5i1HsbcCdSJZE6XAHKm1 KNXPbkEDO15yJ+AV8vgTXCvVcMY7AVx49i139wViAJ3tthrM6+lpRvFCozs5aHBMVa+ccjHsqWQNO S9jZUNrDk1ECgW4MHVK7m1ltUZQUZi+Oqg/g9CMngu8Avz9uWiA2OIDXJyCAw3PW1q6V3kWKAh798 HyJybwCh0F97za3evkVC224eKJoaJVZ787Wp3S5H8JaVdf9QMjO1hb7iR+eOirsHY6l/ucQr/B0jN JYffaXEVdMOSR1b+QFfA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oMYf0-00Be2t-NJ; Fri, 12 Aug 2022 17:41:27 +0000 Received: from mail-lf1-x12c.google.com ([2a00:1450:4864:20::12c]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oMYeP-00BdPe-7k for linux-arm-kernel@lists.infradead.org; Fri, 12 Aug 2022 17:40:52 +0000 Received: by mail-lf1-x12c.google.com with SMTP id z6so2237027lfu.9 for ; Fri, 12 Aug 2022 10:40:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc; bh=KtLfPjByJa6q8FlTlUeWe/aEeZBvhai424SUeEWrjNw=; b=WiYvUWDtdP2T33THfoYXJr8aqe3Vztx4aPKwH0K/t5St4XZ1By0hd5EGuwad/kEzhg qu9G4zdBw4tClRvKHpDMMd3VRzCybF/iom3GzyoxBK+nP0ai3NwzsM+SzZamThs59I6b WI2ExxrC70iOB7PciV5GC8Epcm6eG+voIYkwTpjRyBS5nDBrG4vJygxRUg2v6E66NvUt Hq5O1O6BHjFzFKMLXPtFeplzMJu2JDLzVi25WCNnRHpXom1Rbs/xqhxxSenYHhFUEglO yl6bESpuWVaaY3qf9mxX70z1sP1tHRJg8UpuLwKEQI1EjCGEtZ9gFV+HFnAchatTEpth WG4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc; bh=KtLfPjByJa6q8FlTlUeWe/aEeZBvhai424SUeEWrjNw=; b=2rTx0B+MMc0+N1lmm7yLr067lmOM2PImO5DXtPrZAcCWlk0AlixvDa2znsRnPnjCAU vxDo04s2gF2VjLstLdWyhbQLysJgedXEsJPClNMmxnYqd8CFMin5J/Dz4iYNNUJquvjI x/ep4XphFqo60gqEFDuOhEwu3ng0AaGIwN5tAb6Fj8aeIQHq8V9UOUizt46BzB0DF4GJ iPuU1QD4j9WTmfjTvqUS49L+/Ksy51eObX3xTHL/FCgEC9j7M1bSXAcFUBg5ckr1/a5W fVk21X6j2EjOfA5o3Lf5PESljibo8Mpky76E+lm4Y0+LaZF/uNYSpEB+vQLUdY1m3F4O LQGQ== X-Gm-Message-State: ACgBeo1oDcXSdBBILI+ULIKyk25D/8zcvYxurGx/+DcHTdvRjGdNBmG9 mSz8hLkhMR/6OQgXI1gwf4g6z4meG9QNbAz7 X-Google-Smtp-Source: AA6agR4gKsnQ7z6AOnP2EMb+hBAdH/VJcnRq3ePnpWKzPgo5UA0FU3J8EYlFfa5NuXc7fXHSbkN+eA== X-Received: by 2002:a05:6512:3ba8:b0:48a:f8e2:8ee8 with SMTP id g40-20020a0565123ba800b0048af8e28ee8mr1502276lfv.104.1660326044221; Fri, 12 Aug 2022 10:40:44 -0700 (PDT) Received: from [192.168.1.39] ([83.146.140.105]) by smtp.gmail.com with ESMTPSA id t12-20020a056512068c00b0048b26a0d760sm276283lfe.229.2022.08.12.10.40.42 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 12 Aug 2022 10:40:43 -0700 (PDT) Message-ID: Date: Fri, 12 Aug 2022 20:40:39 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0 Subject: Re: [PATCH] ARM: dts: imx6qdl-dhcom: Move IPU iomux node from PDK2 to SoM file Content-Language: en-US To: Marek Vasut , Christoph Niedermaier , linux-arm-kernel@lists.infradead.org Cc: Shawn Guo , Fabio Estevam , NXP Linux Team , kernel@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> From: Krzysztof Kozlowski In-Reply-To: <143da4b5-56b8-4752-2716-7df0720bf88d@denx.de> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220812_104049_365027_5042E79A X-CRM114-Status: GOOD ( 22.13 ) 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 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. Best regards, Krzysztof _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel