From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id F0307C433F5 for ; Mon, 21 Feb 2022 17:51:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231249AbiBURvm (ORCPT ); Mon, 21 Feb 2022 12:51:42 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:55908 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231579AbiBURth (ORCPT ); Mon, 21 Feb 2022 12:49:37 -0500 Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E12A3117A; Mon, 21 Feb 2022 09:47:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1645465634; x=1677001634; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=xpY7J7nzp9IuhJIMZ851JicROXwhZoI/6l0O+HJAEo8=; b=GBRxerXbwmzIP4iSg2vDwF1rgS+bXrKjjW86h+5XXOKyFr2M7xlV77Tr UDWFGbejeu4bBU8U+R5NxXN5Wewuw0gFzqxjjd9d8EgLqLjryN73UMXkJ ms/UQSoWuKBsDIca70N3xbJKlAmS6wCfN+hapGXJthbZq8tP7iYkAjmjs pC/Pbm0jQ6N/+F4hjYCRHwuJgxSfhRKszd/GpHGtafe51y/kqDQhL0t1l qd1AIR4CY6f4RV6Z8r8N6o9P3FHpUlRKyrRYD/nNpZfa9Gfe7QU9b2eWt 8GoNf901lpihBfs0hPbYrbrlxj3Dw1AcbTwPfBUkuuxXoaivgGwCm2KnO g==; X-IronPort-AV: E=McAfee;i="6200,9189,10265"; a="235089559" X-IronPort-AV: E=Sophos;i="5.88,386,1635231600"; d="scan'208";a="235089559" Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Feb 2022 09:47:10 -0800 X-IronPort-AV: E=Sophos;i="5.88,386,1635231600"; d="scan'208";a="505162234" Received: from smile.fi.intel.com ([10.237.72.59]) by orsmga002-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Feb 2022 09:47:05 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.95) (envelope-from ) id 1nMClJ-006rzr-6u; Mon, 21 Feb 2022 19:46:13 +0200 Date: Mon, 21 Feb 2022 19:46:12 +0200 From: Andy Shevchenko To: =?iso-8859-1?Q?Cl=E9ment_L=E9ger?= Cc: Daniel Scally , Heikki Krogerus , Sakari Ailus , Greg Kroah-Hartman , "Rafael J . Wysocki" , Wolfram Sang , Peter Rosin , Russell King , Andrew Lunn , Heiner Kallweit , "David S . Miller" , Jakub Kicinski , linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, linux-i2c@vger.kernel.org, netdev@vger.kernel.org, Thomas Petazzoni , Alexandre Belloni Subject: Re: [RFC 02/10] property: add fwnode_get_match_data() Message-ID: References: <20220221162652.103834-1-clement.leger@bootlin.com> <20220221162652.103834-3-clement.leger@bootlin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220221162652.103834-3-clement.leger@bootlin.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-i2c@vger.kernel.org On Mon, Feb 21, 2022 at 05:26:44PM +0100, Clément Léger wrote: > Add fwnode_get_match_data() which is meant to be used as > device_get_match_data for fwnode_operations. ... > +const void *fwnode_get_match_data(const struct fwnode_handle *fwnode, > + const struct device *dev) > +{ > + const struct of_device_id *match; > + > + match = fwnode_match_node(fwnode, dev->driver->of_match_table); > + if (!match) > + return NULL; > + > + return match->data; > +} It's OF-centric API, why it has fwnode prefix? Can it leave in drivers/of instead? -- With Best Regards, Andy Shevchenko