On Sat, Jun 13, 2015 at 9:21 PM, Jonathan Cameron <jic23@xxxxxxxxxx> wrote: > On 12/06/15 08:40, Vlad Dogaru wrote: >> On Thu, Jun 11, 2015 at 06:49:34PM +0300, Daniel Baluta wrote: >>> Because of the ABI confusion proximity value exposed by SX9500 >>> was inverted. >>> >>> Signed-off-by: Daniel Baluta <daniel.baluta@xxxxxxxxx> >> >> Reviewed-by: Vlad Dogaru <vlad.dogaru@xxxxxxxxx> >> >> Sorry for causing the confusion, it was the only proximity sensor I had >> encountered to date. > Greg, > > I've cc'd you to let you know that this fix causes an ABI change for > one driver. Technically that driver actually matched with the current documentation, > just the documentation was misleading and lots of drivers have ended up with > the reverse interpretation (question was whether proximity values get larger > or smaller as you get nearer). > > Anyhow, given timing I doubt the pull request will reach you until after the > merge window. I am also going to mark this for stable to cover the 4.0 and 4.1 > kernels that have this driver in them. > > Hope that's fine! > > Applied to the fixes-togreg branch of iio.git > > Daniel, thanks for clearing this mess up and checking through all the drivers > and datasheets to figure out it was only this one! You are welcome. Also, lets not forget that as mentioned in the cover letter there is still one driver that needs to be fixed. That is stk3310, where the fix is not trivial, but I have already talked with Tiberiu and he will take care of it. thanks, Daniel. -- 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
