Paul Thomas wrote on 2011-08-26: > I was just trying to test this driver with the IRQ, and I get this > after a ctrl^c after a hung modprobe. Hi Paul, Can you explain this a bit further? The modprobe can only hung if the part never generates an interrupt. This basically happens in ad7192_calibrate(). When this happens, you press ctrl^c? Then the second time doing the modprobe you see this oops? It's basically something enabled an already enabled interrupt. > I also get a "ad7192 spi1.1: > device ID query failed (0x3)", but it looks like the id isn't used. Well the AD7194 is currently not recognized by the driver. You have to add it, as known ID. > Also this is with the ad7194 instead of the ad7192. I'm using > .irq=AT91SAM9260_ID_IRQ0 which works well for the mcp251x driver, > although with that device it's a dedicated interrupt line. There is a significant difference between the AD7190/AD7192/AD7195, and the part you are going to add. Make sure you get the channel selection bits right! 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
