Hi, > >>> The device does not estimate distance, it only outputs a single bit which > >>> indicates proximity. We use 0 to mean that an object is close and 1 otherwise, > >>> sort of an uncalibrated distance. From what I understand in the ABI > >>> specification, this is allowed. > >> > >> perhaps the input subsystem would be a better fit for this driver/device? > >> what is it typically used for? > >> > >> regards, p. > >> > > Hi Peter, > > > > Whilst it may be the case that this particular one might have a reasonable > > home in input, these are often integrated with ambient light sensors > > and as such we already have a quite a few proximity sensors in IIO... > > > > Interestingly there is one obvious proximity sensor in input and that > > is a dual ambient light/ proximity part though I can't see any way > > of reading the light side of it. Interesting... > Note that, given it describes itself as a button trip I can entirely see > your point with this one! I wrote my reply before opening the datasheet. > oops. > > The device does seem to provide access to measurements related to > the capacitance sensed so might be rather more flexible than just > a button though. yes, it depends what you want to use it for if there is some aspect of measurement I think it has a place in IIO the chip can report proximity values (reg. 0x21) the proposed driver just seems to be targetted at realizing a button... regards, p. -- Peter Meerwald +43-664-2444418 (mobile) -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
