All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh+dt@kernel.org>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" 
	<linux-arm-kernel@lists.infradead.org>,
	linux-clk <linux-clk@vger.kernel.org>,
	linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Ryder Lee <ryder.lee@mediatek.com>,
	Frank Rowand <frowand.list@gmail.com>
Subject: Re: [PATCH 1/4] of/device: Add a way to probe drivers by match data
Date: Tue, 6 Nov 2018 14:44:52 -0600	[thread overview]
Message-ID: <CAL_JsqLvKWcJUYDyWOg3rMeEWv7JV4zw7-YkOUWiL5rfXgVRvQ@mail.gmail.com> (raw)
In-Reply-To: <20181106183609.207702-2-sboyd@kernel.org>

On Tue, Nov 6, 2018 at 12:36 PM Stephen Boyd <sboyd@kernel.org> wrote:
>
> We have a handful of clk drivers that have a collection of slightly
> variant device support keyed off of the compatible string. In each of
> these drivers, we demux the variant and then call the "real" probe
> function based on whatever is stored in the match data for that
> compatible string. Let's generalize this function so that it can be
> re-used as the platform_driver probe function directly.

This looks really hacky to me. It sounds kind of general, but really
only works if we have match data that's a single function and we lose
any type checking on the function. What about things other than
platform devices?

Rob

WARNING: multiple messages have this Message-ID (diff)
From: robh+dt@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] of/device: Add a way to probe drivers by match data
Date: Tue, 6 Nov 2018 14:44:52 -0600	[thread overview]
Message-ID: <CAL_JsqLvKWcJUYDyWOg3rMeEWv7JV4zw7-YkOUWiL5rfXgVRvQ@mail.gmail.com> (raw)
In-Reply-To: <20181106183609.207702-2-sboyd@kernel.org>

On Tue, Nov 6, 2018 at 12:36 PM Stephen Boyd <sboyd@kernel.org> wrote:
>
> We have a handful of clk drivers that have a collection of slightly
> variant device support keyed off of the compatible string. In each of
> these drivers, we demux the variant and then call the "real" probe
> function based on whatever is stored in the match data for that
> compatible string. Let's generalize this function so that it can be
> re-used as the platform_driver probe function directly.

This looks really hacky to me. It sounds kind of general, but really
only works if we have match data that's a single function and we lose
any type checking on the function. What about things other than
platform devices?

Rob

  reply	other threads:[~2018-11-06 20:45 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06 18:36 [PATCH 0/4] Simplify mediatek clk driver probes Stephen Boyd
2018-11-06 18:36 ` Stephen Boyd
2018-11-06 18:36 ` [PATCH 1/4] of/device: Add a way to probe drivers by match data Stephen Boyd
2018-11-06 18:36   ` Stephen Boyd
2018-11-06 20:44   ` Rob Herring [this message]
2018-11-06 20:44     ` Rob Herring
2018-11-06 20:44     ` Rob Herring
2018-11-07 18:37     ` Stephen Boyd
2018-11-07 18:37       ` Stephen Boyd
2018-11-07 18:37       ` Stephen Boyd
2018-11-09  9:56       ` Geert Uytterhoeven
2018-11-09  9:56         ` Geert Uytterhoeven
2018-11-09  9:56         ` Geert Uytterhoeven
2018-11-09 16:59         ` Stephen Boyd
2018-11-09 16:59           ` Stephen Boyd
2018-11-09 16:59           ` Stephen Boyd
2018-11-09 19:18           ` Geert Uytterhoeven
2018-11-09 19:18             ` Geert Uytterhoeven
2018-11-09 19:18             ` Geert Uytterhoeven
2018-11-30  0:28       ` Stephen Boyd
2018-11-30  0:28         ` Stephen Boyd
2018-11-30  0:28         ` Stephen Boyd
2018-11-30  1:01         ` Rob Herring
2018-11-30  1:01           ` Rob Herring
2018-11-30  1:01           ` Rob Herring
2018-11-30  7:03           ` Stephen Boyd
2018-11-30  7:03             ` Stephen Boyd
2018-11-30  7:03             ` Stephen Boyd
2018-11-08  8:29   ` Matthias Brugger
2018-11-08  8:29     ` Matthias Brugger
2018-11-08 17:58     ` Stephen Boyd
2018-11-08 17:58       ` Stephen Boyd
2018-11-09 10:29       ` Matthias Brugger
2018-11-09 10:29         ` Matthias Brugger
2018-11-09 10:36         ` Geert Uytterhoeven
2018-11-09 10:36           ` Geert Uytterhoeven
2018-11-09 10:36           ` Geert Uytterhoeven
2018-11-09 16:30           ` Rob Herring
2018-11-09 16:30             ` Rob Herring
2018-11-09 16:30             ` Rob Herring
2018-11-09 16:56           ` Frank Rowand
2018-11-09 16:56             ` Frank Rowand
2018-11-09 16:56             ` Frank Rowand
2018-11-06 18:36 ` [PATCH 2/4] clk: mediatek: Convert to platform_driver_probe_by_match_data() Stephen Boyd
2018-11-06 18:36   ` Stephen Boyd
2018-11-06 18:36 ` [PATCH 3/4] clk: mediatek: Drop THIS_MODULE from platform_driver Stephen Boyd
2018-11-06 18:36   ` Stephen Boyd
2018-11-06 18:36 ` [PATCH 4/4] clk: mediatek: Simplify single driver probes Stephen Boyd
2018-11-06 18:36   ` Stephen Boyd

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=CAL_JsqLvKWcJUYDyWOg3rMeEWv7JV4zw7-YkOUWiL5rfXgVRvQ@mail.gmail.com \
    --to=robh+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=ryder.lee@mediatek.com \
    --cc=sboyd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.