No LED indication on tanix tx6 android box

[hqctfl]

Hello arthur, one issue raised on my tanix tx6 box which is allwinner H6 SOC based, I am running on android for this box, the LED controller is FD650, but no indication on the LED when I used the openvfd driver for the android system. The dmesg copied below, I used the contents from vfd.conf and phased in sysconfig.fex (device tree for android) for android rom pack. The dmesg always show "OpenVFD: Select Dummy controller" and I cannot switch to controller FD650. Can you please have a look？ Thank you.

vfd.conf: ;This file must be renamed to vfd.conf and placed in the /storage/.config/ folder. ; ; Tanix TX6 - Allwinner H6 configuration ;-------------------- ;gpio_xxx: ; [0] 0 = &gpiochip0, 1 = &gpiochip1. ; [1] pin number ; [0] Reserved - must be 0.

vfd_gpio_clk='1,229,0' vfd_gpio_dat='1,230,0' vfd_gpio_stb='0,0,0xFF' vfd_gpio_chip_name='300b000.pinctrl'

;chars: ; < DHHMM > Order of display chars (D=dots, represented by a single char)

vfd_chars='2,4,3,2,1'

;dot_bits: ; Order of dot bits. Typical configurations: ; Display Type 0, 1 usually has Alarm, USB, Play, Pause, Col, Ethernet, Wifi dots ; Alarm = 0, USB = 1, Play = 2, Pause = 3, Col = 4, Eth = 5, Wifi = 6 ; Display Type 2 usually has APPS, USB, SETUP, CARD, Col, HDMI, CVBS dots ; APPS = 0, USB = 1, SETUP = 2, CARD = 3, Col = 4, HDMI = 5, CVBS = 6 ; Display Type 3 Power, LAN, Col, Low Wifi, High Wifi ; N/A = 0, N/A = 1, Power = 2, LAN = 3, Col = 4, Low Wifi = 5, High Wifi = 6

vfd_dot_bits='0,1,2,3,4,5,6'

;display_type: ; [0] - Display type. ; [1] - Reserved - must be 0.. ; [2] - Flags. (bit 0 = '1' - Common Anode display) ; [3] - Controller.

vfd_display_type='0x01,0x00,0x00,0x03'

dmesg: [ 7.830385] OpenVFD: Version: V1.4.1 [ 7.834328] OpenVFD: vfd_gpio_clk: Empty. [ 7.838838] OpenVFD: vfd_gpio_dat: Empty. [ 7.843617] OpenVFD: vfd_gpio_stb: Empty. [ 7.848119] OpenVFD: vfd_gpio0: #0 = 0x00; #1 = 0x00; #2 = 0xFF; [ 7.857572] OpenVFD: vfd_gpio1: #0 = 0x00; #1 = 0x00; #2 = 0xFF; [ 7.864588] OpenVFD: vfd_gpio2: #0 = 0x00; #1 = 0x00; #2 = 0xFF; [ 7.873018] OpenVFD: vfd_gpio3: #0 = 0x00; #1 = 0x00; #2 = 0xFF; [ 7.880416] OpenVFD: vfd_gpio_protocol: #0 = 0x00; #1 = 0x00; [ 7.887442] OpenVFD: vfd_chars: Empty. [ 7.892095] OpenVFD: vfd_dot_bits: Empty. [ 7.896809] OpenVFD: vfd_display_type: Empty. [ 7.902171] OpenVFD: Detected gpio chips: pio, r_pio. [ 7.910410] OpenVFD: Failed to verify VFD configuration file, attempt using device tree as fallback. [ 7.921209] OpenVFD: openvfd_gpio_clk: pin = 229, flags = 0xE5 [ 7.927650] OpenVFD: openvfd_gpio_dat: pin = 230, flags = 0xE6 [ 7.934653] OpenVFD: openvfd_gpio_stb pin entry not found [ 7.940929] OpenVFD: openvfd_gpio0 pin entry not found [ 7.946594] OpenVFD: openvfd_gpio1 pin entry not found [ 7.983617] OpenVFD: openvfd_gpio2 pin entry not found [ 7.989587] OpenVFD: openvfd_gpio3 pin entry not found [ 7.995901] OpenVFD: chars_prop = ffffffc0bbfde618 [ 8.001867] OpenVFD: chars_prop->length = 11 [ 8.006567] OpenVFD: char #0: 50 [ 8.010277] OpenVFD: char #1: 44 [ 8.014072] OpenVFD: char #2: 52 [ 8.017606] OpenVFD: char #3: 44 [ 8.021380] OpenVFD: char #4: 51 [ 8.025367] OpenVFD: char #5: 44 [ 8.028878] OpenVFD: char #6: 50 [ 8.032686] OpenVFD: dot_bits_prop = ffffffc0bbfde648 [ 8.038266] OpenVFD: dot_bits_prop->length = 15 [ 8.043504] OpenVFD: dot_bit #0: 48 [ 8.047344] OpenVFD: dot_bit #1: 44 [ 8.051350] OpenVFD: dot_bit #2: 49 [ 8.055198] OpenVFD: dot_bit #3: 44 [ 8.059047] OpenVFD: dot_bit #4: 50 [ 8.063124] OpenVFD: dot_bit #5: 44 [ 8.066964] OpenVFD: dot_bit #6: 51 [ 8.070958] OpenVFD: dot_bit #7: 44 [ 8.074799] OpenVFD: dot_bit #8: 52 [ 8.078640] OpenVFD: dot_bit #9: 44 [ 8.082776] OpenVFD: dot_bit #10: 53 [ 8.086766] OpenVFD: dot_bit #11: 44 [ 8.090862] OpenVFD: dot_bit #12: 54 [ 8.094806] OpenVFD: dot_bit #13: 39 [ 8.098755] OpenVFD: dot_bit #14: 0 [ 8.102850] OpenVFD: display.type = 51, display.controller = 48, pdata->dev->dtb_active.display.flags = 0x78 [ 8.115436] OpenVFD: Select Dummy controller [ 8.143211] no ioctl found(cmd:0x13) in disp_unregister_compat_ioctl_func [ 8.143423] init: Starting service 'openvfd'...

[arthur-liberman]

You provided a chipname that doesn't exist. You can see Detected gpio chips: pio, r_pio that it's either pio or r_pio. Also, I'm not sure what you did, but according to the dmesg output, your vfd.conf file had not been applied at all. You can see by the output that everything is empty.

[hqctfl]

Thanks for response. The vfd.conf should be placed in the /storage/.config/ folder as per the introduction, but I am running android on the box, there is no /storage/.config/ folder, I think the address is for debian or other similar systems rather than android. I cannot creat the folder on android partition, since the android system is not rooted. I copied the contents from vfd.conf to device tree definition file of sys_config.fex (please see dmesg [ 7.910410] OpenVFD: Failed to verify VFD configuration file, attempt using device tree as fallback). Seems the openvfd service cannot find the specific vfd controller which should be FD650 on the tanix tx6 box. Can you support how to write the device tree definition file of sys_config.fex? Or help to figure out where can I drop the file of vfd.conf on android system? For obtaining your further response, thank you so much.

[hqctfl]

supplement for the format of device tree definition file of sys_config.fex on the android system: the configuration should be "openvfd_gpio_clk= xxx" instead of "vfd_gpio_clk= xxx"

[arthur-liberman]

The instructions are for CoreELEC, not for Android. The driver should technically still work, but you need to make manual configuration changes to make it work with your device. If it's stock android, the display should just work. If you're using a custom/3rd party image, you will need to make your own changes to the configuration. The error + the output you see tells you that the configuration in your vfd.conf file were not applied when loading the driver. There is a basic support for dtb configuration, but I think it'll only work with amlogic devices.

[hqctfl]

Thanks for your prompt response, I will further study the approach and try to make the LED work on my own complied android ROM.

[arthur-liberman]

Closing due to lack of activity. Please let me know if you still have an issue with the latest commits pushed recently.