From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Yauhen Kharuzhy <jekhor@gmail.com>
Cc: Darren Hart <dvhart@infradead.org>,
platform-driver-x86@vger.kernel.org,
Hans de Goede <hdegoede@redhat.com>,
linux-kernel@vger.kernel.org,
Andy Shevchenko <andy@infradead.org>
Subject: Re: [PATCH v2 1/1] platform/x86/intel_cht_int33fe: Split code to USB TypeB and TypeC variants
Date: Wed, 18 Sep 2019 14:38:35 +0300 [thread overview]
Message-ID: <20190918113835.GA16243@kuha.fi.intel.com> (raw)
In-Reply-To: <20190917194507.14771-2-jekhor@gmail.com>
On Tue, Sep 17, 2019 at 10:45:07PM +0300, Yauhen Kharuzhy wrote:
> Existing intel_cht_int33fe ACPI pseudo-device driver assumes that
> hardware has TypeC connector and register related devices described as
> I2C connections in the _CRS resource.
>
> There is at least one hardware (Lenovo Yoga Book YB1-91L/F) with micro
> USB B connector exists. It has INT33FE device in the DSDT table but
> there are only two I2C connection described: PMIC and BQ27452 battery
> fuel gauge.
>
> Splitting existing INT33FE driver allow to maintain code for USB type B
> (AB) connector variant separately and make it simpler.
Sorry, but "Type B" is even more confusing here. Type B refers to the
Standard-B USB connector, so _not_ the micro connector family. You can
check the connector definitions from the latest USB 3.2 specification.
The standard-b definition goes something like this:
"The standard _Type-B_ connector defined by the USB x specification."
Note that all the five supported connectors are listed in ch5
"Mechanical":
Standard-A
Standard-B
Micro-B
Micro-AB
Type-C
So what was the problem with names that refer to the micro connector
family, for example "micro-ab" or "micro-b"?
thanks,
--
heikki
next prev parent reply other threads:[~2019-09-18 11:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 19:45 [PATCH v2 0/1] intel_cht_int33fe: Split code to USB TypeB and TypeC variants Yauhen Kharuzhy
2019-09-17 19:45 ` [PATCH v2 1/1] platform/x86/intel_cht_int33fe: " Yauhen Kharuzhy
2019-09-18 9:20 ` Hans de Goede
2019-09-18 11:42 ` Yauhen Kharuzhy
2019-09-18 20:12 ` Hans de Goede
2019-09-18 20:33 ` Yauhen Kharuzhy
2019-09-18 22:11 ` Yauhen Kharuzhy
2019-09-18 11:38 ` Heikki Krogerus [this message]
2019-09-18 11:52 ` Yauhen Kharuzhy
2019-09-18 12:53 ` Hans de Goede
2019-09-18 13:07 ` Andy Shevchenko
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=20190918113835.GA16243@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=hdegoede@redhat.com \
--cc=jekhor@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox