public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Prashant Malani <pmalani@chromium.org>
To: Alyssa Ross <hi@alyssa.is>
Cc: linux-kernel@vger.kernel.org, Tzung-Bi Shih <tzungbi@google.com>,
	Benson Leung <bleung@chromium.org>,
	Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	Guenter Roeck <groeck@chromium.org>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>
Subject: Re: [PATCH v2] platform/chrome: cros_ec_typec: Check for EC device
Date: Wed, 26 Jan 2022 23:08:14 +0000	[thread overview]
Message-ID: <YfHUXtJPU77wtCPb@chromium.org> (raw)
In-Reply-To: <20220126230411.nn2illij4wbpdm4q@eve>

Hi Alyssa,

On Jan 26 23:04, Alyssa Ross wrote:
> On Wed, Jan 26, 2022 at 07:02:20PM +0000, Prashant Malani wrote:
> > The Type C ACPI device on older Chromebooks is not generated correctly
> > (since their EC firmware doesn't support the new commands required). In
> > such cases, the crafted ACPI device doesn't have an EC parent, and it is
> > therefore not useful (it shouldn't be generated in the first place since
> > the EC firmware doesn't support any of the Type C commands).
> >
> > To handle devices which use these older firmware revisions, check for
> > the parent EC device handle, and fail the probe if it's not found.
> >
> > Fixes: fdc6b21e2444 ("platform/chrome: Add Type C connector class driver")
> > Reported-by: Alyssa Ross <hi@alyssa.is>
> > Reviewed-by: Tzung-Bi Shih <tzungbi@google.com>
> > Signed-off-by: Prashant Malani <pmalani@chromium.org>
> > ---
> > Hi Alyssa, could you kindly test this with your existing setup? Thanks!
> 
> Hi Prashant, I'm happy to test, but I'm on vacation until the end of the
> week so probably won't get a chance before Monday.

No worries, whenever you get the chance is fine.

> 
> I'm guessing I should be testing with latest upstream coreboot (now that
> your fix there has been applied)?

You should use the coreboot with which you discovered the crash, so the
one which *doesn't* contain the fix.

Thanks again!

-Prashant

  reply	other threads:[~2022-01-26 23:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 19:02 [PATCH v2] platform/chrome: cros_ec_typec: Check for EC device Prashant Malani
2022-01-26 23:04 ` Alyssa Ross
2022-01-26 23:08   ` Prashant Malani [this message]
2022-02-01 12:17     ` Alyssa Ross
2022-02-01 18:29       ` Prashant Malani
2022-01-31 11:13 ` Heikki Krogerus
2022-02-01 18:04 ` Benson Leung

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=YfHUXtJPU77wtCPb@chromium.org \
    --to=pmalani@chromium.org \
    --cc=bleung@chromium.org \
    --cc=enric.balletbo@collabora.com \
    --cc=groeck@chromium.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=hi@alyssa.is \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tzungbi@google.com \
    /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