mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Chen Yu <chenyu56@huawei.com>, Jun Li <jun.li@nxp.com>,
	Hans de Goede <hdegoede@redhat.com>,
	USB <linux-usb@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/8] usb: typec: mux: Find the muxes by also matching against the device node
Date: Mon, 28 Jan 2019 17:46:18 +0200	[thread overview]
Message-ID: <20190128154618.GI7262@kuha.fi.intel.com> (raw)
In-Reply-To: <CAHp75VfG9LDOfz9K0jYvGOK=j1uDmyg=eeRMur7hnw2rF9qx+Q@mail.gmail.com>

On Mon, Jan 28, 2019 at 11:53:54AM +0200, Andy Shevchenko wrote:
> On Fri, Jan 25, 2019 at 3:17 PM Heikki Krogerus
> <heikki.krogerus@linux.intel.com> wrote:
> >
> > When the connections are defined in firmware, struct
> > device_connection will have the fwnode member pointing to
> > the device node (struct fwnode_handle) of the requested
> > device, and the endpoint will not be used at all in that
> > case.
> 
> >  static void *typec_mux_match(struct device_connection *con, int ep, void *data)
> >  {
> > +       const struct typec_altmode_desc *desc = data;
> >         struct typec_mux *mux;
> 
> > +       bool match = !con->id;
> 
> I don't see how this assignment is used.

That definitely deserves a comment at least.

This series adds support for the "device graph" to the device
connection API, but it is also possible to describe connections with
normal references (fwnode_property_get_reference_args()). With normal
references we don't need to do any extra identification like we do
with device graph.

The idea is to supply the connection id only if it has not been
"consumed" already (device graph case). If it has been "consumed", we
know there is no need for any extra connection identification (normal
references), and we can jump straight to the next stage -> find the
mux..

> > +       size_t nval;
> > +       u16 *val;
> > +       int i;
> > +
> > +       if (!con->fwnode) {
> > +               list_for_each_entry(mux, &mux_list, entry)
> > +                       if (!strcmp(con->endpoint[ep], dev_name(mux->dev)))
> > +                               return mux;
> > +               return ERR_PTR(-EPROBE_DEFER);
> > +       }
> > +
> > +       if (match)
> > +               goto find_mux;

..here.

I'll change this so that the match variable is introduced without
setting default value. Instead, how about this:

        /*
         * Check has the identifier already been "consumed". If it
         * has, no need to do any extra connection identification.
         */
        match = !con->id;
        if (match)
                goto find_mux;

thanks,

-- 
heikki

  reply	other threads:[~2019-01-28 15:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-25 13:15 [PATCH 0/8] device connection: Add support for device graphs Heikki Krogerus
2019-01-25 13:15 ` [PATCH 1/8] platform/x86: intel_cht_int33fe: Remove connection for the alt mode mux Heikki Krogerus
2019-01-28  9:45   ` Andy Shevchenko
2019-01-28 10:44     ` Hans de Goede
2019-01-28 15:27       ` Heikki Krogerus
2019-01-31 10:04         ` Hans de Goede
2019-01-25 13:15 ` [PATCH 2/8] usb: typec: Rationalize the API for the muxes Heikki Krogerus
2019-01-28  9:50   ` Andy Shevchenko
2019-01-28 15:28     ` Heikki Krogerus
2019-01-25 13:15 ` [PATCH 3/8] device connection: Add fwnode member to struct device_connection Heikki Krogerus
2019-01-25 13:15 ` [PATCH 4/8] usb: typec: mux: Find the muxes by also matching against the device node Heikki Krogerus
2019-01-28  9:53   ` Andy Shevchenko
2019-01-28 15:46     ` Heikki Krogerus [this message]
2019-01-28 16:17       ` Andy Shevchenko
2019-01-25 13:15 ` [PATCH 5/8] usb: roles: " Heikki Krogerus
2019-01-25 13:15 ` [PATCH 6/8] usb: typec: Find the ports " Heikki Krogerus
2019-01-25 13:15 ` [PATCH 7/8] device connection: Prepare support for firmware described connections Heikki Krogerus
2019-01-25 13:15 ` [PATCH 8/8] device connection: Find device connections also from device graphs Heikki Krogerus
2019-01-28  9:58   ` Andy Shevchenko

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=20190128154618.GI7262@kuha.fi.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=chenyu56@huawei.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

Powered by JetHome