[lkml]   [2015]   [May]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] fix n900 dts file to work around 4.1 touchscreen regression on n900

> > > single DT, you don't even use that property in your driver, and now
> > > that you realise you meant something else, you want the code that
> >
> > not Pali, Sebastian.
> >
> > > actually parse the *right* property and does the right thing, that all
> > > other DT agree (and depend on) to be reverted?
> >
> > We shouldn't revert, that I agree. But both properties should be parsed.
> No. If the property is wrong, and nobody parsed it, I do not see any reason to
> start now.


But that's not what I'm asking. See a changelog of
3eea8b5d68c801fec788b411582b803463834752 and compare it with what it
actually does.

It is buggy. If fuzz is specified but maximum is not, it overwites
maximum with zero.

Plus it introduces new failure "if (!test_bit(axis, dev->absbit))".

Plus it fails to distinguish between "value not specified in the dt"
and "zero is specified in the dt".

The 3eea8b5d68c801fec788b411582b803463834752 is just bad.

(cesky, pictures)

 \ /
  Last update: 2015-05-29 23:01    [W:0.209 / U:37.676 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site