From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Tim Van Patten <timvp@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
robbarnes@google.com, lalithkraj@google.com,
rrangel@chromium.org, Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
chrome-platform@lists.linux.dev
Subject: Re: [PATCH] [v9] platform/chrome: cros_ec_lpc: Move host command to prepare/complete
Date: Wed, 17 May 2023 10:35:15 +0800 [thread overview]
Message-ID: <ZGQ9Y+vqWhQLHAQh@google.com> (raw)
In-Reply-To: <20230515142552.1.I17cae37888be3a8683911991602f18e482e7a621@changeid>
On Mon, May 15, 2023 at 02:25:52PM -0600, Tim Van Patten wrote:
> Update cros_ec_lpc_pm_ops to call cros_ec_lpc_prepare() during PM
> .prepare() and cros_ec_lpc_complete() during .complete(). This moves the
> host command that the AP sends and allows the EC to log entry/exit of
> AP's suspend/resume more accurately.
I can understand the patch wants to notify EC earlier/later when the system
suspend/resume. But what is the issue addressed? What happens if the
measurement of suspend/resume duration is not that accurate?
Copied from my previous mail:
* Should it move the callbacks?
* Is it appropriate to call cros_ec_suspend() when PM is still in prepare
phase and call cros_ec_resume() when PM is already in complete phase?
It seems prepare() is a more general callback. It could be followed by
suspend(), freeze(), or poweroff()[1]. Do we expect the change? For example,
the system is going to power off but EC gets notification about the system
should be going to suspend. Same as complete().
Moreover, cros_ec_suspend() and cros_ec_resume() do more than just notify EC.
E.g. [2].
What about other interfaces (i2c, spi, uart)? Do they also need to change
the callbacks?
[1]: https://elixir.bootlin.com/linux/v6.4-rc1/source/include/linux/pm.h#L74
[2]: https://elixir.bootlin.com/linux/v6.4-rc1/source/drivers/platform/chrome/cros_ec.c#L351
> Changes in v9:
> - Remove log statements.
> - Ignore return value from cros_ec_resume().
The change logs are not part of commit message. They should put after "---".
next prev parent reply other threads:[~2023-05-17 2:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 20:25 [PATCH] [v9] platform/chrome: cros_ec_lpc: Move host command to prepare/complete Tim Van Patten
2023-05-17 2:35 ` Tzung-Bi Shih [this message]
2023-05-17 15:56 ` Tim Van Patten
2023-05-18 1:38 ` Tzung-Bi Shih
2023-05-18 16:47 ` Tim Van Patten
2023-05-19 1:55 ` Tzung-Bi Shih
2023-05-19 15:32 ` Tim Van Patten
2023-05-22 2:00 ` patchwork-bot+chrome-platform
2023-05-22 8:10 ` 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=ZGQ9Y+vqWhQLHAQh@google.com \
--to=tzungbi@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=lalithkraj@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robbarnes@google.com \
--cc=rrangel@chromium.org \
--cc=timvp@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