Re: [PATCH 0/3] AW8695 haptic driver.

[Val Packett]

On 9/14/26 11:37 AM, Griffin Kroah-Hartman wrote:
> Clean-up of the aw8695 haptic driver patchset that was sent in 2022.
> Variables dependant on devicetree have been hardcoded, and unnecessary
> functions have been removed.
> [..]

This looks similar to aw86927.c just with a somewhat different register 
layout, but there's even the same waveform and so on.

Could it be better / worth it to do everything in one driver (aw86927.c) 
and only have different register accessors per model but shared "logic" 
overall? Or would that make testing too annoying?

FWIW I've been trying to bring up aw86224 which has even fewer (but 
still *some*) differences to aw86927, so I'm potentially interested in 
having a unified base to add it to (when I figure out why it's stuck in 
overvoltage protection or whatever it was..)

Thanks,
~val