From: Shawn Guo <shawnguo@kernel.org>
To: Christoph Niedermaier <cniedermaier@dh-electronics.com>
Cc: linux-arm-kernel@lists.infradead.org,
Fabio Estevam <festevam@denx.de>, Marek Vasut <marex@denx.de>,
NXP Linux Team <linux-imx@nxp.com>,
kernel@dh-electronics.com
Subject: Re: [PATCH V7 2/7] ARM: dts: imx6q-dhcom: Rework of the DHCOM GPIO pinctrls
Date: Mon, 9 Aug 2021 15:31:08 +0800 [thread overview]
Message-ID: <20210809073107.GH30984@dragon> (raw)
In-Reply-To: <20210802141038.59663-2-cniedermaier@dh-electronics.com>
On Mon, Aug 02, 2021 at 04:10:33PM +0200, Christoph Niedermaier wrote:
> The function of each SoM pins is defined in the DHCOM standard [1] and
> subset of them is defined as GPIOs (pins A-W). To ensure the interchange-
> ability of the DHCOM SoMs, the function of the pins are fixed and cannot
> be changed. On board level the DHCOM GPIOs can be used associated with
> different blocks e.g. for interrupt or reset, but the function is always
> GPIO. If not used, they can be freely used in the user space.
>
> Therefore the whole configuration of SoM pins is made in the SoM DT.
> Defining the DHCOM GPIO pins as a separate pinctrl nodes makes moving a
> subset of them to an appropriate block pinctrl group easier on board level,
> since it is not necessary to have a large pinctrl hog group containing
> unrelated pinmux entries on board level. This also makes it easy to update
> the SoM DT without having to update all the board DTs too. If necessary it
> is also possible to change the electrical properties of the DHCOM GPIOs by
> overwriting the pinctrl on board level.
>
> [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>
> Cc: Shawn Guo <shawnguo@kernel.org>
> Cc: Fabio Estevam <festevam@denx.de>
> Cc: Marek Vasut <marex@denx.de>
> Cc: NXP Linux Team <linux-imx@nxp.com>
> Cc: kernel@dh-electronics.com
> To: linux-arm-kernel@lists.infradead.org
Applied, thanks!
_______________________________________________
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:[~2021-08-09 7:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 14:10 [PATCH V7 1/7] ARM: dts: imx6q-dhcom: Use 1G ethernet on the PDK2 board Christoph Niedermaier
2021-08-02 14:10 ` [PATCH V7 2/7] ARM: dts: imx6q-dhcom: Rework of the DHCOM GPIO pinctrls Christoph Niedermaier
2021-08-09 7:31 ` Shawn Guo [this message]
2021-08-02 14:10 ` [PATCH V7 3/7] ARM: dts: imx6q-dhcom: Rearrange of iomux Christoph Niedermaier
2021-08-09 7:34 ` Shawn Guo
2021-08-02 14:10 ` [PATCH V7 4/7] ARM: dts: imx6q-dhcom: Cleanup of the devicetrees Christoph Niedermaier
2021-08-09 7:35 ` Shawn Guo
2021-08-02 14:10 ` [PATCH V7 5/7] ARM: dts: imx6qdl-dhcom: Split SoC-independent parts of DHCOM SOM and PDK2 Christoph Niedermaier
2021-08-09 7:36 ` Shawn Guo
2021-08-02 14:10 ` [PATCH V7 6/7] ARM: dts: imx6qdl-dhcom: Add DHCOM based PicoITX board Christoph Niedermaier
2021-08-09 7:38 ` Shawn Guo
2021-08-02 14:10 ` [PATCH V7 7/7] ARM: dts: imx6qdl-dhcom: Add DHSOM based DRC02 board Christoph Niedermaier
2021-08-09 7:40 ` Shawn Guo
2021-08-09 7:30 ` [PATCH V7 1/7] ARM: dts: imx6q-dhcom: Use 1G ethernet on the PDK2 board 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=20210809073107.GH30984@dragon \
--to=shawnguo@kernel.org \
--cc=cniedermaier@dh-electronics.com \
--cc=festevam@denx.de \
--cc=kernel@dh-electronics.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=marex@denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.