Jean-Francois Lessard

Thanks for great work @Jean-Francois Lessard !!!
I think the trigger was not loaded OK with my manual install.
My 2 boxes is for the moment HA in production and the second one is updated Android V11 (from V10) then it was having problems running large IPTV (corrupting the files system) that looks working OK now.
Then i have getting all stable and also can getting HyperHDR also running (USB problems . . .  with V1.4 hardware but one other box looks doing better but not the USB3) i can doing one rockade and doing more testing.

@L Jumadi It looks like you should reverse the pin configuration of the data and clock pins
 
Your openvfd config:
```
openvfd_gpio_clk = <&pio 8 11 0>; // this is the clock ping
openvfd_gpio_dat = <&pio 8 12 0>; // this is the data pin
```
 
Should become:
```
sda-gpios = <&pio 8 12 (GPIO_ACTIVE_HIGH|GPIO_OPEN_DRAIN)>; // this is the data pin
scl-gpios = <&pio 8 11 (GPIO_ACTIVE_HIGH|GPIO_OPEN_DRAIN)>; // this is the clock pin
```
 
You can also try setting gpio flags to 0 such as in your openvfd config. It would become:
```
sda-gpios = <&pio 8 12 0>; // this is the data pin
scl-gpios = <&pio 8 11 0>; // this is the clock pin
```
 
Edit: I have added a check in tm16xx.c to report "Failed to initialize display" instead of "Display initialized successfully" when it fails to set brightness or to write display data. This won't fix your issue per se but at least it will add clarity when looking at dmesg.

Hello  @Jean-Francois Lessard, congratulations for the excellent driver!
I stumbled here because I started making myself an fd6551 driver , and just after I discovered you already published a fully working product, which is way more polished than mine.
 
Anyway, I did not have yet the chance to tm16xx driver, but will do soon and report here the result. I have a HK1 box with rk3318 and fd6551 chip on board.
 
 
 
 
 

In the meantime I integrated the driver into armbian for rockchip64 targets: https://github.com/armbian/build/pull/7338 , so it will be a bit easier to test it out-of-the box and it would also be easier for amlogic people to copy-paste the driver patch and integrate the device trees as well.
 
My tests on hk1 rk3318 tv box (board silkscreen YX_RK3318) worked like a charm and the display is now pleasantly showing up-to-date date and time
 

Hi
 
I've made a new kernel Auxiliary Display Driver for TM16XX and compatible LED controllers. This driver supports various LED controller chips, including TM16XX family, FD6XX family, PT6964, and HBS658. It provides support for both I2C and SPI interfaces.
 
I wanted it to manage the hardware on the kernel space while having an easy sysfs user space interface. It also aims to reduce the code to maintain by relaying on existing kernel features instead of recoding them. Plus, you can switch to hardware i2c/spi (instead of software gpio) depending on the pins used.
 
You can use "vfdconf-convert" to convert your existing vfd.conf to its device-tree version.  Or you can use the already converted vfd.conf of https://github.com/arthur-liberman/vfd-configurations that are listed in the device table.
 
You don't need to manually edit your device tree, the "make" command will apply the device tree source overlay to your dtb.
 
It comes with a service written as a simple bash script. So it's easily customizable without having to write custom C code.
 
Instructions and source code at https://github.com/jefflessard/tm16xx-display/
 
Could you please give it a try and report your feedback? 

I have added rk3566-h96-max-v56 to the repo. You could try with this one.
 
I think the JianPian is very similar to H96 Max V56 so I made this config file from this post.
 
This is a blind attempt... I have no much info on the JianPian and I have no way to test the config. Let me know if it works for you.
 

I have added rk3566-h96-max-v56 to the repo. You could try with this one.
 
I think the JianPian is very similar to H96 Max V56 so I made this config file from this post.
 
This is a blind attempt... I have no much info on the JianPian and I have no way to test the config. Let me know if it works for you.
 

Hi
 
I've made a new kernel Auxiliary Display Driver for TM16XX and compatible LED controllers. This driver supports various LED controller chips, including TM16XX family, FD6XX family, PT6964, and HBS658. It provides support for both I2C and SPI interfaces.
 
I wanted it to manage the hardware on the kernel space while having an easy sysfs user space interface. It also aims to reduce the code to maintain by relaying on existing kernel features instead of recoding them. Plus, you can switch to hardware i2c/spi (instead of software gpio) depending on the pins used.
 
You can use "vfdconf-convert" to convert your existing vfd.conf to its device-tree version.  Or you can use the already converted vfd.conf of https://github.com/arthur-liberman/vfd-configurations that are listed in the device table.
 
You don't need to manually edit your device tree, the "make" command will apply the device tree source overlay to your dtb.
 
It comes with a service written as a simple bash script. So it's easily customizable without having to write custom C code.
 
Instructions and source code at https://github.com/jefflessard/tm16xx-display/
 
Could you please give it a try and report your feedback?