Re: [PATCH 1/5] iio: humidity: hts221: report available values via read_avail()

[Adinata Tan]

Hi Jonathan,
Thanks for the input. In this case, we can proceed with the current
implementation?

> > For this humidity case in particular, would it be better to keep the legacy
> > implementation while adding the new read_avail()?
>
> To me it seems vanishingly unlikely there is any code out there jumping
> through the hoops to read the wrong ABI element to figure out a possible
> value to write to in_humidityrelative_oversampling_ratio
>
> So I think this is in the category of ABI that we can change as long
> as no one notices.  For IIO I will also generally take ABI fixes on
> basis we actually want to know if anyone is using the broken ABI
> (and they very rarely are!)