Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932255AbbGJMyW (ORCPT ); Fri, 10 Jul 2015 08:54:22 -0400 Received: from mail-wi0-f179.google.com ([209.85.212.179]:38838 "EHLO mail-wi0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932154AbbGJMyO (ORCPT ); Fri, 10 Jul 2015 08:54:14 -0400 MIME-Version: 1.0 In-Reply-To: <4797404.Tr5H8KsQkK@vostro.rjw.lan> References: <1435676108-20590-1-git-send-email-tomeu.vizoso@collabora.com> <1435676108-20590-11-git-send-email-tomeu.vizoso@collabora.com> <4797404.Tr5H8KsQkK@vostro.rjw.lan> From: Tomeu Vizoso Date: Fri, 10 Jul 2015 14:53:53 +0200 X-Google-Sender-Auth: gVpkZC60TP-cKpTykej27OEn4tI Message-ID: Subject: Re: [PATCH v1 10/10] core: platform: use fwnode_driver_match_device() To: "Rafael J. Wysocki" Cc: "linux-kernel@vger.kernel.org" , Mark Brown , Greg Kroah-Hartman Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2600 Lines: 68 On 2 July 2015 at 01:46, Rafael J. Wysocki wrote: > 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 > > This one should be part of the other set IMO. Yeah, I wasn't sure about it myself, but in any case the other series won't depend on this patch any more because I have moved the match delay into platform.c. I plan though to resend this with Rob's comments addressed in the next revision, so they can be taken if they are seen worthy in themselves. > Or please just combine the two sets so it is more clear what the new helpers > are intended for. Sorry about that, I did the split because Mark suggested so in the previous review round. I understand that depending on each person's workflow it may be more convenient in one way or the other, so I'm not sure I can find a way that fits everybody's preferences. Thanks, Tomeu >> --- >> >> 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. > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/