On Tue, 29 May 2012 17:02:41 +0200 Ubdfu <ubdfu@xxxxxxxxxxxxxxx> wrote: > Hello, > > Please excuse my and be aware that I'm quite new to kernel hacking :-) > > I'm currently trying to enable the RS485 support on the MAX3107 and > continuously getting the error: > "max3107 spi2.0: interrup isn't serviced normally!" > Assuming it means interrupt it nevertheless does not help me to find the > cause of the problem. > > Added some patches form: > http://marc.info/?l=linux-serial&w=2&r=1&s=max3107&q=b > > And changed the baudrate to the appropriate, set bit for rs458 mode. > > Has anyone tried working with the MAX3107? Not in rs485 mode and not for a while. The base code in drivers/tty/serial should work for RS232 mode at least. The trigger you are hitting implies that it got an event during suspend/freezing or somehow tried to queue work when work was already queued. The current code doesn't cope with the device being on a shared interrupt line, so my first guess would be that might be the problem ? Alan -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
