Skip to contentSkip to conversation

Duplicate htu21 drivers

DISCUSSION Michal Marek 2 participants 3 messages Oct 28, 2015 1 message not in the archive IIO

lore
Share & tools
lore
#0 lore raw

Hi,

commit 2b5c53d2c958 ("Add htu21 meas-spec driver support") introduced a new implementation of the htu21 driver into drivers/iio/humidity. At first glance, it provides the same features as drivers/hwmon/htu21 with a different sysfs interface. What is the plan with these two drivers? Will the iio driver replace the hwmon one? At a minimum, they should conflict in kconfig, because module names must be unique.

Thanks,
Michal

_______________________________________________
lm-sensors mailing list
[email protected]
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

#2 lore raw
In reply to a message not in the archive

Dne 28.10.2015 v 11:52 [email protected] napsal(a):

Quoted 7 lines

Hello Michal,

the plan discussed with Jonathan and Guenter was to remove the driver in hwmon once the iio one was introduced.

Should I provide a patch in Kconfig to make them conflict as of now ?

Then you can either execute your plan :), or make the hwmon driver depend on HTU21=n.

Michal

#3 lore raw
Quoted 2 lines · On Wed, Oct 28, 2015 at 12:53:12PM +0100, [email protected]…

I was not sure about the timing for the plan … :)
Now that the patch has been approved for IIO, then indeed I can remove the patch for htu21 in hwmon.

Yes, the driver in hwmon needs to be removed. Patch welcome.

Guenter

Quoted 25 lines

Thanks,
Ludovic

Quoted 19 lines · Michal Marek

Dne 28.10.2015 v 11:52 [email protected] napsal(a):

Quoted 7 lines

Hello Michal,

the plan discussed with Jonathan and Guenter was to remove the driver in hwmon once the iio one was introduced.

Should I provide a patch in Kconfig to make them conflict as of now ?

Then you can either execute your plan :), or make the hwmon driver depend on HTU21=n.

Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html