Repository navigation
device-raven, tools: haptics through feedbackd on the CS40L25A - #113
Conversation
|
Thanks. The udev rule follows cheetah's, and the rescan unit is a neat way around feedbackd looking for its devices only at start-up. It's good that you checked it by replaying the motor's arrival. The firmware mapping only touches raven's branch of The red CI isn't yours: it's a flaky test in This merges after the driver (kernel #114), since |
|
Smoke report from the build that runs this: derekross/linux-omarchy-mobile#112 (comment). |
|
Thanks for the smoke report. It comes from a build with this PR's package changes in it (device-raven 0.1.23.5) and names the kernel, so that covers what I asked for here. I checked the rest again against today's main and the driver's new head:
One small thing before merge, if you can: the plan's H5 result names two kernels from before the driver's rework ( The order stays the same: the driver (kernel #114) first, once it's rebased with the one-line register-read fix, then this PR. I'll set the version at merge: 0.1.27, since #126 brings main's version file up to the 0.1.26 that #112 named. |
The kernel side is derekross/linux-omarchy-mobile#114 (cs40l25-vibra, its binding and raven's node). This is the rest: - device/raven/kernel.config builds cs40l25-vibra as a module. - extract-vendor-firmware -d raven stages the CS40L25A's files from the owner's factory image: the CLAB RAM firmware and the default wavetable, which the driver loads, and the CLAB configuration (braking), not loaded yet. - device-raven's 72-omamobile-feedbackd.rules makes the motor a feedbackd vibra, as cheetah's CS40L26. The motor's input device appears only once its firmware has loaded, about 5 s into the boot, and feedbackd (D-Bus activated) only looks for it when it starts, so on a boot where something asked for feedback first there were no haptics until feedbackd was restarted. The motor's arrival now starts omamobile-feedbackd-rescan.service, which stops a running feedbackd; the next request starts it again with the motor. HAPTICS-TORCH-PLAN records H5 and the boot race. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
e2793db to
df34e24
Compare
|
Rebased onto |
|
Thanks. The rebase keeps both sides of the The one red job is the I'll merge this right after the driver (derekross/linux-omarchy-mobile#114). At merge I'll set the version file to 0.1.27 and put it in the title, so they agree. Once both are in, I'll also update raven's Haptics cell in DEVICES.md to point at H5. |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The matrix and the Wanted list against what has merged since #140, with each pull request's state checked on GitHub today: - Pixel 7 (panther): the GPU and haptics nodes (kernel #129, #130) were closed because they landed unchanged through kernel #134, merged with the touchscreen node and s2idle by default; device-panther 0.1.1 (#145) carries the GPU's always-on rule, the feedbackd rule and the sleep.conf drop-in. GPU and Haptics stay "testing" and now cite #134, #145 and the 2026-10-28 notes. Touch stays WIP: kernel #134's body records touches driving Hyprland and the PIN screen, but the driver fixes (kernel #133) and the kernel option with the touch notes (#149) are still in review. Suspend: "no" with the s2idle default named, since the notes say it hasn't run. - Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5 passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel #114, feedbackd's rule in device-raven 0.1.27 (#113). Display names its open kernel PR, #116. - Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (#133) records it scanning through its own UART; kernel #98 and #98 are in review. The Wanted line says so too. - Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained vbmeta_b needs (NOTES 2026-10-28 and 10-29, #104); Suspend describes the merged tier 1 auto-sleep (#64, off by default behind the omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old "until S8" text. Nothing from the open #171, #172, #174-#176. - Wanted: coral's #52 is merged, so its line no longer says "in review"; flame gets a line for its native install in review (#55, #56, #58, #59, split out of #17); the OnePlus 13 (dodge) is listed with #111 and kernel #115, both open. The Pixel 9a row and the Pixel 9 family line are left to #165. Every status word still parses with the website's parseCell. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…derekross#113) * device-raven, tools: haptics through feedbackd on the CS40L25A The kernel side is derekross/linux-omarchy-mobile#114 (cs40l25-vibra, its binding and raven's node). This is the rest: - device/raven/kernel.config builds cs40l25-vibra as a module. - extract-vendor-firmware -d raven stages the CS40L25A's files from the owner's factory image: the CLAB RAM firmware and the default wavetable, which the driver loads, and the CLAB configuration (braking), not loaded yet. - device-raven's 72-omamobile-feedbackd.rules makes the motor a feedbackd vibra, as cheetah's CS40L26. The motor's input device appears only once its firmware has loaded, about 5 s into the boot, and feedbackd (D-Bus activated) only looks for it when it starts, so on a boot where something asked for feedback first there were no haptics until feedbackd was restarted. The motor's arrival now starts omamobile-feedbackd-rescan.service, which stops a running feedbackd; the next request starts it again with the motor. HAPTICS-TORCH-PLAN records H5 and the boot race. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * device-raven 0.1.27: the haptics version bump Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Derek Ross <derekross@gmail.com>
The matrix and the Wanted list against what has merged since derekross#140, with each pull request's state checked on GitHub today: - Pixel 7 (panther): the GPU and haptics nodes (kernel derekross#129, derekross#130) were closed because they landed unchanged through kernel derekross#134, merged with the touchscreen node and s2idle by default; device-panther 0.1.1 (derekross#145) carries the GPU's always-on rule, the feedbackd rule and the sleep.conf drop-in. GPU and Haptics stay "testing" and now cite derekross#134, derekross#145 and the 2026-10-28 notes. Touch stays WIP: kernel derekross#134's body records touches driving Hyprland and the PIN screen, but the driver fixes (kernel derekross#133) and the kernel option with the touch notes (derekross#149) are still in review. Suspend: "no" with the s2idle default named, since the notes say it hasn't run. - Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5 passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel derekross#114, feedbackd's rule in device-raven 0.1.27 (derekross#113). Display names its open kernel PR, derekross#116. - Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (derekross#133) records it scanning through its own UART; kernel derekross#98 and derekross#98 are in review. The Wanted line says so too. - Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained vbmeta_b needs (NOTES 2026-10-28 and 10-29, derekross#104); Suspend describes the merged tier 1 auto-sleep (derekross#64, off by default behind the omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old "until S8" text. Nothing from the open derekross#171, derekross#172, derekross#174-derekross#176. - Wanted: coral's derekross#52 is merged, so its line no longer says "in review"; flame gets a line for its native install in review (derekross#55, derekross#56, derekross#58, derekross#59, split out of derekross#17); the OnePlus 13 (dodge) is listed with derekross#111 and kernel derekross#115, both open. The Pixel 9a row and the Pixel 9 family line are left to derekross#165. Every status word still parses with the website's parseCell. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The rest of raven's haptics, with the driver in derekross/linux-omarchy-mobile#114: raven's
kernel.configbuildscs40l25-vibra,extract-vendor-firmware -d ravenstages the CS40L25A's firmware from the owner's factory image, and a udev rule makes the motor a feedbackd vibra, as cheetah's.The motor appears only once its firmware has loaded, about 5 s into the boot, and feedbackd looks for it only when it starts, so some boots had no haptics until feedbackd was restarted. The motor's arrival now restarts a running feedbackd. Tested on raven: key-press haptics on the keyboard, and the restart checked by replaying the motor's arrival. Version bump left to you.
🤖 Generated with Claude Code