linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hector Martin <marcan@marcan.st>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sven Peter <sven@svenpeter.dev>
Cc: "Hector Martin" <marcan@marcan.st>,
	"Guido Günther" <agx@sigxcpu.org>,
	"Alyssa Rosenzweig" <alyssa@rosenzweig.io>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH RESEND 0/2] usb: typec: tipd: Fixes for Apple M1 (CD321X) support
Date: Sat, 20 Nov 2021 12:07:15 +0900	[thread overview]
Message-ID: <20211120030717.84287-1-marcan@marcan.st> (raw)

Hi folks,

These two fixes make tipd work properly on Apple M1 devices, in
particular in the case where the bootloader hasn't initialized
the controllers yet.

We normally do it in m1n1 (so the machine can charge and so bootloaders
get working USB without needing this driver), but that was causing this
codepath to never get properly exercised, so we never caught it. I
noticed on the new machines with 3+1 ports, since m1n1 was only
initializing 2 and the other 2 were failing to initialize.

No changes since the previous version, just updating the commit tags.

Hector Martin (2):
  usb: typec: tipd: Fix typo in cd321x_switch_power_state
  usb: typec: tipd: Fix initialization sequence for cd321x

 drivers/usb/typec/tipd/core.c | 35 +++++++++++++++++------------------
 1 file changed, 17 insertions(+), 18 deletions(-)

-- 
2.33.0


             reply	other threads:[~2021-11-20  3:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-20  3:07 Hector Martin [this message]
2021-11-20  3:07 ` [PATCH RESEND 1/2] usb: typec: tipd: Fix typo in cd321x_switch_power_state Hector Martin
2021-11-20  3:07 ` [PATCH RESEND 2/2] usb: typec: tipd: Fix initialization sequence for cd321x Hector Martin

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=20211120030717.84287-1-marcan@marcan.st \
    --to=marcan@marcan.st \
    --cc=agx@sigxcpu.org \
    --cc=alyssa@rosenzweig.io \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sven@svenpeter.dev \
    /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).