-
Notifications
You must be signed in to change notification settings - Fork 5.2k
bcm2710-rpi-zero-2-w.dts defines "TXD0" and "RXD0" twice #5058
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
This duplication comes as a result of the mixed heritage of the Zero 2 W - half Zero and half 3B. The Zero 2W schematic calls the first two of these Thanks for reporting this - see 83bb376 for the fix. |
Thank you for the swift response. Apologies, I should have also checked other Zero variants - I notice that the Zero W dts also has this oddity. |
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
Also fixed now. |
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: raspberrypi#5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: raspberrypi#5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: raspberrypi#5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: raspberrypi#5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
Closing as the reported fault has been fixed. |
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: raspberrypi#5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: raspberrypi#5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: #5058 Signed-off-by: Phil Elwell <[email protected]>
commit 83bb3768c8823ec294e4a7f30d1c9e1b308b7e96 from https://github.com/raspberrypi/linux.git rpi-5.15.y GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: raspberrypi/linux#5058 Signed-off-by: Phil Elwell <[email protected]> Signed-off-by: Meng Li <[email protected]>
commit e4adbab1f577d9a88b5056c5dad41ae7ee79f977 from https://github.com/raspberrypi/linux.git rpi-5.15.y GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: raspberrypi/linux#5058 Signed-off-by: Phil Elwell <[email protected]> Signed-off-by: Meng Li <[email protected]>
commit 83bb3768c8823ec294e4a7f30d1c9e1b308b7e96 from https://github.com/raspberrypi/linux.git rpi-5.15.y GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: raspberrypi/linux#5058 Signed-off-by: Phil Elwell <[email protected]> Signed-off-by: Meng Li <[email protected]>
commit e4adbab1f577d9a88b5056c5dad41ae7ee79f977 from https://github.com/raspberrypi/linux.git rpi-5.15.y GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: raspberrypi/linux#5058 Signed-off-by: Phil Elwell <[email protected]> Signed-off-by: Meng Li <[email protected]>
commit 83bb3768c8823ec294e4a7f30d1c9e1b308b7e96 from https://github.com/raspberrypi/linux.git rpi-5.15.y GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: raspberrypi/linux#5058 Signed-off-by: Phil Elwell <[email protected]> Signed-off-by: Meng Li <[email protected]>
commit e4adbab1f577d9a88b5056c5dad41ae7ee79f977 from https://github.com/raspberrypi/linux.git rpi-5.15.y GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: raspberrypi/linux#5058 Signed-off-by: Phil Elwell <[email protected]> Signed-off-by: Meng Li <[email protected]>
GPIOs 14 and 15 are currently labelled TXD0 and RXD0, which matches comments on the schematic but 1) doesn't reflect their likely usage (i.e. UART1) and 2) clashes with GPIOs 32 and 33. Adopt the common naming for those two pins on BT-equipped Pis - TXD1 and RXD1. See: raspberrypi/linux#5058 Signed-off-by: Phil Elwell <[email protected]>
Describe the bug
File bcm2710-rpi-zero-2-w.dts has "TXD0" and "RXD0" defined twice. I believe the first definitions should be TXD1 and RXD1 in line with other boards.
Steps to reproduce the behaviour
The
gpioinfo
command lists TXD0 and RXD0 twice.Device (s)
Raspberry Pi Zero 2 W
System
$ cat /etc/rpi-issue
Raspberry Pi reference 2022-04-04
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 27a8050c3c06e567c794620394a8c2d74262a516, stage2
$ vcgencmd version
Mar 24 2022 13:20:54
Copyright (c) 2012 Broadcom
version e5a963efa66a1974127860b42e913d2374139ff5 (clean) (release) (start)
$ uname -a
Linux zero2-1 5.15.32-v8+ #1538 SMP PREEMPT Thu Mar 31 19:40:39 BST 2022 aarch64 GNU/Linux
Logs
No response
Additional context
I appreciate this is a minor issue, however, confuses GPIO auto discovery.
The text was updated successfully, but these errors were encountered: