From: patchwork-bot+chrome-platform@kernel.org
To: Stephen Boyd <swboyd@chromium.org>
Cc: linus.walleij@linaro.org, brgl@bgdev.pl,
linux-kernel@vger.kernel.org, patches@lists.linux.dev,
devicetree@vger.kernel.org, chrome-platform@lists.linux.dev,
dianders@chromium.org, treapking@chromium.org,
linux-gpio@vger.kernel.org, lee@kernel.org, bleung@chromium.org,
groeck@chromium.org
Subject: Re: [PATCH v2] gpio: Add ChromeOS EC GPIO driver
Date: Mon, 25 Mar 2024 01:54:22 +0000 [thread overview]
Message-ID: <171133166251.9916.2499455576829331445.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240220045230.2852640-1-swboyd@chromium.org>
Hello:
This patch was applied to chrome-platform/linux.git (for-kernelci)
by Bartosz Golaszewski <bartosz.golaszewski@linaro.org>:
On Mon, 19 Feb 2024 20:52:27 -0800 you wrote:
> The ChromeOS embedded controller (EC) supports setting the state of
> GPIOs when the system is unlocked, and getting the state of GPIOs in all
> cases. The GPIOs are on the EC itself, so the EC acts similar to a GPIO
> expander. Add a driver to get and set the GPIOs on the EC through the
> host command interface.
>
> Cc: Lee Jones <lee@kernel.org>
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Cc: Bartosz Golaszewski <brgl@bgdev.pl>
> Cc: Benson Leung <bleung@chromium.org>
> Cc: Guenter Roeck <groeck@chromium.org>
> Cc: <linux-gpio@vger.kernel.org>
> Cc: <chrome-platform@lists.linux.dev>
> Cc: Pin-yen Lin <treapking@chromium.org>
> Signed-off-by: Stephen Boyd <swboyd@chromium.org>
>
> [...]
Here is the summary with links:
- [v2] gpio: Add ChromeOS EC GPIO driver
https://git.kernel.org/chrome-platform/c/f837fe1bffe6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-03-25 1:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 4:52 [PATCH v2] gpio: Add ChromeOS EC GPIO driver Stephen Boyd
2024-02-20 8:38 ` Linus Walleij
2024-02-20 11:48 ` Bartosz Golaszewski
2024-03-25 1:54 ` patchwork-bot+chrome-platform [this message]
2024-03-25 2:13 ` patchwork-bot+chrome-platform
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=171133166251.9916.2499455576829331445.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=bleung@chromium.org \
--cc=brgl@bgdev.pl \
--cc=chrome-platform@lists.linux.dev \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=groeck@chromium.org \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=swboyd@chromium.org \
--cc=treapking@chromium.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).