From: Yauhen Kharuzhy <jekhor@gmail.com>
To: Darren Hart <dvhart@infradead.org>,
platform-driver-x86@vger.kernel.org,
Hans de Goede <hdegoede@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Andy Shevchenko <andy@infradead.org>,
Yauhen Kharuzhy <jekhor@gmail.com>
Subject: [PATCH v2 0/1] intel_cht_int33fe: Split code to USB TypeB and TypeC variants
Date: Tue, 17 Sep 2019 22:45:06 +0300 [thread overview]
Message-ID: <20190917194507.14771-1-jekhor@gmail.com> (raw)
Patch to support INT33FE ACPI pseudo-device on hardware with USB Type B
connector.
v2:
Instead of defining two separated modules with two separated config
options, compile {common,typeb,typec} sources into one .ko module.
Call needed variant-specific probe function based after of hardware type
detection in common code.
Yauhen Kharuzhy (1):
platform/x86/intel_cht_int33fe: Split code to USB TypeB and TypeC
variants
drivers/platform/x86/Kconfig | 14 +-
drivers/platform/x86/Makefile | 4 +
.../platform/x86/intel_cht_int33fe_common.c | 148 ++++++++++++++++++
.../platform/x86/intel_cht_int33fe_common.h | 44 ++++++
.../platform/x86/intel_cht_int33fe_typeb.c | 64 ++++++++
...ht_int33fe.c => intel_cht_int33fe_typec.c} | 79 +---------
6 files changed, 278 insertions(+), 75 deletions(-)
create mode 100644 drivers/platform/x86/intel_cht_int33fe_common.c
create mode 100644 drivers/platform/x86/intel_cht_int33fe_common.h
create mode 100644 drivers/platform/x86/intel_cht_int33fe_typeb.c
rename drivers/platform/x86/{intel_cht_int33fe.c => intel_cht_int33fe_typec.c} (83%)
--
2.20.1
next reply other threads:[~2019-09-17 19:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 19:45 Yauhen Kharuzhy [this message]
2019-09-17 19:45 ` [PATCH v2 1/1] platform/x86/intel_cht_int33fe: Split code to USB TypeB and TypeC variants 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
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=20190917194507.14771-1-jekhor@gmail.com \
--to=jekhor@gmail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=hdegoede@redhat.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