From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Jun Li <jun.li@nxp.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] usb: typec: mux: Remove requirement for the "orientation-switch" device property
Date: Mon, 31 May 2021 11:26:14 +0300 [thread overview]
Message-ID: <YLSdptmScGo5TJ1D@kuha.fi.intel.com> (raw)
In-Reply-To: <YLSW0IoHdnzRSzUW@kuha.fi.intel.com>
On Mon, May 31, 2021 at 10:57:04AM +0300, Heikki Krogerus wrote:
> On Mon, May 31, 2021 at 10:24:35AM +0300, Heikki Krogerus wrote:
> > On Fri, May 28, 2021 at 07:26:43AM +0000, Jun Li wrote:
> > > Hi,
> > > > -----Original Message-----
> > > > From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> > > > Sent: Wednesday, May 26, 2021 11:36 PM
> > > > To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>; Hans de Goede
> > > > <hdegoede@redhat.com>; Jun Li <jun.li@nxp.com>
> > > > Cc: linux-usb@vger.kernel.org; linux-kernel@vger.kernel.org
> > > > Subject: [PATCH 2/2] usb: typec: mux: Remove requirement for the
> > > > "orientation-switch" device property
> > > >
> > > > The additional boolean device property "orientation-switch"
> > > > is not needed when the connection is described with device graph, so removing
> > > > the check and the requirement for it.
> > > >
> > > > Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> > > > ---
> > > > drivers/usb/typec/mux.c | 3 ---
> > > > 1 file changed, 3 deletions(-)
> > > >
> > > > diff --git a/drivers/usb/typec/mux.c b/drivers/usb/typec/mux.c index
> > > > e40a555724fb6..603f3e698cc0b 100644
> > > > --- a/drivers/usb/typec/mux.c
> > > > +++ b/drivers/usb/typec/mux.c
> > > > @@ -30,9 +30,6 @@ static void *typec_switch_match(struct fwnode_handle
> > > > *fwnode, const char *id, {
> > > > struct device *dev;
> > > >
> > > > - if (id && !fwnode_property_present(fwnode, id))
> > > > - return NULL;
> > > > -
> > >
> > > May this change the result of fwnode_connection_find_match()
> > > if there are multiple remote-endpoint node?
> > >
> > > After the 2 patches change, typec_switch_match() will never
> > > return NULL, so
> > >
> > > 17 static void *
> > > 18 fwnode_graph_devcon_match(struct fwnode_handle *fwnode, const char *con_id,
> > > 19 void *data, devcon_match_fn_t match)
> > > 20 {
> > > 21 struct fwnode_handle *node;
> > > 22 struct fwnode_handle *ep;
> > > 23 void *ret;
> > > 24
> > > 25 fwnode_graph_for_each_endpoint(fwnode, ep) {
> > > 26 node = fwnode_graph_get_remote_port_parent(ep);
> > > 27 if (!fwnode_device_is_available(node))
> > > 28 continue;
> > > 29
> > > 30 ret = match(node, con_id, data);// ret can't be NULL;
> > > 31 fwnode_handle_put(node);
> > > 32 if (ret) {
> > > /*
> > > * So loop will go to here and stop
> > > * checking next ep, even this ep
> > > * actually is not for typec_switch
> > > */
> > > 33 fwnode_handle_put(ep);
> > > 34 return ret;
> > > 35 }
> > > 36 }
> > > 37 return NULL;
> > > 38 }
> > >
> > > fwnode_graph_devcon_match() Will return ERR_PTR(-EPROBE_DEFER)
> > > even this ep's remote parent already probed but it's not for
> > > typec_switch.
> >
> > You are correct. With device graph I guess we really always need the
> > extra device property after all.
> >
> > So let's forget about this one.
>
> Oh no. This patch just landed into Greg's usb-next. I'll prepare the
> revert. I'm sorry about this.
Actually, if we always need that extra (boolean) device property to
identify the device class when OF graph is used, shouldn't we just do
that always in fwnode_graph_devcon_match()?
diff --git a/drivers/base/property.c b/drivers/base/property.c
index 1421e9548857b..238da64375bb1 100644
--- a/drivers/base/property.c
+++ b/drivers/base/property.c
@@ -1263,6 +1263,13 @@ fwnode_graph_devcon_match(struct fwnode_handle *fwnode, const char *con_id,
if (!fwnode_device_is_available(node))
continue;
+ /*
+ * With device graph @con_id is expected to be the name of the
+ * "device class" of the fwnode.
+ */
+ if (con_id && !fwnode_property_present(node, con_id))
+ continue;
+
ret = match(node, con_id, data);
fwnode_handle_put(node);
if (ret) {
thanks,
--
heikki
next prev parent reply other threads:[~2021-05-31 8:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 15:35 [PATCH 0/2] usb: typec: mux: a few improvements Heikki Krogerus
2021-05-26 15:35 ` [PATCH 1/2] usb: typec: mux: Use device type instead of device name for matching Heikki Krogerus
2021-05-31 7:30 ` Heikki Krogerus
2021-05-31 8:09 ` Hans de Goede
2021-05-26 15:35 ` [PATCH 2/2] usb: typec: mux: Remove requirement for the "orientation-switch" device property Heikki Krogerus
2021-05-28 7:26 ` Jun Li
2021-05-31 7:24 ` Heikki Krogerus
2021-05-31 7:57 ` Heikki Krogerus
2021-05-31 8:26 ` Heikki Krogerus [this message]
2021-05-31 11:08 ` Jun Li
2021-05-31 12:33 ` Heikki Krogerus
2021-05-26 16:38 ` [PATCH 0/2] usb: typec: mux: a few improvements Hans de Goede
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=YLSdptmScGo5TJ1D@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=jun.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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