mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v1 10/10] core: platform: use fwnode_driver_match_device()
Date: Thu, 02 Jul 2015 01:46:19 +0200	[thread overview]
Message-ID: <4797404.Tr5H8KsQkK@vostro.rjw.lan> (raw)
In-Reply-To: <1435676108-20590-11-git-send-email-tomeu.vizoso@collabora.com>

On Tuesday, June 30, 2015 04:55:08 PM Tomeu Vizoso wrote:
> Instead of calling both of_driver_match_device() and
> acpi_driver_match_device(), call fwnode_driver_match_device() which
> should be able to sort out what firmware describes the device in
> question.
> 
> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>

This one should be part of the other set IMO.

Or please just combine the two sets so it is more clear what the new helpers
are intended for.


> ---
> 
>  drivers/base/platform.c | 8 ++------
>  1 file changed, 2 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/base/platform.c b/drivers/base/platform.c
> index 063f0ab..a7e7757 100644
> --- a/drivers/base/platform.c
> +++ b/drivers/base/platform.c
> @@ -843,12 +843,8 @@ static int platform_match(struct device *dev, struct device_driver *drv)
>  	if (pdev->driver_override)
>  		return !strcmp(pdev->driver_override, drv->name);
>  
> -	/* Attempt an OF style match first */
> -	if (of_driver_match_device(dev, drv))
> -		return 1;
> -
> -	/* Then try ACPI style match */
> -	if (acpi_driver_match_device(dev, drv))
> +	/* Attempt a firmware match first */
> +	if (fwnode_driver_match_device(dev, drv))
>  		return 1;
>  
>  	/* Then try to match against the id table */
> 

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  reply	other threads:[~2015-07-01 23:20 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 14:54 [PATCH v1 0/10] Fixes and API additions for firmware nodes Tomeu Vizoso
2015-06-30 14:54 ` [PATCH v1 01/10] of/platform: Set fwnode field for new devices Tomeu Vizoso
2015-06-30 18:24   ` Grant Likely
2015-07-01 23:32   ` Rafael J. Wysocki
2015-06-30 14:55 ` [PATCH v1 02/10] i2c: core: Have clients point to their firmware nodes Tomeu Vizoso
2015-07-31 10:36   ` Wolfram Sang
2015-08-06 14:17     ` Tomeu Vizoso
2015-08-06 21:06       ` Wolfram Sang
2015-06-30 14:55 ` [PATCH v1 03/10] mfd: Have child devices " Tomeu Vizoso
2015-06-30 18:24   ` Grant Likely
2015-07-01  7:36   ` Lee Jones
2015-07-01 23:33   ` Rafael J. Wysocki
2015-06-30 14:55 ` [PATCH v1 04/10] device property: add fwnode_get_parent() Tomeu Vizoso
2015-07-01 23:38   ` Rafael J. Wysocki
2015-06-30 14:55 ` [PATCH v1 05/10] device property: add fwnode_get_name() Tomeu Vizoso
2015-06-30 18:26   ` Grant Likely
2015-07-01 23:38   ` Rafael J. Wysocki
2015-07-22 11:53     ` Tomeu Vizoso
2015-06-30 14:55 ` [PATCH v1 06/10] ACPI / scan: Add acpi_dev_get_next_child() Tomeu Vizoso
2015-07-01 23:39   ` Rafael J. Wysocki
2015-06-30 14:55 ` [PATCH v1 07/10] device property: Add fwnode_get_next_child_node() Tomeu Vizoso
2015-07-01 23:40   ` Rafael J. Wysocki
2015-06-30 14:55 ` [PATCH v1 08/10] device property: add fwnode_is_compatible() Tomeu Vizoso
2015-06-30 18:28   ` Grant Likely
2015-07-01 23:44   ` Rafael J. Wysocki
2015-06-30 14:55 ` [PATCH v1 09/10] device: property: add fwnode_driver_match_device() Tomeu Vizoso
2015-06-30 18:32   ` Grant Likely
2015-07-01 23:45   ` Rafael J. Wysocki
2015-06-30 14:55 ` [PATCH v1 10/10] core: platform: use fwnode_driver_match_device() Tomeu Vizoso
2015-07-01 23:46   ` Rafael J. Wysocki [this message]
2015-07-10 12:53     ` Tomeu Vizoso
2015-07-11  2:47       ` Rafael J. Wysocki
2015-07-13  6:55         ` Tomeu Vizoso
2015-06-30 15:32 ` [PATCH v1 0/10] Fixes and API additions for firmware nodes Rafael J. Wysocki

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=4797404.Tr5H8KsQkK@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomeu.vizoso@collabora.com \
    /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

all inboxes | Powered by JetHome®