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,
Garrick Evans <garrick@google.com>
Subject: Re: [PATCH] [v9] platform/chrome: cros_ec_lpc: Move host command to prepare/complete
Date: Fri, 19 May 2023 09:55:34 +0800 [thread overview]
Message-ID: <ZGbXFtrBzbaD9rQs@google.com> (raw)
In-Reply-To: <CAMaBtwFtE=vjuhVy7rw9zCe9WV0dRyeBWj88JH2j3bkbh2BkXA@mail.gmail.com>
On Thu, May 18, 2023 at 10:47:23AM -0600, Tim Van Patten wrote:
> On Wed, May 17, 2023 at 7:38 PM Tzung-Bi Shih <tzungbi@kernel.org> wrote:
> > On Wed, May 17, 2023 at 09:56:59AM -0600, Tim Van Patten wrote:
> > > The issue is that we need the EC aware of the AP being in the process
> > > of suspend/resume from start to finish, so we can accurately
> > > determine:
> > > - How long the process took to better gauge we're meeting ChromeOS requirements.
> > > - When the AP failed to complete the process, so we can collect data
> > > and perform error recovery.
[...]
> > How could the *error* recovery do?
>
> I don't understand what this is asking.
Given that you said "we can collect data and perform error recovery" if the
suspend-resume takes more/less time than expected. I'm trying to understand
what does "error recovery" mean. What recovery it could take?
> > > > What about other interfaces (i2c, spi, uart)? Do they also need to change
> > > the callbacks?
> > >
> > > We aren't concerned about those devices, because they aren't being
> > > used on the devices we're seeing issues with. If devices using those
> > > ECs want this change, they can pick it up as well, but we don't have
> > > any way to test changes on those devices (whatever they may be).
> >
> > This doesn't sound good. As I would suppose you are adding some new EC FW
> > features regarding to EC_CMD_HOST_SLEEP_EVENT, you should consider the
> > existing systems too.
>
> Again, why are you assuming there is new EC FW for this? This is only
> changing when an already-existing host command is being sent. Nothing
> is being added or removed.
I see. There is no EC changes.
Specifically, do you see any crashes, or premature events, or mal-functions
regarding to the measurement is not that accurate?
Also, we wouldn't want it to be LPC-specialized. Please consider other
interfaces.
next prev parent reply other threads:[~2023-05-19 1:55 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
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 [this message]
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=ZGbXFtrBzbaD9rQs@google.com \
--to=tzungbi@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=garrick@google.com \
--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;
as well as URLs for NNTP newsgroup(s).