From: Stephen Boyd <swboyd@chromium.org>
To: Benson Leung <bleung@chromium.org>
Cc: linux-kernel@vger.kernel.org, chrome-platform@lists.linux.dev,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, Guenter Roeck <groeck@chromium.org>,
Douglas Anderson <dianders@chromium.org>,
Craig Hesling <hesling@chromium.org>,
Tom Hughes <tomhughes@chromium.org>,
Alexandru M Stan <amstan@chromium.org>,
Tzung-Bi Shih <tzungbi@kernel.org>,
Matthias Kaehlcke <mka@chromium.org>
Subject: [PATCH v4 0/3] Update cros-ec-spi for fingerprint devices
Date: Mon, 21 Mar 2022 12:10:56 -0700 [thread overview]
Message-ID: <20220321191100.1993-1-swboyd@chromium.org> (raw)
This patch series introduces a DT binding for chromeos fingerprint
devices and then implements support to boot those processors during
driver probe if the BIOS hasn't done it already.
Changes from v3 (https://lore.kernel.org/r/20220318015451.2869388-1-swboyd@chromium.org):
* Drop spi_device_id because it isn't used
* Dropped struct members for gpios
* Picked up tags
Changes from v2 (https://lore.kernel.org/r/20220317005814.2496302-1-swboyd@chromium.org):
* Dropped cros-ec spi dt properties that aren't of use right now
* Picked up tags
Changes from v1 (https://lore.kernel.org/r/20220314232214.4183078-1-swboyd@chromium.org):
* Properly do the boot sequence
* Add a message that we're booting and delaying a while
* Fix typo in commit text
* Change binding to not spell out reset-gpios and indicate that boot0
is about asserting boot mode
* Split device id to different patch as it's a different topic from
booting
Stephen Boyd (3):
dt-bindings: chrome: Add ChromeOS fingerprint binding
platform/chrome: cros_ec_spi: Match cros-ec-fp compatible
platform/chrome: cros_ec_spi: Boot fingerprint processor during probe
.../bindings/chrome/google,cros-ec-fp.yaml | 66 +++++++++++++++++++
drivers/platform/chrome/cros_ec_spi.c | 43 +++++++++++-
2 files changed, 106 insertions(+), 3 deletions(-)
create mode 100644 Documentation/devicetree/bindings/chrome/google,cros-ec-fp.yaml
Cc: Rob Herring <robh+dt@kernel.org>
Cc: <devicetree@vger.kernel.org>
Cc: Guenter Roeck <groeck@chromium.org>
Cc: Douglas Anderson <dianders@chromium.org>
Cc: Craig Hesling <hesling@chromium.org>
Cc: Tom Hughes <tomhughes@chromium.org>
Cc: Alexandru M Stan <amstan@chromium.org>
Cc: Tzung-Bi Shih <tzungbi@kernel.org>
Cc: Matthias Kaehlcke <mka@chromium.org>
base-commit: ffb217a13a2eaf6d5bd974fc83036a53ca69f1e2
--
https://chromeos.dev
next reply other threads:[~2022-03-21 19:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 19:10 Stephen Boyd [this message]
2022-03-21 19:10 ` [PATCH v4 1/3] dt-bindings: chrome: Add ChromeOS fingerprint binding Stephen Boyd
2022-03-22 1:32 ` Rob Herring
2022-03-22 1:40 ` Stephen Boyd
2022-03-25 15:40 ` Stephen Boyd
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=20220321191100.1993-1-swboyd@chromium.org \
--to=swboyd@chromium.org \
--cc=amstan@chromium.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=groeck@chromium.org \
--cc=hesling@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=robh+dt@kernel.org \
--cc=tomhughes@chromium.org \
--cc=tzungbi@kernel.org \
/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).