On Sat, Jan 10, 2015 at 03:15:39PM +0100, Belisko Marek wrote: > Ping for input maintainer. DT changes was acked. Thanks. > > On Tue, Sep 30, 2014 at 10:17 PM, Marek Belisko <marek@xxxxxxxxxxxxx> wrote: > > This patch adds new parameters that allow to address typical hardware > > design differences: touch screens may be wired or oriented differently > > (portrait or landscape). And usually the active area of the touch is a > > little larger than the active area of the LCD. This results in the touch > > coordinates that have some significant deviation from LCD coordinates. > > Usually this is addressed in user space by a calibration tool (e.g. tslib > > or xinput-calibrator) but some systems don't have these tools or require > > that the screen is already roughly calibrated (e.g. Replicant) to operate > > the device until a better calibration can be done. And, some systems > > react very strangely if the touch event stream reports coordinates > > outside of the active area. > > > > This makes it necessry to be able to configure: > > 1. swapping x and y wires (coordinate values) > > 2. flipping of x (left - right) or y (top - bottom) or even both > > 3. define an active area so that an uncalibrated screen already > > roughly matches the LCD to be useful. > > 4. clip reported coordinates to the active area. > > > > If none of the new parameters is defined (in DT) or set in a board file, > > the driver behaves the same as without this patch. > > > > Author (1&2): H. Nikolaus Schaller <hns@xxxxxxxxxxxxx> > > Author (3&4): Paul Kocialkowski <contact@xxxxxxxx> > > > > Signed-off-by: H. Nikolaus Schaller <hns@xxxxxxxxxxxxx> OK, I was hesitant of adding these as normally we have tslib to perform the conversion, but maybe it is time to allow it in the kernel and standardize users. However, this seems like a general issue and we should: 1. Perform conversion in input core rather than individual drivers. I think we should allocate a new bitmaps for some transformations and have the code do X/Y flip/clip of the coordinates. 2. Standardize on bindings. We already have of-touchscreen.c doing rudimentary parsing, we shoudl look into extending it rather than creating myriad of driver-specific bindings. Also, do we need swap and flip or do we simply need rotation (like the proposed Broadcom iproc driver has)? Thanks. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
