[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230223203713.hcse3mkbq3m6sogb@skbuf>
Date: Thu, 23 Feb 2023 22:37:13 +0200
From: Vladimir Oltean <vladimir.oltean@....com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Daniel Scally <djrscally@...il.com>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Implementation of fwnode_operations :: device_get_match_data() for
software nodes?
Hi,
I have a need to instantiate a driver written for OF which calls
device_get_match_data(dev) to get various information based on the
compatible string.
I am creating a software node based on the following properties:
struct property_entry props[2] = {
PROPERTY_ENTRY_STRING("compatible", compatible),
{},
};
(I see I'm not the only one doing this, some drivers/platform/x86/x86-android-tablets.c
and drivers/platform/chrome/chromeos_laptop.c also do it)
and the driver in question does begin to probe, but its match_data is
NULL, because the operation from the title isn't implemented for
software nodes. So probing ultimately fails.
Is there some sort or reason why this doesn't exist, other than a lack
of need?
Can someone please help me with an implementation of this feature?
Thanks,
Vladimir
Powered by blists - more mailing lists