[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180430124158.45269-1-heikki.krogerus@linux.intel.com>
Date: Mon, 30 Apr 2018 15:41:54 +0300
From: Heikki Krogerus <heikki.krogerus@...ux.intel.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Hans de Goede <hdegoede@...hat.com>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Guenter Roeck <linux@...ck-us.net>,
linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org
Subject: [PATCH 0/4] usb: typec: fixes for Cherry Trails
Hi,
I now have a GPD Win device - Intel Cherry Trail based board with
FUSB302 USB Type-C PHY - that I started using for testing my alternate
mode patches. I noticed a few dependency issues, and some other
problems with the fusb302 driver. These were the most obvious ones.
Hans, I included the patch for the xhci usb role mux to this series.
On top of these, the driver for INT34D3 (the PMIC) needs CHT GPIO
driver in order for it to work at least on GPD Win. If that is the
case with all CHT based platforms, we probable should make the driver
depend on the CHT GPIO, but I don't know if it is?
With CHT, the driver for fusb302 also depends in practice on the
extcon_intel_cht_wc extcon device. It would probable be possible to
check it in Kconfig, but I'm not proposing anything for that here
either. I wonder if that thing needs to be an extcon device at all?
Heikki Krogerus (4):
platform: x86: intel_cht_int33fe: Fix dependencies
usb: typec: tcpm: Release the role mux when exiting
usb: typec: fusb302: Fix debugfs issue
usb: roles: intel_xhci: Always allow user control
drivers/i2c/busses/Kconfig | 3 +--
drivers/platform/x86/Kconfig | 4 ++--
drivers/usb/roles/intel-xhci-usb-role-switch.c | 15 +--------------
drivers/usb/typec/fusb302/fusb302.c | 9 ++++-----
drivers/usb/typec/tcpm.c | 1 +
5 files changed, 9 insertions(+), 23 deletions(-)
--
2.17.0
Powered by blists - more mailing lists