On Thu, 2012-08-09 at 20:05 +0800, Mark Brown wrote: > On Thu, Aug 09, 2012 at 11:48:42AM +0000, Arnd Bergmann wrote: > > On Thursday 09 August 2012, Wei Ni wrote: > > > > The wlan driver wish this flags include the IRQF_TRGGER_* information, > > > and it will use this flags to configure other hw settings. If it is > > > wrong, the wlan can't work. > > You can read the configuration with irqd_get_trigger_type() - see the OF > code in sound/soc/codecs/wm8903.c for an example. I tried it, it worked fine. thanks for your help. > > > The driver should not need to know about thie flag. It gets read > > by irq_create_of_mapping when calling teh xlate function and > > gets set using irq_set_irq_type from there too. > > That only helps the interrupt controller, it doesn't help the interrupt > source. A good proportion of embedded devices have a great deal of > flexibility in how they signal interrupts so they need to know what mode > to pick. > -- > To unsubscribe from this list: send the line "unsubscribe linux-tegra" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
