Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: 76/cb8AcpFxHaGYevWn1WqdOhmSv+CVW87ay8WMlyINDJ1OKYlDerFiH9YMk/js2fEZehq5LJs
 +Tu0Z/Iowj7g==
IronPort-SDR: 1ydds1PjwrCI9xbX9aY0Xij9f0HuFGXd6BaPte1ufpb20YGsSZIyndjNUb7j9A6ZswRXlyRbeZ
 fh7z0fr3pvpA==
From:   Heikki Krogerus <heikki.krogerus@linux.intel.com>
To:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Hans de Goede <hdegoede@redhat.com>, Li Jun <jun.li@nxp.com>
Cc:     linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] usb: typec: mux: a few improvements
Date:   Wed, 26 May 2021 18:35:46 +0300
Message-Id: <20210526153548.61276-1-heikki.krogerus@linux.intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Hi,

The first patch should be trivial cleanup, but in the second one I'm
removing the condition that in practice forces the orientation switch
to always have the device property named "orientation-switch". This
change only impacts connections described with device graph since only
in that case the callback function is supplied with the "id" parameter
which is the first part of the condition (if the id is not supplied,
the function also does not expect the device property to exist).

But when the connection between the connector and the switch is
described with device graph, I don't see any need for that device
property. Therefore let's just remove the condition and the
requirement for the device property with it.

thanks,

Heikki Krogerus (2):
  usb: typec: mux: Use device type instead of device name for matching
  usb: typec: mux: Remove requirement for the "orientation-switch"
    device property

 drivers/usb/typec/mux.c | 29 ++++++++++-------------------
 drivers/usb/typec/mux.h |  6 ++++++
 2 files changed, 16 insertions(+), 19 deletions(-)

-- 
2.30.2