Dear Dmitry Torokhov, [...] > > > +#define CHAN_MASK_TOUCHBUTTON (0x3 << 0) > > > +#define CHAN_MASK_TOUCHSCREEN_4WIRE (0xf << 2) > > > +#define CHAN_MASK_TOUCHSCREEN_5WIRE (0x1f << 2) > > > + int use_touchbutton:1; > > Why would someone not want to use it? The touchbutton is not present on many devices using the MX28. I'd like to implement it in subsequent patch for completeleness though. Jonathan, just a quick thought, but we're getting close to have MX233 Olinuxino device supported as well (not my work, another guy is working on that I guess). The device is very cheap, maybe you can get one? It also has this insane touchscreen controller and all these cool insane parts ;-) > > > + int use_touchscreen_4wire:1; > > > + int use_touchscreen_5wire:1; > > This is weird. Can it be both 4 and 5 wires? I assume not, so using > bits is not the best idea. What do you say to "use_touchscreen" and "use_touchscreen_5wire" ? 5wire touchscreen is special case, but it's easy to support it, so I dropped it in. Or maybe make it enum? TOUCHSCREEN_NONE = 0, TOUCHSCREEN_4WIRE, TOUCHSCREEN_5WIRE, I like enum :) [...] Rest will be fixed in V2. Thanks for the review! Best regards, Marek Vasut -- 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
