On 06/14/2011 02:38 PM, Baohua Song wrote: >> Could we add an option for gpio >> pendown, like this? >> >> - gpios : should specify GPIO used for pendown. >> >> If interrupt node is not present in this node, gpio_to_irq of the pen >> down GPIO will be used. > > I disagree... An optional gpio node doesn't make sense here. The result of gpio_to_irq is still an interrupt, then we can place the result in interrupt node. > And the ads7846 driver required an interrupt node but not a gpio node since we don't find any of_get_gpio() in this driver. > BTW, it even doesn’t make sense to call function gpio_to_irq in a driver like ads7846. on the contrary, drivers/input/keyboard/gpio_keys.c is really an good user of gpio_to_irq. Hi Barry, The classical platform data is seldom used when device tree is passed. So it would be better to disable platform data passing to verify device tree support. Without platform data passing, we don't have pdata and pdata->get_pendown_state func for ads7846_setup_pendown(). The ads7846_probe() will need updates on this. Passing gpio for pendown might be a possible solution, as device tree supports "gpios" node. We could use of_get_gpio_flags() to retrieve it. I sent an earlier work of mine on this back in Feb. to you. Best regards, Thomas -- 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
