From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Christoph Niedermaier <cniedermaier@dh-electronics.com>,
linux-arm-kernel@lists.infradead.org
Cc: Shawn Guo <shawnguo@kernel.org>,
Fabio Estevam <festevam@gmail.com>, Marek Vasut <marex@denx.de>,
NXP Linux Team <linux-imx@nxp.com>,
kernel@dh-electronics.com
Subject: Re: [PATCH V2] ARM: dts: imx6qdl-dhcom: Move IPU iomux node from PDK2 to SoM file
Date: Wed, 17 Aug 2022 10:01:22 +0300 [thread overview]
Message-ID: <ddc7b625-f68b-9c4e-a2c9-ac2e0a575ede@linaro.org> (raw)
In-Reply-To: <20220816124133.41023-1-cniedermaier@dh-electronics.com>
On 16/08/2022 15:41, Christoph Niedermaier wrote:
> The SoM itself provides the display interface, see [1] page 20.
> 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 them into the SoM DTSI.
>
> [1] https://wiki.dh-electronics.com/images/2/2e/DOC_DHCOM-Standard-Specification_R01_2016-11-17.pdf
>
> Signed-off-by: Christoph Niedermaier <cniedermaier@dh-electronics.com>
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-08-17 7:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 12:41 [PATCH V2] ARM: dts: imx6qdl-dhcom: Move IPU iomux node from PDK2 to SoM file Christoph Niedermaier
2022-08-17 7:01 ` Krzysztof Kozlowski [this message]
2022-08-22 2:37 ` Shawn Guo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ddc7b625-f68b-9c4e-a2c9-ac2e0a575ede@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=cniedermaier@dh-electronics.com \
--cc=festevam@gmail.com \
--cc=kernel@dh-electronics.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=marex@denx.de \
--cc=shawnguo@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).