On Thu, May 22, 2014 at 10:29 AM, Nick Dyer <nick.dyer@xxxxxxxxxxx> wrote: > > Dmitry Torokhov wrote: > > On Thu, Jul 18, 2013 at 07:17:44PM +0200, rydberg@xxxxxxxxxxx wrote: > >>> From: Yufeng Shen <miletus@xxxxxxxxxxxx> > >>> This is the preparation for supporting the code path when there is > >>> platform data provided and still boot the device into a sane state > >>> with backup NVRAM config. > >>> > >>> Make the irqflags default to be IRQF_TRIGGER_FALLING if no platform data is > >>> provided. > > > > I think if there is no platform data we should use 0 as IRQ falgs and > > assume that IRQ line is properly configured by the board code or via > > device tree. > > Beson/Yufeng - do you still have a requirement to probe without platform > data or device tree? I'm just merging in some changes to add device tree > support, and it would simplify things a bit if I can drop this patch. It has been working for quite a while for boards/devices that don't provide platform data. If we drop the default IRQ flags, sure we can add code for each board to configure the IRQ separately, but that's just adding extra work. Is there strong reason why we should not do the default setting in the driver if it is not already configured in platform data ? -- 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
