All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Samuel Čavoj" <samuel@cavoj.net>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: typec: ucsi: introduce read_explicit operation
Date: Sat, 18 Mar 2023 03:04:32 +0100	[thread overview]
Message-ID: <c5223adc99dd9bf849071e8fdfed4bb1@cavoj.net> (raw)
In-Reply-To: <ZBMUsweZjfqxZJdc@kuha.fi.intel.com>

Hi,

On 2023-03-16 14:08, Heikki Krogerus wrote:
> On Wed, Mar 08, 2023 at 06:17:47PM +0200, Heikki Krogerus wrote:
>> Hi Samuel,
>> 
>> > I asked that Samuel to share this here, but perhaps we should consider
>> > it still as an RFC. I have tested this with some of my platforms, but
>> > I want to test more.
>> 
>> Sorry about the slow progress, but this is causing commands to fail on
>> some platforms. I've been trying to figure out how to fix those, but
>> nothing has worked so far.

No worries, I've been very busy with other stuff as well, that's
why I haven't responded for some time--nothing new on my end.

>> I think we have to handle this with a DMI quick in ucsi_acpi.c. I
>> don't have any other ideas. I'll try a few more things, and then
>> prepare a patch for that.
> 
> Unfortunately nothing seems to work... I'm attaching the DMI quirk
> patch here. Can you test it?

I'll definitely try it out, I hope sometime next week!

> I'm not sure if the DMI_PRODUCT_NAME is just "ZenBook" so you may
> need to fix that in the patch!!
> 
> You can get the correct value by running dmidecode. This should work:
> 
>         % dmidecode -s system-product-name
> 
> thanks,

Thanks
Sam

  reply	other threads:[~2023-03-18  2:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-20 23:39 [PATCH] usb: typec: ucsi: introduce read_explicit operation Samuel Čavoj
2023-01-21  7:17 ` Greg KH
2023-01-24 11:21   ` Heikki Krogerus
2023-03-08 16:17     ` Heikki Krogerus
2023-03-16 13:08       ` Heikki Krogerus
2023-03-18  2:04         ` Samuel Čavoj [this message]
2023-03-29 23:48           ` Samuel Čavoj
2023-03-30 14:06             ` Heikki Krogerus
2023-04-01 18:06               ` Samuel Čavoj
2023-04-04 13:02                 ` Heikki Krogerus

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=c5223adc99dd9bf849071e8fdfed4bb1@cavoj.net \
    --to=samuel@cavoj.net \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-usb@vger.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.