• Content Count

  • Joined

  • Last visited

About Learnincurve

  • Rank
    Elite member

Recent Profile Visitors

1417 profile views
  1. Yes. This is working now! You just need to enable it in armbian-conf and make sure the "goodix" module gets loaded at boot for the touchscreen. Ignore instructions of the download page for now, they are for the older legacy releases. If you have trouble with the touchscreen failing to load on reboot, see this post:
  2. This is resolved now. After reading https://www.raspberrypi.org/forums/viewtopic.php?t=216901 I created the following systemd service file: Unit] Description=unload the goodix driver ahead of reboots to allow it to properly load again when the system restarts [Service] ExecStop=/sbin/rmmod goodix Type=oneshot RemainAfterExit=true [Install] WantedBy=multi-user.target System now comes up with working touchscreen every time:)
  3. Hi Lucapinello, Thank you for the tip to make sure ts_uinput -d is running. For me, the problem with reboot seems to be at a lower level (at goodix module load and before tslib gets loaded). I am trying to work out how to unload the goodix module before reboot, as a manual removal of the module leads to a working reboot, but am having some trouble writing a systemd service that runs early, before reboot BR.
  4. 5.10.4-sunxi64 pine64 board with goodix 7" mipi-dsi LCD touchscreen. The LCD output is working fine across reboots after enabling the dt overlay using armbian-config. For the touchscreen, I have added "goodix" to /etc/modules and the digitizer works fine from all cold boots: ~$ dmesg | grep -i goodix [ 5.836601] Goodix-TS 1-005d: supply VDDIO not found, using dummy regulator [ 5.843605] Goodix-TS 1-005d: ID k}\xfa, version: 7b6f [ 5.866815] input: Goodix Capacitive TouchScreen as /devices/platform/soc/1c2ac00.i2c/i2c-1/1-005d/input/input5
  5. I'm having the same problem on a Pine64-plus. [ 6.465215] WARNING: CPU: 2 PID: 34 at drivers/clocksource/arm_arch_timer.c:364 sun50i_a64_read_cntpct_el0+0x2c/0x38 [ 6.467239] Modules linked in: cpufreq_dt joydev sch_fq_codel goodix panel_feiyang_fy07024di26a30d pinctrl_axp209 realtek dwmac_sun8i mdio_mux i2c_mv64xxx pwm_bl [ 6.470647] CPU: 2 PID: 34 Comm: kworker/2:1 Not tainted 5.10.4-sunxi64 #20.11.7 [ 6.472786] Hardware name: Pine64+ (DT) [ 6.475136] Workqueue: events dbs_work_handler [ 6.477389] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO BTYPE=--) [ 6.47956
  6. Hi, Thanks to the hard work of your team, the Pine64-plus touchscreen now works great with the mainline kernel and legacy images are no longer listed in the download options, but it looks like some of the instructions at https://www.armbian.com/pine64/ are still referring to the "old way" of doing things: ie: Pine64’s own LCD with touchscreen support can simply be activated in /boot/armbianEnv.txt by setting pine64_lcd=on and adding gt9xxf_ts to /etc/modules followed by a reboot. The LCD screen is now activated by manipulating the DT overlays, whic
  7. I found the solution at I was expecting this to be called "cir something", but the device is already listed in the device tree as ir@1f02000. I did a sudo fdtput -t s /boot/dtb/allwinner/sun50i-a64-pine64-plus.dtb /soc/ir@1f02000 status okay and rebooted. Device now shows up as /dev/input/event2 Now all I need is to find some codes that can be used with it.
  8. Hi, Thank you all for so much work to fully implement the mainline kernel for the Pine64! So much is now working out-of-the-box with armbian, that there is no need to use the legacy version based on kernel 3.10. The pine64 does have CIR capabilities and the sunxi-cir kernel module is available, but we are still missing DT bindings for the device, although I see that an overlay file is present for the h5: /dts-v1/; / { compatible = "allwinner,sun50i-h5"; fragment@0 { target = <0xffffffff>; __overl
  9. I cheated and upgraded to nightly from the latest stable build, which you can do from the armbian-config - System menu. Otherwise I see that all of https://minio.k-space.ee/armbian/ is unavailable at the moment. The link will probably work again later.
  10. : Issue is finally fixed in (at least) nightly builds ! There is now a "pine64-7inch-lcd" overlay in /boot/dtb//allwinner/overlay Just add "overlays=pine64-7inch-lcd" to armbianEnv.txt and screen magically works. A BIG thank you to the team for fixing this! Pine64 is now ready for mainline kernel goodness!
  11. Good suggestion! I did try disabling hdmi stuff earlier (without success, but not sure if it was before or after adding the panel, so will try again). I'm also a DTS-noob and finding it hard to get my head around it. Hence my spamming of this thread, which it looks like the experts are now filtering out (can't say I blame them).
  12. Update: I just took out the feiyang panel section in the device tree, as that gives the clearest dmesg indication that the dsi port is working: Have also discovered armbianmonitor -u. Dump at http://ix.io/2E03
  13. Hi p1x313d. Thank you for your support! No. The problem is not that I don't have the panel, I do. My problem is lack of understanding and knowledge regarding the Device Tree. I am at the stage where I am stuck, unable to correctly set the pins (I think) for the panel. @lex was able to do this, using an earlier kernel and device tree, but too many internal references in the later available trees have changed, and I'm not smart enough to sort them out. If you or anyone else would like to help trying to debug, I'd be very grateful, as this i
  14. Found that this isn't going to work without the Feiyang panel. Where I am stuck now is the reset-gpios for the feiyang panel dts code extracted from @lex's dtb post earlier in this thread and modified with unique phandles for the current tree: dsi@1ca0000 { compatible = "allwinner,sun50i-a64-mipi-dsi"; reg = <0x1ca0000 0x1000>; interrupts = <0x00 0x59 0x04>; clocks = <0x02 0x1c>; resets = <0x02 0x05>; phys = <0x44>; phy-names = "dphy"; status = "okay";