From: Konstantin Kletschke <konstantin.kletschke@inside-m2m.de>
To: Sascha Hauer <sha@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Compiled in boot environment and dtbo files
Date: Tue, 22 Jun 2021 12:40:25 +0200 [thread overview]
Message-ID: <1D32E771-3167-453F-AF94-606F610CEEC2@inside-m2m.de> (raw)
In-Reply-To: <D71BFF12-5C4D-4C41-B15F-2D53376F5669@inside-m2m.de>
[-- Attachment #1.1: Type: text/plain, Size: 1729 bytes --]
I got the uart1 and uart4 available on boot after I changed the appropiate dtsi in this way:
--- arch/arm/boot/dts/am335x-bone-common.dtsi_ORIG 2021-01-29 15:08:15.085080693 +0100
+++ arch/arm/boot/dts/am335x-bone-common.dtsi 2021-06-22 11:26:48.197115876 +0200
@@ -96,6 +96,20 @@
>;
};
+ uart1_pins: pinmux_uart1_pins {
+ pinctrl-single,pins = <
+ AM33XX_PADCONF(AM335X_PIN_UART1_RXD, PIN_INPUT_PULLUP, MUX_MODE0)
+ AM33XX_PADCONF(AM335X_PIN_UART1_TXD, PIN_OUTPUT_PULLDOWN, MUX_MODE0)
+ >;
+ };
+
+ uart4_pins: pinmux_uart4_pins {
+ pinctrl-single,pins = <
+ AM33XX_PADCONF(AM335X_PIN_GPMC_WAIT0, PIN_INPUT_PULLUP, MUX_MODE6) /* (T17) gpmc_wait0.uart4_rxd */
+ AM33XX_PADCONF(AM335X_PIN_GPMC_WPN, PIN_OUTPUT_PULLDOWN, MUX_MODE6) /* (U17) gpmc_wpn.uart4_txd */
+ >;
+ };
+
clkout2_pin: pinmux_clkout2_pin {
pinctrl-single,pins = <
AM33XX_PADCONF(AM335X_PIN_XDMA_EVENT_INTR1, PIN_OUTPUT_PULLDOWN, MUX_MODE3) /* xdma_event_intr1.clkout2 */
@@ -190,6 +204,20 @@
status = "okay";
};
+
+&uart1 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&uart1_pins>;
+
+ status = "okay";
+};
+
+&uart4 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&uart4_pins>;
+
+ status = "okay";
+};
&usb {
status = "okay”;
This change is activating and enabling those uarts at boot and does pin muxing properly.
It’s not muxing only as I previously assumed wrongly investigating the initial overlays.
I will go with that and if in future it is required programming proper overlays for
this that will be a side quest unrelated to barebox.
I just put a result into this mail thread if someone stumbles upon this.
Kind Regards
Konsti
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4124 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-06-22 10:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 8:10 Konstantin Kletschke
2021-06-16 12:34 ` Sascha Hauer
2021-06-16 15:57 ` Konstantin Kletschke
2021-06-16 19:55 ` Trent Piepho
2021-06-18 12:43 ` Konstantin Kletschke
2021-06-17 6:41 ` Sascha Hauer
2021-06-18 13:15 ` Konstantin Kletschke
2021-06-21 4:01 ` Sascha Hauer
2021-06-21 14:21 ` Konstantin Kletschke
2021-06-22 10:40 ` Konstantin Kletschke [this message]
2021-06-18 6:48 ` Ahmad Fatoum
2021-06-18 13:16 ` Konstantin Kletschke
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=1D32E771-3167-453F-AF94-606F610CEEC2@inside-m2m.de \
--to=konstantin.kletschke@inside-m2m.de \
--cc=barebox@lists.infradead.org \
--cc=sha@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox