From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Mathias Nyman <mathias.nyman@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
USB <linux-usb@vger.kernel.org>
Subject: Re: [PATCH 01/12] drivers: base: Unified device connection lookup
Date: Fri, 16 Feb 2018 13:28:23 +0200 [thread overview]
Message-ID: <20180216112823.GI1480@kuha.fi.intel.com> (raw)
In-Reply-To: <ee0d4723-ab1c-85d8-e6b7-a66e1a045b02@redhat.com>
On Fri, Feb 16, 2018 at 12:21:15PM +0100, Hans de Goede wrote:
> Hi,
>
> On 16-02-18 12:00, Andy Shevchenko wrote:
> > On Fri, Feb 16, 2018 at 12:47 PM, Hans de Goede <hdegoede@redhat.com> wrote:
> > > From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> > >
> > > Several frameworks - clk, gpio, phy, pmw, etc. - maintain
> > > lookup tables for describing connections and provide custom
> > > API for handling them. This introduces a single generic
> > > lookup table and API for the connections.
> > >
> > > The motivation for this commit is centralizing the
> > > connection lookup, but the goal is to ultimately extract the
> > > connection descriptions also from firmware by using the
> > > fwnode_graph_* functions and other mechanisms that are
> > > available.
> >
> > > +void *__device_find_connection(struct device *dev, const char *con_id,
> >
> > > + void *data,
> > > + void *(*match)(struct devcon *con, int ep,
> > > + void *data))
> >
> > Perhaps swap them, since data is dependent parameter to match.
>
> The pattern of having the data before the callback function is not
> unheard of in the kernel. Changing this now feels like needless
> churn, but if there is a strong preference for this then we can
> fix this for v2.
>
> Heikki, do you want me to take care of minor changes like this for v2?
Yes, please do if you don't mind. I would appreciate it.
I'll be on vacation next week.
Thanks,
--
heikki
next prev parent reply other threads:[~2018-02-16 11:28 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 10:47 [PATCH 00/12] USB Type-C device-connection, mux and switch support Hans de Goede
2018-02-16 10:47 ` [PATCH 01/12] drivers: base: Unified device connection lookup Hans de Goede
2018-02-16 11:00 ` Andy Shevchenko
2018-02-16 11:21 ` Hans de Goede
2018-02-16 11:28 ` Heikki Krogerus [this message]
2018-02-16 10:47 ` [PATCH 02/12] usb: typec: Start using ERR_PTR Hans de Goede
2018-02-16 11:07 ` Andy Shevchenko
2018-02-16 11:21 ` Hans de Goede
2018-02-16 10:47 ` [PATCH 03/12] usb: typec: API for controlling USB Type-C Multiplexers Hans de Goede
2018-02-16 14:00 ` Andy Shevchenko
2018-02-25 12:13 ` Hans de Goede
2018-02-16 10:47 ` [PATCH 04/12] usb: common: Small class for USB role switches Hans de Goede
2018-02-16 14:07 ` Andy Shevchenko
2018-02-16 14:22 ` Heikki Krogerus
2018-02-19 9:32 ` Hans de Goede
2018-02-25 12:16 ` Hans de Goede
2018-02-16 18:33 ` Randy Dunlap
2018-02-25 12:16 ` Hans de Goede
2018-02-16 10:47 ` [PATCH 05/12] usb: typec: tcpm: Set USB role switch to device mode when configured as such Hans de Goede
2018-02-16 13:19 ` Heikki Krogerus
2018-02-16 10:47 ` [PATCH 06/12] usb: typec: tcpm: Use new Type-C switch/mux and usb-role-switch functions Hans de Goede
2018-02-16 13:20 ` Heikki Krogerus
2018-02-16 10:47 ` [PATCH 07/12] xhci: Add option to get next extended capability in list by passing id = 0 Hans de Goede
2018-02-16 13:21 ` Heikki Krogerus
2018-02-16 10:47 ` [PATCH 08/12] xhci: Add Intel extended cap / otg phy mux handling Hans de Goede
2018-02-16 13:32 ` Heikki Krogerus
2018-02-16 13:53 ` Andy Shevchenko
2018-02-25 13:01 ` Hans de Goede
2018-02-16 10:47 ` [PATCH 09/12] usb: roles: Add Intel XHCI USB role switch driver Hans de Goede
2018-02-16 13:38 ` Heikki Krogerus
2018-02-25 12:11 ` Hans de Goede
2018-02-16 13:47 ` Andy Shevchenko
2018-02-25 13:29 ` Hans de Goede
2018-02-16 10:47 ` [PATCH 10/12] usb: typec: driver for Pericom PI3USB30532 Type-C cross switch Hans de Goede
2018-02-16 13:33 ` Andy Shevchenko
2018-02-16 13:43 ` Heikki Krogerus
2018-02-16 10:47 ` [PATCH 11/12] platform/x86: intel_cht_int33fe: Add device connections for the Type-C port Hans de Goede
2018-02-16 13:10 ` Andy Shevchenko
2018-02-16 13:43 ` Heikki Krogerus
2018-02-16 10:47 ` [PATCH 12/12] extcon: axp288: Set USB role where necessary Hans de Goede
2018-02-16 13:19 ` Andy Shevchenko
2018-02-25 13:49 ` Hans de Goede
2018-02-16 13:45 ` Heikki Krogerus
2018-02-16 13:36 ` [PATCH 00/12] USB Type-C device-connection, mux and switch support Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2018-02-16 10:43 [PATCH 0/12] " Hans de Goede
2018-02-16 10:43 ` [PATCH 01/12] drivers: base: Unified device connection lookup 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=20180216112823.GI1480@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=cw00.choi@samsung.com \
--cc=dvhart@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=myungjoo.ham@samsung.com \
--cc=platform-driver-x86@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