On Mon, Feb 05, 2018 at 11:07:08AM +0100, Christian Gmeiner wrote: > Hi all. > > 2017-04-27 14:22 GMT+02:00 Martin Kepplinger <martin.kepplinger@xxxxxxxxxxxxx>: > > The device could as well be in command mode, in which this driver cannot > > handle the device. When opening the device, let's make sure the device > > will be in the mode we expect it to be for this driver. > > > > I run into issues caused by this change. It turns out that the device > is non-functional > after some warm-reboots and as a result I am not able to use xorg's > evdev driver. > So I have some questions about this change: > > * Should we enable irq before calling i2c_master_send(..) as the chip raises an > irq if the command was processed? Well, we do not care about the response... However, what is your interrupt trigger settings? Are you using edge by chance? If so, please try switching to level. > > * Would it be enough to send this command only once during driver > lifetime? I can > see that on my system open gets called 3 times during boot-up. > > * What are the circumstances the touch device would be in an other state? In the > official kernel driver the userspace can send commands via sysfs. > Also the driver > does set the touch enable mode as this patch does. What is "the official kernel driver"? Thanks. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
