Skip to content
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

input: misc: qcom-spmi-haptics: make auto res mode and vmax configureable via DT prop #217

Open
wants to merge 3 commits into
base: 6.12/main
Choose a base branch
from

Conversation

Smankusors
Copy link

@Smankusors Smankusors commented Nov 23, 2024

This has been tested on my Zenfone 3 ZE520KL with pmi8952, and it works as I wanted using qcom,auto-res-mode = <HAP_AUTO_RES_QWD> and qcom,vmax-millivolt = <1500>.

On another note, I noticed that the pm660 has only two available auto res modes to select:
https://github.com/Zenfone-5-X00QD-4-19/kernel_asus_sdm660/blob/3163b5f4e036f69e43626ae60f4b67b8bb61b733/drivers/soc/qcom/qpnp-haptic.c#L232-L235

I think supporting the pm660 is outside the scope of this PR, and the haptics on my Zenfone 5 with pm660 seem to be functioning normally anyway.

Wdyt?

@barni2000
Copy link
Member

barni2000 commented Jan 1, 2025

I think one of your commit prefix is not correct. Check this https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Documentation/devicetree/bindings/submitting-patches.rst

You should separte schema modifications from the code modification

also:
* remove unused HAP_VMAX_MAX_MV_STRONG
* adjust spmi_haptics_play_effect so that it's not overriding the vmax from DT

Signed-off-by: Antony K. S <[email protected]>
@Smankusors Smankusors force-pushed the haptic-auto-res-vmax-dt-prop branch from 971559b to e0741e1 Compare January 5, 2025 14:06
@Smankusors
Copy link
Author

I think one of your commit prefix is not correct. Check this https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Documentation/devicetree/bindings/submitting-patches.rst

You should separte schema modifications from the code modification

ok, updated and rebased 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants