From: Mathieu Othacehe <othacehe@gnu.org>
To: Wadim Egorov <w.egorov@phytec.de>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Li Yang <leoyang.li@nxp.com>,
Primoz Fiser <primoz.fiser@norik.com>,
Stefan Wahren <wahrenst@gmx.net>,
Christoph Stoidner <c.stoidner@phytec.de>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 3/3] arm64: dts: imx93: Add phyBOARD-Segin-i.MX93 support
Date: Tue, 23 Jan 2024 08:44:55 +0100 [thread overview]
Message-ID: <87ttn45w94.fsf@gnu.org> (raw)
In-Reply-To: <537266fe-0bf7-4208-a9f3-ae27f462c6ed@phytec.de> (Wadim Egorov's message of "Tue, 23 Jan 2024 07:11:27 +0100")
Hey Wadim,
> You are doing more than you describing in your changes log.
> Here you are forcing a gpio-only functionality for the X16 header. But the
> pins we route down to the X16 expansion connector can be also used
> differently.
> Typically we provide device tree overlays for different use cases on this
> expansion connectors.
Adding those GPIOs on X16 was a suggestion from Stefan back in v3. I
must say that it is quite convenient as a user to be able to interact
with gpiolib on some GPIOs on the eval board.
Would it be a possibility to change the muxing of those two pins in the
overlays if the need arises?
> Maybe this comment was lost, but I asked to move the dts-v1 tag into the
> carrier board device tree.
Missed that, sorry.
Thanks,
Mathieu
next prev parent reply other threads:[~2024-01-23 7:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 9:53 [PATCH v4 0/3] Add phyBOARD-Segin-i.MX93 support Mathieu Othacehe
2024-01-22 9:53 ` [PATCH v4 1/3] dt-bindings: arm: fsl: Add phyBOARD-Segin-i.MX93 Mathieu Othacehe
2024-01-22 9:53 ` [PATCH v4 2/3] dt-bindings: gpio: gpio-vf610: add gpio-line-names Mathieu Othacehe
2024-01-22 12:32 ` Stefan Wahren
2024-01-22 18:01 ` Conor Dooley
2024-01-22 9:53 ` [PATCH v4 3/3] arm64: dts: imx93: Add phyBOARD-Segin-i.MX93 support Mathieu Othacehe
2024-01-23 6:11 ` Wadim Egorov
2024-01-23 7:42 ` Stefan Wahren
2024-01-23 8:25 ` Wadim Egorov
2024-01-23 10:21 ` Stefan Wahren
2024-01-24 5:13 ` Wadim Egorov
2024-01-24 11:39 ` Stefan Wahren
2024-01-24 13:48 ` Mathieu Othacehe
2024-01-24 17:28 ` Stefan Wahren
2024-01-25 6:05 ` Wadim Egorov
2024-01-25 6:12 ` Primoz Fiser
2024-01-25 7:41 ` Stefan Wahren
2024-01-23 7:44 ` Mathieu Othacehe [this message]
2024-01-23 8:34 ` Primoz Fiser
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=87ttn45w94.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=c.stoidner@phytec.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=primoz.fiser@norik.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=w.egorov@phytec.de \
--cc=wahrenst@gmx.net \
/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).