linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: "Samuel Čavoj" <samuel@cavoj.net>
Cc: linux-usb@vger.kernel.org
Subject: Re: How to proceed: usci_acpi: PPM init failed (-110)
Date: Thu, 24 Mar 2022 11:45:03 +0200	[thread overview]
Message-ID: <Yjw9n5FXHMp8TpsM@kuha.fi.intel.com> (raw)
In-Reply-To: <23e8104421efcf0937168e0ac5489367@cavoj.net>

Hi again,

I'm sorry for the super slow progress with this. Just a quick update.

On Sat, Feb 19, 2022 at 01:39:33AM +0100, Samuel Čavoj wrote:
> Hi
> 
> sorry about the delay.
> 
> On 2022-01-24 10:23, Heikki Krogerus wrote:
> > On Sat, Jan 22, 2022 at 12:21:29AM +0000, Samuel Čavoj wrote:
> > > Hi Heikki,
> > > 
> > > do you think we could get this back on track somehow? I'm not sure
> > > what to
> > > try next, do you have any ideas? Are there any tools to try and
> > > trace what
> > > the Windows driver does? Either from within Windows itself or
> > > intercept it
> > > somehow externally -- a hypervisor approach? Are there any tools
> > > developed
> > > for this purpose? I wasn't really able to find much.
> > 
> > I don't have any ideas right now, but I'll try to think of something
> > that we could try. I'll also see if I can get my hands on one of those
> > Asus Zenbook laptops. It was a Zenbook 13, right?
> 
> Yup, it's a Zenbook 13 OLED (UM325).

So, I'm not able to get one of those unfortunately.

> > Did you try to see what happens if you don't reset the "PPM"?
> 
> No difference, as far as I can tell. I used the patch below to
> get more output. This is right after boot, in the initramfs:
> 
> [    0.787887] ucsi_acpi USBC000:00: hi ucsi here
> [    0.787893] ucsi_acpi USBC000:00: skipping reset
> [    0.787894] ucsi_acpi USBC000:00: enable basic notifications
> [    0.813169] ucsi_acpi USBC000:00: got notification:
> [    0.814386] ucsi_acpi USBC000:00:     checking ua->flags: 2, cci: 0
> [    1.859334] ucsi_acpi USBC000:00: PPM init failed (-110)
> 
> Same output after cold boot, reboot from linux and reboot from windows.

Based on that output, there is a notification, and I'm assuming that
notification is for the command completion. But CCI is 0?

That could be because the mailbox in memory is not getting
synchronised for some reason, but it could also mean that the EC
firmware is really not writing anything to the CCI. Both cases
probable mean we are missing some extra step that Windows is doing,
but what... I have no idea.

thanks,

-- 
heikki

  reply	other threads:[~2022-03-24  9:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23 18:06 How to proceed: usci_acpi: PPM init failed (-110) Samuel Čavoj
2021-08-24 10:24 ` Heikki Krogerus
     [not found]   ` <20210824164942.6pakfzf2crnxes7w@fastboi.localdomain>
2021-08-25  8:02     ` Heikki Krogerus
2021-08-25  9:21       ` Samuel Čavoj
2021-08-26  7:53         ` Heikki Krogerus
2021-08-26 11:41           ` Samuel Čavoj
2022-01-22  0:21             ` Samuel Čavoj
2022-01-24  9:23               ` Heikki Krogerus
2022-02-19  0:39                 ` Samuel Čavoj
2022-03-24  9:45                   ` Heikki Krogerus [this message]
2022-12-22 20:18                     ` Samuel Čavoj
2023-01-02 10:09                       ` Heikki Krogerus
2023-01-09 11:08                         ` 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=Yjw9n5FXHMp8TpsM@kuha.fi.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=samuel@cavoj.net \
    /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;
as well as URLs for NNTP newsgroup(s).