Jonathan Cameron wrote on 2011-05-26: > > ... >>> What would happen if this driver used any other trigger? Would > everything work? >> No. But other drivers can you the trigger. It's not really an >> trigger > it's a data ready. > Most are. As you say, it is useful to trigger other reads from this, > but not to trigger this to read from other sources... >>> I think it would do an immediate read which is going to be a problem. >>> Perhaps we need a way of restricting triggers. This one can be used >>> by anyone, but the part can only use it's own trigger (I think). >> Having the ability to reject alien triggers are nice to have. > True enough. I guess the easiest is some sort of 'filter' callback on > trigger connect. > Then drivers that care, can reject devices that don't match what they > need. Would probably want one in each direction. Trigggers can > reject devices and devices can reject triggers. Are you going to put this in place? Or do you want me to look at it? BTW - I'm out next week... Greetings, Michael -- Analog Devices GmbH Wilhelm-Wagenfeld-Str. 6 80807 Muenchen Sitz der Gesellschaft: Muenchen; Registergericht: Muenchen HRB 40368; Geschaeftsfuehrer:Dr.Carsten Suckrow, Thomas Wessel, William A. Martin, Margaret Seif -- 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
