[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Zh24eN9ZMZ6QhzeZ@google.com>
Date: Mon, 15 Apr 2024 16:30:00 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Cc: quic_fenglinw@...cinc.com, kernel@...cinc.com,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
linux-arm-msm@...r.kernel.org, linux-input@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v10 1/4] input: pm8xxx-vibrator: correct VIB_MAX_LEVELS
calculation
On Fri, Apr 12, 2024 at 07:21:16PM +0300, Dmitry Baryshkov wrote:
> On Fri, 12 Apr 2024 at 15:36, Fenglin Wu via B4 Relay
> <devnull+quic_fenglinw.quicinc.com@...nel.org> wrote:
> >
> > From: Fenglin Wu <quic_fenglinw@...cinc.com>
> >
> > The output voltage is inclusive hence the max level calculation is
> > off-by-one-step. Correct it.
>
> ... while we are at it also add a define for the step size instead of
> using the magic value.
I adjusted the patch description as Dmitry suggested, and applied this
patch. Please address Konrad's feedback on the other 2 and I will apply
the rest.
Thank you.
--
Dmitry
Powered by blists - more mailing lists