On Mon, Dec 14, 2020 at 5:34 PM Jonathan Cameron <Jonathan.Cameron@xxxxxxxxxx> wrote: > On Mon, 14 Dec 2020 16:30:22 +0100 Peter Rosin <peda@xxxxxxxxxx> wrote: > > >> And that gets transformed by the > > >> rescaler into the processed values being presented as raw, with rescaling > > >> added on top, but with the read_avail info for this new raw channel being > > >> completely wrong. > > >> > > >> For the intended driver (ab8500-gpadc) this is not the case (it has no > > >> read_avail for its raw channel). But it does have a raw channel, so adding > > >> read_avail seems easy and I can easily see other drivers already doing it. > > >> Haven't checked that though... > > > > > > Drat. I'd failed to register this is one of those corner cases. > > > > I'm not sure, I just browsed the code. Maybe I misread it? > > It's doing both - you were right. I think there are only a small number of > drivers that have that history. > > Looks superficially like it's easy enough to catch this corner case and > block it - so lets do that. Sorry if I am a bit confused here. I don't understand what I am supposed to do to proceed with using this driver with the ab8500 GPADC... Shall I fix something in the AB8500 GPADC as a prerequisite? In that case I think I need some more pointers... Yours, Linus Walleij
