[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168514964951.348612.17473479796367169535.b4-ty@kernel.org>
Date: Fri, 26 May 2023 18:07:28 -0700
From: Bjorn Andersson <andersson@...nel.org>
To: Rob Herring <robh+dt@...nel.org>, Dan Murphy <dmurphy@...com>,
Yassine Oudjana <y.oudjana@...tonmail.com>,
Luca Weiss <luca@...tu.xyz>, phone-devel@...r.kernel.org,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Raffaele Tranquillini <raffaele.tranquillini@...il.com>,
Andy Gross <agross@...nel.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
~postmarketos/upstreaming@...ts.sr.ht,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-input@...r.kernel.org
Subject: Re: (subset) [PATCH 0/5] Improvements for drv260x driver and add to Huawei Watch
On Sun, 30 Apr 2023 20:20:52 +0200, Luca Weiss wrote:
> Clean up some issues with the driver I've noticed while working on it,
> then fix the magnitude handling which previously resulted the driver
> discarding the upper 8 bits of the magnitude value, and finally we can
> add the drv260x to the APQ8026 Huawei Watch.
>
> While the "fix magnitude handling" commit technically changes behavior
> and could change behavior of existing user space applications that deal
> with this quirky behavior, it's definitely not correct and results in
> very unexpected behavior if the user space doesn't look out for it
> (meaning only use 0x00-0xFF magnitude, and also know that the magnitude
> was interpreted as signed value, see more details in the commit message
> there).
>
> [...]
Applied, thanks!
[5/5] ARM: dts: qcom: apq8026-huawei-sturgeon: Add vibrator
commit: ad318f9ce5a2e815816bfcf7f187a3ac32905523
Best regards,
--
Bjorn Andersson <andersson@...nel.org>
Powered by blists - more mailing lists