From: Stephen Boyd <swboyd@chromium.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
linux-kernel@vger.kernel.org, patches@lists.linux.dev,
linux-arm-msm@vger.kernel.org,
Matthias Kaehlcke <mka@chromium.org>,
Alexandru M Stan <amstan@chromium.org>
Subject: Re: [PATCH v2 2/2] arm64: dts: qcom: Fully describe fingerprint node on Trogdor
Date: Tue, 8 Nov 2022 16:56:26 -0800 [thread overview]
Message-ID: <CAE-0n53yS28hwhNASP5KpgGHLAuEb4f_cUUc_iFc6LpzynR62g@mail.gmail.com> (raw)
In-Reply-To: <CAD=FV=XKHftMn4Ja40fdDggwi78F2pB0A+prs94+fFBhbSvNYw@mail.gmail.com>
Quoting Doug Anderson (2022-11-07 17:22:51)
> On Mon, Nov 7, 2022 at 11:15 AM Stephen Boyd <swboyd@chromium.org> wrote:
> >
> > diff --git a/arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi b/arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi
> > index 4a5ea17a15ba..65601bea0797 100644
> > --- a/arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi
> > +++ b/arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi
> > @@ -894,13 +894,16 @@ ap_spi_fp: &spi10 {
> > cs-gpios = <&tlmm 89 GPIO_ACTIVE_LOW>;
> >
> > cros_ec_fp: ec@0 {
> > - compatible = "google,cros-ec-spi";
> > + compatible = "google,cros-ec-fp", "google,cros-ec-spi";
> > reg = <0>;
> > interrupt-parent = <&tlmm>;
> > interrupts = <4 IRQ_TYPE_LEVEL_LOW>;
> > pinctrl-names = "default";
> > - pinctrl-0 = <&fp_to_ap_irq_l>;
> > + pinctrl-0 = <&fp_to_ap_irq_l>, <&fp_rst_l>, <&fpmcu_boot0>;
> > + boot0-gpios = <&tlmm 10 GPIO_ACTIVE_HIGH>;
> > + reset-gpios = <&tlmm 22 GPIO_ACTIVE_LOW>;
>
> This isn't totally a no-op change since the pinctrl entries for
> fp_rst_l and fpmcu_boot0 will now be applied. I assume you've
> confirmed that it works as expected?
Yes my fingerprint still works to unlock. I also confirmed that the bios
sets these pinctrl settings so this is to be more explicit and not rely
on bootloader state.
>
> ...other than the subject (same as patch #1), this LGTM.
>
> Reviewed-by: Douglas Anderson <dianders@chromium.org>
Cool thanks.
next prev parent reply other threads:[~2022-11-09 0:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 19:15 [PATCH v2 0/2] Update fingerprint node on herobrine/trogdor Stephen Boyd
2022-11-07 19:15 ` [PATCH v2 1/2] arm64: dts: qcom: Fully describe fingerprint node on Herobrine Stephen Boyd
2022-11-08 1:22 ` Doug Anderson
2022-11-07 19:15 ` [PATCH v2 2/2] arm64: dts: qcom: Fully describe fingerprint node on Trogdor Stephen Boyd
2022-11-08 1:22 ` Doug Anderson
2022-11-09 0:56 ` Stephen Boyd [this message]
2022-11-08 4:36 ` (subset) [PATCH v2 0/2] Update fingerprint node on herobrine/trogdor Bjorn Andersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAE-0n53yS28hwhNASP5KpgGHLAuEb4f_cUUc_iFc6LpzynR62g@mail.gmail.com \
--to=swboyd@chromium.org \
--cc=agross@kernel.org \
--cc=amstan@chromium.org \
--cc=andersson@kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=patches@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).