[BPI-R2] Control On-board LEDs

Hdmi is not working in kernels != 4.4,

dual gmac only in 4.4 (without dsa) and 4.9 (with dsa).

In 4.9 maybe you can archive it by disabling dsa-driver.

Are you sure this is correct?

earlycon=uart8250,mmio32,0x11004000

./build.sh allone is enough to build 4.14 (no need for param)

Yes, Iā€™m sure. Boot with:

console=earlyprintk console=tty1 fbcon=map:0 console=ttyS0,115200

But with

console=console=ttyS0,115200 earlycon=uart8250,mmio32,0x11004000 earlyprintk=serial,ttyS0,115200 debug=7 loglevel=7 ignore_loglevel=1

canā€™t boot.

In kernels != 4.4 for HDMI it is a problem with drivers or something other? It is possible to have/port LEDs support in/to kernel 4.4?

console ttyS0 is mapped via dtsā€¦a user from github gave me the line with adressā€¦have not tried it yet ā€¦btw. you have ā€œconsole=console=ā€ at beginningā€¦

HDMI is ported to current mainline-kernel 4.17, now this have to be backported to 4.14ā€¦hoping gary / jack are working on it

you can try to port the dts-nodes from 4.14 to 4.4 and add CONFIG_LED to your config

in my wiki there is an instruction for Access to GPIO also for 4.4ā€¦you have to search where the nodes in 4.4 for ledā€¦

The first ā€œconsole=ā€ in both lines is a variable in uEnv.txt file, so I think it is correct. I will try to find how to access LEDs in kernel 4.4 without any additional electronic elements (resistors etc.).

Rightt the first is correct,but not assigning console= to it

anyone know how to disable the blinking from green isink-led?

btw. the patch for pio-leds is included in linux-next:

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts?h=next-20180718&id=2ca48895ba984c9b1fa0e725064decfed527811b

Patch is included in 4.19

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts

1 Like

@frank-w Hello. Thanks for your work again! Any advice how to turn off the annoying Ethernet (mt7530) leds? There is definitely the according GPIO support in drivers, though need to locate them in the sys tree.

In my case for Linux mxbpir201 4.14.27-bpi-r2-main Thanks in advance!

I would look where MT7530_LED_EN is used and set value to 0 :slight_smile: