From patchwork Fri May 26 13:14:32 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Heikki Krogerus X-Patchwork-Id: 685987 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 511FFC7EE2C for ; Fri, 26 May 2023 13:14:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243569AbjEZNOf (ORCPT ); Fri, 26 May 2023 09:14:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53808 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243561AbjEZNOe (ORCPT ); Fri, 26 May 2023 09:14:34 -0400 Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6B7A513A; Fri, 26 May 2023 06:14:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1685106873; x=1716642873; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=P3aDrbgWsczzMF6L7QMUDAva/xddidPwaE1GdyMC7Bk=; b=Qgim3uNW1dZ4pBgLuymhmrlE9DdrSZj5xSLr7T1XTGCiyWfFBfihC5Ri t8l4ecrTmNMcFYjFhFQvS46XfOq7kUJgImbR3c9heJMh4SxqtsosW0ujt ggB9bbefuQHOfsi4jG8pVLXbeB2ohkloiv/N8MR5LcXsu7WxKtMRv5jkM YMkeKxxT2znhlj0tbk6K6l5ooUheAmw9gvQhfZ0Myd/hDIdnWuFVGZxdc YJsyTc9jXJ0FW8kOcuANyZzVrfACLzJ25yqeF2vF+JU+axA0ZCnelif2o eTNyzTW3xv3pIqm9lEB3lloqvRczUbK+Hz2ifMhSfdyKbc9EQO6yGVqLn Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10722"; a="419955091" X-IronPort-AV: E=Sophos;i="6.00,194,1681196400"; d="scan'208";a="419955091" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 May 2023 06:14:32 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10722"; a="849555262" X-IronPort-AV: E=Sophos;i="6.00,194,1681196400"; d="scan'208";a="849555262" Received: from black.fi.intel.com (HELO black.fi.intel.com.) ([10.237.72.28]) by fmsmga001.fm.intel.com with ESMTP; 26 May 2023 06:14:30 -0700 From: Heikki Krogerus To: Greg Kroah-Hartman Cc: Bjorn Andersson , chrome-platform@lists.linux.dev, linux-usb@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 0/2] usb: typec: mux: Remove the "svid" device property checks Date: Fri, 26 May 2023 16:14:32 +0300 Message-Id: <20230526131434.46920-1-heikki.krogerus@linux.intel.com> X-Mailer: git-send-email 2.39.2 MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org 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(-)