[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230526131434.46920-1-heikki.krogerus@linux.intel.com>
Date: Fri, 26 May 2023 16:14:32 +0300
From: Heikki Krogerus <heikki.krogerus@...ux.intel.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Bjorn Andersson <andersson@...nel.org>,
chrome-platform@...ts.linux.dev, linux-usb@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH v2 0/2] usb: typec: mux: Remove the "svid" device property checks
Hi,
The comment in the first patch is now fixed as requested by Bjorn. No
other changes compared to v1.
Original message:
The background for this change:
https://lore.kernel.org/lkml/20210726231351.655302-1-bjorn.andersson@linaro.org/
The idea with that device property was that it would allow us to
support separate mode specific switches behind a single port if
necessary.
Although, I guess it is still possible that we could have that kind of
separate mode switches, especially now that the mode switch represents
a kind of virtual aggregate device that can be build from multiple
physical muxes (so the modes could need different "combos" of the
muxes), but now no such systems exist.
We can look at how to handle that kind of switches when/if we actually
have them, but for now, keeping the functions as simple as possible.
thanks,
Heikki Krogerus (2):
usb: typec: mux: Clean up mux_fwnode_match()
usb: typec: mux: Remove alt mode parameters from the API
drivers/platform/chrome/cros_ec_typec.c | 2 +-
drivers/soc/qcom/pmic_glink_altmode.c | 5 +-
drivers/usb/typec/class.c | 4 +-
drivers/usb/typec/mux.c | 61 ++++---------------------
include/linux/usb/typec_mux.h | 11 ++---
5 files changed, 17 insertions(+), 66 deletions(-)
--
2.39.2
Powered by blists - more mailing lists