From: Francesco Dolcini <francesco@dolcini.it>
To: Nishanth Menon <nm@ti.com>
Cc: Parth Pancholi <parth105105@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Francesco Dolcini <francesco.dolcini@toradex.com>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Parth Pancholi <parth.pancholi@toradex.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Tero Kristo <kristo@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH v1] arm64: dts: k3-am625-verdin: enable Verdin UART2
Date: Thu, 23 Nov 2023 09:58:33 +0100 [thread overview]
Message-ID: <ZV8UOTSTl6spUXt5@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <20231123071235.omgxs3ixnojpkfvu@greeter>
Hello Nishanth,
On Thu, Nov 23, 2023 at 01:12:35AM -0600, Nishanth Menon wrote:
> On 17:04-20231121, Parth Pancholi wrote:
> > /* Verdin UART_2 */
> > &wkup_uart0 {
> > - /* FIXME: WKUP UART0 is used by DM firmware */
> > - status = "reserved";
> > + status = "okay";
> > };
> > --
> > 2.34.1
> >
>
> Do the &pinctrl_wkup_uart0 in verdin.dtsi hold good through these
> variants?
Yes.
Let me add a little bit of context.
In general the way the Verdin AM62 (and Toradex SOM) is designed is that
we have a standard pinmuxing on the module edge connector (SODIMM) and
normally the carrier board that is mated with just implements it.
It's absolutely possible to redefine it all, but to maximize
compatibility across the family what we do at most is to reconfigure
some pins as GPIO.
Francesco
next prev parent reply other threads:[~2023-11-23 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 16:04 [PATCH v1] arm64: dts: k3-am625-verdin: enable Verdin UART2 Parth Pancholi
2023-11-23 7:12 ` Nishanth Menon
2023-11-23 8:58 ` Francesco Dolcini [this message]
2023-11-23 9:00 ` Francesco Dolcini
2023-12-04 21:13 ` Nishanth Menon
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=ZV8UOTSTl6spUXt5@francesco-nb.int.toradex.com \
--to=francesco@dolcini.it \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=francesco.dolcini@toradex.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=nm@ti.com \
--cc=parth.pancholi@toradex.com \
--cc=parth105105@gmail.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
/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).