From: patchwork-bot+chrome-platform@kernel.org
To: Mark Hasemeyer <markhas@chromium.org>
Cc: linux-kernel@vger.kernel.org, rrangel@chromium.org,
bhanumaiya@chromium.org, lkp@intel.com, pmalani@chromium.org,
bleung@chromium.org, groeck@chromium.org, tzungbi@kernel.org,
chrome-platform@lists.linux.dev
Subject: Re: [PATCH v12 1/3] platform/chrome: cros_ec_uart: Add cros-ec-uart transport layer
Date: Wed, 28 Dec 2022 05:40:16 +0000 [thread overview]
Message-ID: <167220601608.11271.13667673251726047908.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221209092619.v12.1.If7926fcbad397bc6990dd725690229bed403948c@changeid>
Hello:
This series was applied to chrome-platform/linux.git (for-next)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Fri, 9 Dec 2022 09:26:22 -0700 you wrote:
> From: Bhanu Prakash Maiya <bhanumaiya@chromium.org>
>
> This patch does following:
> 1. Adds a new cros-ec-uart driver. This driver can send EC requests on
> UART and process response packets received on UART transport.
> 2. Once probed, this driver will initialize the serdev device based on
> the underlying information in the ACPI resource. After serdev device
> properties are set, this driver will register itself cros-ec.
> 3. High level driver can use this implementation to talk to ChromeOS
> Embedded Controller device in case it supports UART as transport.
> 4. When cros-ec driver initiates a request packet, outgoing message is
> processed in buffer and sent via serdev. Once bytes are sent, driver
> enables a wait_queue.
> 5. Since ChromeOS EC device sends response asynchronously, AP's TTY
> driver accumulates response bytes and calls the registered callback.
> TTY driver can send multiple callback for bytes ranging from 1 to MAX
> bytes supported by EC device.
> 6. Driver waits for EC_MSG_DEADLINE_MS to collect and process received
> bytes. It wakes wait_queue if expected bytes are received or else
> wait_queue timeout. Based on the error condition, driver returns
> data_len or error to cros_ec.
>
> [...]
Here is the summary with links:
- [v12,1/3] platform/chrome: cros_ec_uart: Add cros-ec-uart transport layer
(no matching commit)
- [v12,2/3] dt-bindings: mfd: cros-ec: Add UART compatible string
https://git.kernel.org/chrome-platform/c/5be8cd61dcdd
- [v12,3/3] platform/chrome: cros_ec_uart: Add DT enumeration support
https://git.kernel.org/chrome-platform/c/c34fea225806
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-12-28 5:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 16:26 [PATCH v12 1/3] platform/chrome: cros_ec_uart: Add cros-ec-uart transport layer Mark Hasemeyer
2022-12-09 16:26 ` [PATCH v12 2/3] dt-bindings: mfd: cros-ec: Add UART compatible string Mark Hasemeyer
2022-12-09 16:26 ` [PATCH v12 3/3] platform/chrome: cros_ec_uart: Add DT enumeration support Mark Hasemeyer
2022-12-26 8:12 ` [PATCH v12 1/3] platform/chrome: cros_ec_uart: Add cros-ec-uart transport layer Tzung-Bi Shih
2022-12-27 10:16 ` Tzung-Bi Shih
2022-12-28 3:50 ` patchwork-bot+chrome-platform
2022-12-28 5:40 ` patchwork-bot+chrome-platform [this message]
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=167220601608.11271.13667673251726047908.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=bhanumaiya@chromium.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=markhas@chromium.org \
--cc=pmalani@chromium.org \
--cc=rrangel@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