[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+BfgNKcG4ShokZ3ERmg75nJXMRbwJeAH=GnWwHt6A3XRar+gQ@mail.gmail.com>
Date: Mon, 3 Jun 2024 13:28:31 -0500
From: Dustin Howett <dustin@...ett.net>
To: Ben Walsh <ben@...nut.com>
Cc: Benson Leung <bleung@...omium.org>, Tzung-Bi Shih <tzungbi@...nel.org>,
Guenter Roeck <groeck@...omium.org>, Kieran Levin <ktl@...me.work>,
Thomas Weißschuh <linux@...ssschuh.net>,
Mario Limonciello <mario.limonciello@....com>, chrome-platform@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/5] platform/chrome: Fix MEC concurrency problems for
Framework Laptop
On Mon, Jun 3, 2024 at 1:38 AM Ben Walsh <ben@...nut.com> wrote:
>
> It has _not_ been tested on any Chromebook devices.
Good news!
I've tested this patch series on the following devices:
- Chromebook Pixel 2013 ("link")
- Framework Laptop 11th Gen Intel Core ("hx20"), firmware revision 3.19
- Framework Laptop AMD Ryzen 7040 Series ("azalea"), firmware revision 3.05
It works as expected.
There is no detectable difference at runtime on Link, nor does the
driver appear to improperly bind any ACPI devices.
I cannot reproduce bus contention on hx20, even performing operations
that would consistently fail without this patch (e.g. long flash
reads).
Therefore, for the series:
Tested-on: link, hx20, azalea
Tested-by: Dustin L. Howett <dustin@...ett.net>
Powered by blists - more mailing lists