mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tzung-Bi Shih <tzungbi@kernel.org>
To: James Fairweather <james.a.fairweather@gmail.com>
Cc: "Łukasz Bartosik" <ukaszb@chromium.org>,
	"Andrei Kuchynski" <akuchynski@chromium.org>,
	"Jameson Thies" <jthies@google.com>,
	"Benson Leung" <bleung@chromium.org>,
	chrome-platform@lists.linux.dev,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, stiraspo@gmail.com
Subject: Re: [PATCH] platform/chrome: cros_usbpd_notify: Only use parent drvdata when parent is GOOG0004
Date: Mon, 5 Oct 2026 03:41:10 +0000	[thread overview]
Message-ID: <asMcVmEa67BUmQ3D@google.com> (raw)
In-Reply-To: <20261003222855.23707-1-james.a.fairweather@gmail.com>

On Sat, Oct 03, 2026 at 06:28:53PM -0400, James Fairweather wrote:
> Only read the parent's driver data when the parent's ACPI node is
> GOOG0004, and otherwise continue without an EC pointer. While at it,
> drop the reference taken by fwnode_get_parent().

Because of this, I'll add "Fixes: e4ee0bb077cd ..." as well when applying
the patch.

> Tested on a Google Nami-based Chromebook (BIOS 09/19/2019)
> running a 7.2.5 distro kernel (linux-omarchy 7.2.5-3). The unpatched
> driver oopsed twice in two days, each time on a charger plug/unplug.
> With this patch built as a module against that kernel, the probe logs
> "Couldn't get Chrome EC device pointer." (confirming GOOG0003's parent
> is not GOOG0004 here), and 12 charger unplug/replug cycles produced no
> oops, with charging negotiating 20V/3.5A as before.

Hi James,

Thanks for looking into this.

Sergey Tiraspolsky ran into the same issue on a Pixelbook (Eve) and sent a
patch shortly before yours [1].  However, because your patch also catches
and resolves the preexisting fwnode reference leak, I plan to proceed with
your patch.

When applying, I plan to credit Sergey's earlier report by adding a
"Reported-by" tag.  I've also CC'd Sergey and invited testing on Eve if
feasible.

[1] https://lore.kernel.org/all/20261003204623.18124-1-stiraspo@gmail.com/

  reply	other threads:[~2026-10-05  3:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-03 22:28 James Fairweather
2026-10-05  3:41 ` Tzung-Bi Shih [this message]
2026-10-06  7:14 ` Sergey Tiraspolsky
2026-10-06 10:28 ` Tzung-Bi Shih

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=asMcVmEa67BUmQ3D@google.com \
    --to=tzungbi@kernel.org \
    --cc=akuchynski@chromium.org \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=james.a.fairweather@gmail.com \
    --cc=jthies@google.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=stiraspo@gmail.com \
    --cc=ukaszb@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

all inboxes | Powered by JetHome®