From: Mathieu Othacehe <othacehe@gnu.org>
To: Stefan Wahren <wahrenst@gmx.net>
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>,
Christoph Stoidner <c.stoidner@phytec.de>,
Wadim Egorov <w.egorov@phytec.de>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/2] arm64: dts: imx93: Add phyBOARD-Segin-i.MX93 support
Date: Mon, 22 Jan 2024 10:38:36 +0100 [thread overview]
Message-ID: <87jzo1emhv.fsf@gnu.org> (raw)
In-Reply-To: <282689a1-a189-4320-9d70-c6d38dc56d9d@gmx.net> (Stefan Wahren's message of "Fri, 19 Jan 2024 11:11:39 +0100")
Hello Stefan,
> According to the documentation there are GPIOs accessible. Those on the
> expansion header X16 could be named via gpio-line-name this makes it
> easier to access via libgpiod. Also there seems to be LEDs and switches
> on the phyBOARD.
I will add gpio-line-name for the two accessible GPIOs on X16 that are
not mapped to specific functions. I will also add the heartbeat LED that
is located on the SoM. Regarding the two switches on the phyBOARD, they
reset the CPU and the board so I am not sure that they can have an entry
in the device tree.
Thanks,
Mathieu
next prev parent reply other threads:[~2024-01-22 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 9:28 [PATCH v3 0/2] Add phyBOARD-Segin-i.MX93 support Mathieu Othacehe
2024-01-19 9:28 ` [PATCH v3 1/2] dt-bindings: arm: fsl: Add phyBOARD-Segin-i.MX93 Mathieu Othacehe
2024-01-19 16:35 ` Conor Dooley
2024-01-19 9:28 ` [PATCH v3 2/2] arm64: dts: imx93: Add phyBOARD-Segin-i.MX93 support Mathieu Othacehe
2024-01-19 10:11 ` Stefan Wahren
2024-01-22 9:38 ` Mathieu Othacehe [this message]
2024-01-22 2:42 ` Wadim Egorov
2024-01-22 7:44 ` Mathieu Othacehe
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=87jzo1emhv.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).