Re: [PATCH v3 2/2] iio: temperature: add support for MCP998X
From: Jonathan Cameron
Date: Sat Jun 14 2025 - 09:27:22 EST
>
> > +
> > +static const struct i2c_device_id mcp9982_id[] = {
> > + { .name = "mcp9933", .driver_data = (kernel_ulong_t)&mcp9933_chip_config },
> > + { .name = "mcp9933d", .driver_data = (kernel_ulong_t)&mcp9933d_chip_config },
> > + { .name = "mcp9982", .driver_data = (kernel_ulong_t)&mcp9982_chip_config },
> > + { .name = "mcp9982d", .driver_data = (kernel_ulong_t)&mcp9982d_chip_config },
> > + { .name = "mcp9983", .driver_data = (kernel_ulong_t)&mcp9983_chip_config },
> > + { .name = "mcp9983d", .driver_data = (kernel_ulong_t)&mcp9983d_chip_config },
> > + { .name = "mcp9984", .driver_data = (kernel_ulong_t)&mcp9984_chip_config },
> > + { .name = "mcp9984d", .driver_data = (kernel_ulong_t)&mcp9984d_chip_config },
> > + { .name = "mcp9985", .driver_data = (kernel_ulong_t)&mcp9985_chip_config },
> > + { .name = "mcp9985d", .driver_data = (kernel_ulong_t)&mcp9985d_chip_config },
> > + { }
> David mentioned the other day that there is an effort to remove the need for
> the kernel_ulong_t here but it relies on
> { "mcp9985d", &mcp9984d_chip_config },
> style entries.
Oops. Still need the cast.
>
> https://lore.kernel.org/all/1c7946f1-d712-4baa-8243-be6a55eec528@xxxxxxxxxxxx/
>
> I wasn't aware of that effort but seems sensible to me!
>
>
> > +};
> > +MODULE_DEVICE_TABLE(i2c, mcp9982_id);
>
>