From: "Grzegorz Alibożek" <grzegorz.alibozek@gmail.com>
To: linux-usb@vger.kernel.org,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, bastian@rieck.me,
andrew.co@free.fr, meven29@gmail.com, pchernik@gmail.com,
jorge.cep.mart@gmail.com, danielmorgan@disroot.org,
bernie@codewiz.org, saipavanchitta1998@gmail.com,
rubin@starset.net, maniette@gmail.com, nate@kde.org
Subject: Re: [RFC PATCH 0/2] usb: typec: ucsi: Check connection on resume
Date: Wed, 07 Sep 2022 23:33:06 +0200 [thread overview]
Message-ID: <4425011.LvFx2qVVIh@abyss> (raw)
In-Reply-To: <20220907115626.21976-1-heikki.krogerus@linux.intel.com>
Hi,
> Hi,
>
> I'm sending these as an RFC first because I'm not done testing.
>
> I made a small modification to my original proposal (in the bug
> report). Now also connection during suspend should be covered.
>
> I would appreciate if you guys could test these again. If everything
> works, and the bug is fixed, let me know, and I'll add your Tested-by
> tags to the patches.
>
> thanks,
>
> Heikki Krogerus (2):
> usb: typec: ucsi: Check the connection on resume
> usb: typec: ucsi: acpi: Add PM hooks
>
> drivers/usb/typec/ucsi/ucsi.c | 42 +++++++++++++++++++++---------
> drivers/usb/typec/ucsi/ucsi_acpi.c | 15 +++++++++++
> 2 files changed, 44 insertions(+), 13 deletions(-)
I have tested this patch on Lenovo T14 Gen2i with ac adapter and everything
looks good. I applied patch on linux 5.19.7.
next prev parent reply other threads:[~2022-09-07 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 11:56 [RFC PATCH 0/2] usb: typec: ucsi: Check connection on resume Heikki Krogerus
2022-09-07 11:56 ` [RFC PATCH 1/2] usb: typec: ucsi: Check the " Heikki Krogerus
2022-09-07 11:56 ` [RFC PATCH 2/2] usb: typec: ucsi: acpi: Add PM hooks Heikki Krogerus
2022-09-07 21:33 ` Grzegorz Alibożek [this message]
2022-09-08 5:01 ` [RFC PATCH 0/2] usb: typec: ucsi: Check connection on resume Bastian Rieck
2022-09-09 6:22 ` Heikki Krogerus
2022-09-16 10:46 ` Heikki Krogerus
2022-10-07 10:00 ` Bastian Rieck
2022-10-07 10:04 ` 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=4425011.LvFx2qVVIh@abyss \
--to=grzegorz.alibozek@gmail.com \
--cc=andrew.co@free.fr \
--cc=bastian@rieck.me \
--cc=bernie@codewiz.org \
--cc=danielmorgan@disroot.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jorge.cep.mart@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=maniette@gmail.com \
--cc=meven29@gmail.com \
--cc=nate@kde.org \
--cc=pchernik@gmail.com \
--cc=rubin@starset.net \
--cc=saipavanchitta1998@gmail.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;
as well as URLs for NNTP newsgroup(s).