On Mon, Dec 09, 2013 at 09:46:38AM -0800, Tony Lindgren wrote: > > +Optional properties: > > + - ti,fuzz-x : integer, X noise value of the > > touchscreen > > + (defaults to 4) > > + - ti,fuzz-y : integer, Y noise value of the > > touchscreen > > + (defaults to 8) > > + - ti,fuzz-pressure : integer, pressure noise value of the > > touchscreen > > + (defaults to 2) > > + - ti,max-x : integer, maximum reported x value > > + (defaults to 4096) > > + - ti,max-y : integer, maximum reported y value > > + (defaults to 4096) > > + - ti,max-pressure : integer, maximum reported pressure > > + (defaults to 4096) > > + - ti,x-plate-resistance : integer, resistance of the touchscreen's X > > plates > > + in ohm (defaults to 280) > > + - ti,esd-recovery-timeout-ms : integer, if the touchscreen does not > > respond after > > + the configured time (in milli seconds), the > > driver > > + will reset it. This is disabled by default. > > Instead of adding these optional ti,* properties you can set them in the > driver directly in the of_match table based on the compatible flag. Then > you can pass compatible flag like ti,tsc2005-nokia-n900, or the name of > the LCD panel. Most likely these depend on the LCD panel selected.
I could certainly do this, but it would move the board specific data from the boardcode into the driver. That looks contra-productive to me. Is there a good reason to do it this way? -- Sebastian
signature.asc
Description: Digital signature
