forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 125
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
harpia: Some touchscreens do not work #190
Labels
Comments
@iyzsong Can you ping me in the postmarketOS mainline chat for help? Thanks. |
Sure, I'll ping you there when I'm available for it, thank you! |
I made it somehow work by report
Close it for now.. Thank you! |
ghost
closed this as completed
Apr 18, 2021
ghost
referenced
this issue
in msm8953-mainline/linux
Apr 22, 2021
Skip setting rate for clk_pixel_ops and clk_byte2+ops when clock is already enabled on same rate, so following warning won't be produced. byte0_clk_src: rcg didn't update its configuration. WARNING: CPU: 0 PID: 12 at drivers/clk/qcom/clk-rcg2.c:122 update_config+0xc4/0xd8 Modules linked in: CPU: 0 PID: 12 Comm: kworker/0:1 Not tainted 5.6.0-rc3-postmarketos-qcom-msm8953-00022-ga0e3878d15f8-dirty #190 Hardware name: Samsung A6-Plus LTE Rev.4 (DT) Workqueue: events deferred_probe_work_func pstate: 60000005 (nZCv daif -PAN -UAO) pc : update_config+0xc4/0xd8 lr : update_config+0xc4/0xd8 sp : ffff800011cbb0f0 x29: ffff800011cbb0f0 x28: ffff0000acb6ccc0 x27: ffff800010879b18 x26: ffff0000adc9e9a8 x25: 0000000000000000 x24: 000000000773286c x23: ffff800010bfb848 x22: ffff800010a27178 x21: ffff0000add09b00 x20: ffff800010bfb848 x19: 0000000000000000 x18: 0000000000000020 x17: 0000000000011940 x16: 0000000000000006 x15: ffff0000add09f50 x14: ffffffffffffffff x13: 0000000000000000 x12: ffff800010c76000 x11: ffff800010bad000 x10: ffff800010c764c8 x9 : ffff80001010cb48 x8 : 6974617275676966 x7 : 6e6f632073746920 x6 : ffff800010c76533 x5 : 0000000000000000 x4 : 0000000000000000 x3 : 00000000ffffffff x2 : ffff8000a0da4000 x1 : 78c520ed39868900 x0 : 0000000000000000 Call trace: update_config+0xc4/0xd8 clk_rcg2_configure+0x28/0x38 clk_byte2_set_rate+0xdc/0x110 clk_change_rate+0x100/0x540 clk_core_set_rate_nolock+0x1ac/0x200 clk_set_rate+0x3c/0xa8 dsi_link_clk_set_rate_6g+0x40/0xe8 msm_dsi_host_power_on+0x130/0x6a0 dsi_mgr_bridge_pre_enable+0x1f4/0x318 drm_atomic_bridge_chain_pre_enable+0x80/0x98 drm_atomic_helper_commit_modeset_enables+0x11c/0x250 msm_atomic_commit_tail+0x178/0x838 commit_tail+0xa4/0x188 drm_atomic_helper_commit+0x148/0x178 drm_atomic_commit+0x50/0x60 drm_client_modeset_commit_atomic.isra.0+0x17c/0x230 drm_client_modeset_commit_force+0x60/0x198 drm_fb_helper_restore_fbdev_mode_unlocked+0x78/0xd8 drm_fb_helper_set_par+0x34/0x68 fbcon_init+0x3cc/0x590 visual_init+0xb4/0x108 do_bind_con_driver+0x1d4/0x3a8 do_take_over_console+0x144/0x200 do_fbcon_takeover+0x70/0xd8 fbcon_fb_registered+0x100/0x110 register_framebuffer+0x208/0x318 __drm_fb_helper_initial_config_and_unlock+0x300/0x4a8 drm_fb_helper_initial_config+0x4c/0x58 msm_fbdev_init+0x90/0xf0 msm_drm_bind+0x5d8/0x650 try_to_bring_up_master+0x268/0x2f0 __component_add+0xd0/0x198 component_add+0x18/0x20 dsi_dev_probe+0x20/0x28 platform_drv_probe+0x58/0xa8 really_probe+0x120/0x438 driver_probe_device+0x9c/0x138 __device_attach_driver+0xb0/0x120 bus_for_each_drv+0x7c/0xc8 __device_attach+0xe4/0x168 device_initial_probe+0x18/0x20 bus_probe_device+0x98/0xa0 deferred_probe_work_func+0xa4/0xe0 process_one_work+0x1c0/0x468 worker_thread+0x50/0x428 kthread+0x104/0x130 ret_from_fork+0x10/0x18 ---[ end trace 212da46ab98f1674 ]---
Kiciuk
referenced
this issue
in Kiciuk/linux
May 3, 2021
Skip setting rate for clk_pixel_ops and clk_byte2+ops when clock is already enabled on same rate, so following warning won't be produced. byte0_clk_src: rcg didn't update its configuration. WARNING: CPU: 0 PID: 12 at drivers/clk/qcom/clk-rcg2.c:122 update_config+0xc4/0xd8 Modules linked in: CPU: 0 PID: 12 Comm: kworker/0:1 Not tainted 5.6.0-rc3-postmarketos-qcom-msm8953-00022-ga0e3878d15f8-dirty msm8953-mainline#190 Hardware name: Samsung A6-Plus LTE Rev.4 (DT) Workqueue: events deferred_probe_work_func pstate: 60000005 (nZCv daif -PAN -UAO) pc : update_config+0xc4/0xd8 lr : update_config+0xc4/0xd8 sp : ffff800011cbb0f0 x29: ffff800011cbb0f0 x28: ffff0000acb6ccc0 x27: ffff800010879b18 x26: ffff0000adc9e9a8 x25: 0000000000000000 x24: 000000000773286c x23: ffff800010bfb848 x22: ffff800010a27178 x21: ffff0000add09b00 x20: ffff800010bfb848 x19: 0000000000000000 x18: 0000000000000020 x17: 0000000000011940 x16: 0000000000000006 x15: ffff0000add09f50 x14: ffffffffffffffff x13: 0000000000000000 x12: ffff800010c76000 x11: ffff800010bad000 x10: ffff800010c764c8 x9 : ffff80001010cb48 x8 : 6974617275676966 x7 : 6e6f632073746920 x6 : ffff800010c76533 x5 : 0000000000000000 x4 : 0000000000000000 x3 : 00000000ffffffff x2 : ffff8000a0da4000 x1 : 78c520ed39868900 x0 : 0000000000000000 Call trace: update_config+0xc4/0xd8 clk_rcg2_configure+0x28/0x38 clk_byte2_set_rate+0xdc/0x110 clk_change_rate+0x100/0x540 clk_core_set_rate_nolock+0x1ac/0x200 clk_set_rate+0x3c/0xa8 dsi_link_clk_set_rate_6g+0x40/0xe8 msm_dsi_host_power_on+0x130/0x6a0 dsi_mgr_bridge_pre_enable+0x1f4/0x318 drm_atomic_bridge_chain_pre_enable+0x80/0x98 drm_atomic_helper_commit_modeset_enables+0x11c/0x250 msm_atomic_commit_tail+0x178/0x838 commit_tail+0xa4/0x188 drm_atomic_helper_commit+0x148/0x178 drm_atomic_commit+0x50/0x60 drm_client_modeset_commit_atomic.isra.0+0x17c/0x230 drm_client_modeset_commit_force+0x60/0x198 drm_fb_helper_restore_fbdev_mode_unlocked+0x78/0xd8 drm_fb_helper_set_par+0x34/0x68 fbcon_init+0x3cc/0x590 visual_init+0xb4/0x108 do_bind_con_driver+0x1d4/0x3a8 do_take_over_console+0x144/0x200 do_fbcon_takeover+0x70/0xd8 fbcon_fb_registered+0x100/0x110 register_framebuffer+0x208/0x318 __drm_fb_helper_initial_config_and_unlock+0x300/0x4a8 drm_fb_helper_initial_config+0x4c/0x58 msm_fbdev_init+0x90/0xf0 msm_drm_bind+0x5d8/0x650 try_to_bring_up_master+0x268/0x2f0 __component_add+0xd0/0x198 component_add+0x18/0x20 dsi_dev_probe+0x20/0x28 platform_drv_probe+0x58/0xa8 really_probe+0x120/0x438 driver_probe_device+0x9c/0x138 __device_attach_driver+0xb0/0x120 bus_for_each_drv+0x7c/0xc8 __device_attach+0xe4/0x168 device_initial_probe+0x18/0x20 bus_probe_device+0x98/0xa0 deferred_probe_work_func+0xa4/0xe0 process_one_work+0x1c0/0x468 worker_thread+0x50/0x428 kthread+0x104/0x130 ret_from_fork+0x10/0x18 ---[ end trace 212da46ab98f1674 ]---
alikates
referenced
this issue
in alikates/linux
Jun 17, 2021
Skip setting rate for clk_pixel_ops and clk_byte2+ops when clock is already enabled on same rate, so following warning won't be produced. byte0_clk_src: rcg didn't update its configuration. WARNING: CPU: 0 PID: 12 at drivers/clk/qcom/clk-rcg2.c:122 update_config+0xc4/0xd8 Modules linked in: CPU: 0 PID: 12 Comm: kworker/0:1 Not tainted 5.6.0-rc3-postmarketos-qcom-msm8953-00022-ga0e3878d15f8-dirty msm8953-mainline#190 Hardware name: Samsung A6-Plus LTE Rev.4 (DT) Workqueue: events deferred_probe_work_func pstate: 60000005 (nZCv daif -PAN -UAO) pc : update_config+0xc4/0xd8 lr : update_config+0xc4/0xd8 sp : ffff800011cbb0f0 x29: ffff800011cbb0f0 x28: ffff0000acb6ccc0 x27: ffff800010879b18 x26: ffff0000adc9e9a8 x25: 0000000000000000 x24: 000000000773286c x23: ffff800010bfb848 x22: ffff800010a27178 x21: ffff0000add09b00 x20: ffff800010bfb848 x19: 0000000000000000 x18: 0000000000000020 x17: 0000000000011940 x16: 0000000000000006 x15: ffff0000add09f50 x14: ffffffffffffffff x13: 0000000000000000 x12: ffff800010c76000 x11: ffff800010bad000 x10: ffff800010c764c8 x9 : ffff80001010cb48 x8 : 6974617275676966 x7 : 6e6f632073746920 x6 : ffff800010c76533 x5 : 0000000000000000 x4 : 0000000000000000 x3 : 00000000ffffffff x2 : ffff8000a0da4000 x1 : 78c520ed39868900 x0 : 0000000000000000 Call trace: update_config+0xc4/0xd8 clk_rcg2_configure+0x28/0x38 clk_byte2_set_rate+0xdc/0x110 clk_change_rate+0x100/0x540 clk_core_set_rate_nolock+0x1ac/0x200 clk_set_rate+0x3c/0xa8 dsi_link_clk_set_rate_6g+0x40/0xe8 msm_dsi_host_power_on+0x130/0x6a0 dsi_mgr_bridge_pre_enable+0x1f4/0x318 drm_atomic_bridge_chain_pre_enable+0x80/0x98 drm_atomic_helper_commit_modeset_enables+0x11c/0x250 msm_atomic_commit_tail+0x178/0x838 commit_tail+0xa4/0x188 drm_atomic_helper_commit+0x148/0x178 drm_atomic_commit+0x50/0x60 drm_client_modeset_commit_atomic.isra.0+0x17c/0x230 drm_client_modeset_commit_force+0x60/0x198 drm_fb_helper_restore_fbdev_mode_unlocked+0x78/0xd8 drm_fb_helper_set_par+0x34/0x68 fbcon_init+0x3cc/0x590 visual_init+0xb4/0x108 do_bind_con_driver+0x1d4/0x3a8 do_take_over_console+0x144/0x200 do_fbcon_takeover+0x70/0xd8 fbcon_fb_registered+0x100/0x110 register_framebuffer+0x208/0x318 __drm_fb_helper_initial_config_and_unlock+0x300/0x4a8 drm_fb_helper_initial_config+0x4c/0x58 msm_fbdev_init+0x90/0xf0 msm_drm_bind+0x5d8/0x650 try_to_bring_up_master+0x268/0x2f0 __component_add+0xd0/0x198 component_add+0x18/0x20 dsi_dev_probe+0x20/0x28 platform_drv_probe+0x58/0xa8 really_probe+0x120/0x438 driver_probe_device+0x9c/0x138 __device_attach_driver+0xb0/0x120 bus_for_each_drv+0x7c/0xc8 __device_attach+0xe4/0x168 device_initial_probe+0x18/0x20 bus_probe_device+0x98/0xa0 deferred_probe_work_func+0xa4/0xe0 process_one_work+0x1c0/0x468 worker_thread+0x50/0x428 kthread+0x104/0x130 ret_from_fork+0x10/0x18 ---[ end trace 212da46ab98f1674 ]---
SirSireesh
referenced
this issue
in msm8953-mainline/linux
Sep 10, 2021
Skip setting rate for clk_pixel_ops and clk_byte2+ops when clock is already enabled on same rate, so following warning won't be produced. byte0_clk_src: rcg didn't update its configuration. WARNING: CPU: 0 PID: 12 at drivers/clk/qcom/clk-rcg2.c:122 update_config+0xc4/0xd8 Modules linked in: CPU: 0 PID: 12 Comm: kworker/0:1 Not tainted 5.6.0-rc3-postmarketos-qcom-msm8953-00022-ga0e3878d15f8-dirty #190 Hardware name: Samsung A6-Plus LTE Rev.4 (DT) Workqueue: events deferred_probe_work_func pstate: 60000005 (nZCv daif -PAN -UAO) pc : update_config+0xc4/0xd8 lr : update_config+0xc4/0xd8 sp : ffff800011cbb0f0 x29: ffff800011cbb0f0 x28: ffff0000acb6ccc0 x27: ffff800010879b18 x26: ffff0000adc9e9a8 x25: 0000000000000000 x24: 000000000773286c x23: ffff800010bfb848 x22: ffff800010a27178 x21: ffff0000add09b00 x20: ffff800010bfb848 x19: 0000000000000000 x18: 0000000000000020 x17: 0000000000011940 x16: 0000000000000006 x15: ffff0000add09f50 x14: ffffffffffffffff x13: 0000000000000000 x12: ffff800010c76000 x11: ffff800010bad000 x10: ffff800010c764c8 x9 : ffff80001010cb48 x8 : 6974617275676966 x7 : 6e6f632073746920 x6 : ffff800010c76533 x5 : 0000000000000000 x4 : 0000000000000000 x3 : 00000000ffffffff x2 : ffff8000a0da4000 x1 : 78c520ed39868900 x0 : 0000000000000000 Call trace: update_config+0xc4/0xd8 clk_rcg2_configure+0x28/0x38 clk_byte2_set_rate+0xdc/0x110 clk_change_rate+0x100/0x540 clk_core_set_rate_nolock+0x1ac/0x200 clk_set_rate+0x3c/0xa8 dsi_link_clk_set_rate_6g+0x40/0xe8 msm_dsi_host_power_on+0x130/0x6a0 dsi_mgr_bridge_pre_enable+0x1f4/0x318 drm_atomic_bridge_chain_pre_enable+0x80/0x98 drm_atomic_helper_commit_modeset_enables+0x11c/0x250 msm_atomic_commit_tail+0x178/0x838 commit_tail+0xa4/0x188 drm_atomic_helper_commit+0x148/0x178 drm_atomic_commit+0x50/0x60 drm_client_modeset_commit_atomic.isra.0+0x17c/0x230 drm_client_modeset_commit_force+0x60/0x198 drm_fb_helper_restore_fbdev_mode_unlocked+0x78/0xd8 drm_fb_helper_set_par+0x34/0x68 fbcon_init+0x3cc/0x590 visual_init+0xb4/0x108 do_bind_con_driver+0x1d4/0x3a8 do_take_over_console+0x144/0x200 do_fbcon_takeover+0x70/0xd8 fbcon_fb_registered+0x100/0x110 register_framebuffer+0x208/0x318 __drm_fb_helper_initial_config_and_unlock+0x300/0x4a8 drm_fb_helper_initial_config+0x4c/0x58 msm_fbdev_init+0x90/0xf0 msm_drm_bind+0x5d8/0x650 try_to_bring_up_master+0x268/0x2f0 __component_add+0xd0/0x198 component_add+0x18/0x20 dsi_dev_probe+0x20/0x28 platform_drv_probe+0x58/0xa8 really_probe+0x120/0x438 driver_probe_device+0x9c/0x138 __device_attach_driver+0xb0/0x120 bus_for_each_drv+0x7c/0xc8 __device_attach+0xe4/0x168 device_initial_probe+0x18/0x20 bus_probe_device+0x98/0xa0 deferred_probe_work_func+0xa4/0xe0 process_one_work+0x1c0/0x468 worker_thread+0x50/0x428 kthread+0x104/0x130 ret_from_fork+0x10/0x18 ---[ end trace 212da46ab98f1674 ]---
Re-opening this since I think it is still unsolved. Ideally someone should work with the RMI4 maintainers upstream to get this handled in a sane way somehow. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Original reported in postmarketOS: https://gitlab.com/postmarketOS/pmaports/-/issues/672
We use this mainline kernel in postmarketOS for harpia, so I think report the issue here maybe more useful..
I have a motorola harpia, lk2nd report panel as
qcom,mdss_dsi_mot_boe_499_720p_video_v1
:Device was reset during configuration process, status: 0x1!
, then no synaptics input event device available in the system.rmi_f01_probe
:synaptics input device available, and it can "moving" but not "touch", with rmi_core debug_flags=15, I dumped dmesg:
Help needed to get my touchscreen working, thank you!
The text was updated successfully, but these errors were encountered: