All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+chrome-platform@kernel.org
To: Ben Walsh <ben@jubnut.com>
Cc: bleung@chromium.org, tzungbi@kernel.org, groeck@chromium.org,
	dustin@howett.net, ktl@frame.work, linux@weissschuh.net,
	mario.limonciello@amd.com, chrome-platform@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] platform/chrome: Fix MEC concurrency problems for Framework Laptop
Date: Thu, 06 Jun 2024 03:30:38 +0000	[thread overview]
Message-ID: <171764463882.22288.7075641947422598016.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240605063351.14836-1-ben@jubnut.com>

Hello:

This series was applied to chrome-platform/linux.git (for-next)
by Tzung-Bi Shih <tzungbi@kernel.org>:

On Wed,  5 Jun 2024 07:33:46 +0100 you wrote:
> Framework Laptops with the Microchip EC have a problem where the EC
> "stops working" after a while. Symptoms include the Fn key not
> working, and "bad packet checksum" errors appearing in the system log.
> 
> The problem is caused by ACPI code which accesses the Microchip EC
> (MEC) memory using the Microchip EMI protocol. It uses an AML mutex to
> prevent concurrent access. But the cros_ec_lpc driver is not aware of
> this mutex. The ACPI code and LPC driver both attempt to talk to the
> EC at the same time, messing up communication with the EC.
> 
> [...]

Here is the summary with links:
  - [v3,1/5] platform/chrome: cros_ec_lpc: MEC access can return error code
    https://git.kernel.org/chrome-platform/c/68dbac0a58ef
  - [v3,2/5] platform/chrome: cros_ec_lpc: MEC access can use an AML mutex
    https://git.kernel.org/chrome-platform/c/60c7df66450e
  - [v3,3/5] platform/chrome: cros_ec_lpc: Add a new quirk for ACPI id
    https://git.kernel.org/chrome-platform/c/040159e0912c
  - [v3,4/5] platform/chrome: cros_ec_lpc: Add a new quirk for AML mutex
    https://git.kernel.org/chrome-platform/c/38c31b1d737b
  - [v3,5/5] platform/chrome: cros_ec_lpc: Add quirks for Framework Laptop
    https://git.kernel.org/chrome-platform/c/04ca0a51f1e6

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-06-06  3:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05  6:33 [PATCH v3 0/5] platform/chrome: Fix MEC concurrency problems for Framework Laptop Ben Walsh
2024-06-05  6:33 ` [PATCH v3 1/5] platform/chrome: cros_ec_lpc: MEC access can return error code Ben Walsh
2024-06-05  6:33 ` [PATCH v3 2/5] platform/chrome: cros_ec_lpc: MEC access can use an AML mutex Ben Walsh
2024-06-06  3:12   ` Tzung-Bi Shih
2024-06-06  5:23     ` Ben Walsh
2024-06-05  6:33 ` [PATCH v3 3/5] platform/chrome: cros_ec_lpc: Add a new quirk for ACPI id Ben Walsh
2024-06-05  6:33 ` [PATCH v3 4/5] platform/chrome: cros_ec_lpc: Add a new quirk for AML mutex Ben Walsh
2024-06-05  6:33 ` [PATCH v3 5/5] platform/chrome: cros_ec_lpc: Add quirks for Framework Laptop Ben Walsh
2024-06-06  3:30 ` [PATCH v3 0/5] platform/chrome: Fix MEC concurrency problems " patchwork-bot+chrome-platform
2024-06-06  3:30 ` 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=171764463882.22288.7075641947422598016.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+chrome-platform@kernel.org \
    --cc=ben@jubnut.com \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=dustin@howett.net \
    --cc=groeck@chromium.org \
    --cc=ktl@frame.work \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=mario.limonciello@amd.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.