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 2/8] usb: typec: Rationalize the API for the muxes
Date: Mon, 28 Jan 2019 17:28:30 +0200 [thread overview]
Message-ID: <20190128152830.GH7262@kuha.fi.intel.com> (raw)
In-Reply-To: <CAHp75VctbnJcLdTrGfPju708StpNPzmzTCBb-B-gmKZzOQwteg@mail.gmail.com>
On Mon, Jan 28, 2019 at 11:50:31AM +0200, Andy Shevchenko wrote:
> On Fri, Jan 25, 2019 at 3:18 PM Heikki Krogerus
> <heikki.krogerus@linux.intel.com> wrote:
> >
> > We can replace the second parameter that is passed to the
> > typec_mux_get() function with alt mode description
> > structure, and simply pass NULL with accessory modes.
> >
> > With accessory modes there is no need for additional
> > identification (in practice the accessory mode can only be
> > Audio Accessory if muxing is needed), only with alternate
> > modes we need to identify the exact alternate mode.
>
> > +struct typec_mux *typec_mux_get(struct device *dev,
> > + const struct typec_altmode_desc *desc)
> > {
> > struct typec_mux *mux;
> >
> > mutex_lock(&mux_lock);
> > - mux = device_connection_find_match(dev, name, NULL, typec_mux_match);
> > + mux = device_connection_find_match(dev, "typec-mux", (void *)desc,
> > + typec_mux_match);
>
> Not related to this series, but shouldn't
> device_connection_find_match() be improved to avoid dropping const
> qualifier?
I'll see if we can do that already.
thanks,
--
heikki
next prev parent reply other threads:[~2019-01-28 15:28 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 [this message]
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
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=20190128152830.GH7262@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