From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Peter Rosin <peda@axentia.se>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
Andi Shyti <andi.shyti@kernel.org>, Wolfram Sang <wsa@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v7 0/4] Extend device_get_match_data() to struct bus_type
Date: Tue, 15 Aug 2023 09:44:31 +0300 [thread overview]
Message-ID: <ZNsez3oWNcT72PGy@smile.fi.intel.com> (raw)
In-Reply-To: <OS0PR01MB5922E09340CDCFF54A9A6CBA8610A@OS0PR01MB5922.jpnprd01.prod.outlook.com>
On Fri, Aug 11, 2023 at 02:46:10PM +0000, Biju Das wrote:
> > Subject: Re: [PATCH v7 0/4] Extend device_get_match_data() to struct
> > bus_type
> > On Fri, Aug 11, 2023 at 01:27:36PM +0000, Biju Das wrote:
> > > > On Thu, Aug 10, 2023 at 09:05:10AM +0000, Biju Das wrote:
...
> > > > I'm good with this approach, but make sure you checked the whole
> > > > kernel source tree for a such.
> > >
> > > Checking against 16 is too short I guess??
> > >
> > > drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h has 18 enums.
> >
> > So, what does prevent us from moving that tables to use pointers?
>
> I think that will lead to ABI breakage(client->name vs id->name)
>
> match = device_get_match_data(&client->dev);
> if (match) {
> chip_type = (uintptr_t)match;
> name = client->name;
> } else if (id) {
> chip_type = (enum inv_devices)
> id->driver_data;
> name = id->name;
> } else {
> return -ENOSYS;
> }
It's easy to work around (may be better fix can be found, haven't checked, just
what first comes to my mind):
match ...
name = match->name;
/* If enumerated via firmware node, fix the ABI */
if (dev_fwnode())
client->name
> > > /*device enum */
> > > enum inv_devices {
> > > INV_MPU6050,
> > > INV_MPU6500,
> > > INV_MPU6515,
> > > INV_MPU6880,
> > > INV_MPU6000,
> > > INV_MPU9150,
> > > INV_MPU9250,
> > > INV_MPU9255,
> > > INV_ICM20608,
> > > INV_ICM20608D,
> > > INV_ICM20609,
> > > INV_ICM20689,
> > > INV_ICM20600,
> > > INV_ICM20602,
> > > INV_ICM20690,
> > > INV_IAM20680,
> > > INV_NUM_PARTS
> > > };
> > >
> > > The new helper function
> >
> > You mean for debugging? We don't need that in production.
>
> That is sample code for iterating through id table to find max enum
> and check against ZERO_OR_NULL_PTR
Much better with a coccinelle. You will find all or almost all occurrences
without too much effort done.
> > I think what you need is a coccinelle script to find these.
>
> I need to explore using coccinelle script as I have n't tried before.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-08-15 6:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 16:17 [PATCH v7 0/4] Extend device_get_match_data() to struct bus_type Biju Das
2023-08-04 16:17 ` [PATCH v7 1/4] drivers: fwnode: " Biju Das
2023-08-05 16:40 ` [PATCH v7 0/4] " Jonathan Cameron
2023-08-05 17:42 ` Biju Das
2023-08-06 13:29 ` Jonathan Cameron
2023-08-06 16:27 ` Biju Das
2023-08-07 14:54 ` Andy Shevchenko
2023-08-07 19:45 ` Jonathan Cameron
2023-08-08 12:14 ` Andy Shevchenko
2023-08-07 20:37 ` Dmitry Torokhov
2023-08-08 12:18 ` Andy Shevchenko
[not found] ` <20230809182551.7eca502e@jic23-huawei>
2023-08-10 9:05 ` Biju Das
2023-08-10 15:11 ` Andy Shevchenko
2023-08-11 13:27 ` Biju Das
2023-08-11 14:30 ` Andy Shevchenko
2023-08-11 14:46 ` Biju Das
2023-08-14 13:12 ` Geert Uytterhoeven
2023-08-14 13:17 ` Biju Das
2023-08-28 13:01 ` Jonathan Cameron
2023-08-15 6:44 ` Andy Shevchenko [this message]
2023-08-15 6:58 ` Biju Das
2023-08-15 7:06 ` Biju Das
2023-08-15 9:42 ` Andy Shevchenko
2023-08-10 15:04 ` Andy Shevchenko
2023-08-08 15:16 ` Jonathan Cameron
2023-08-14 13:01 ` Geert Uytterhoeven
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=ZNsez3oWNcT72PGy@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andi.shyti@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=djrscally@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jic23@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=peda@axentia.se \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=wsa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox