Tuesday 28 July 2009 17:07:27 Mark Brown wrote: > On Tue, Jul 28, 2009 at 04:59:33PM +0200, Janusz Krzysztofik wrote: > > Following that model, the line discipline code didn't seam to belong to a > > codec driver for me. If it could be recognized as a new bus dirver, it > > should be pushed down probably into a separate module. However, if it was > > rather some kind of a bus adapter driver, it seamed to belong to the > > machine code. > > The way it looks with the current code the line discipline itself is > going to apply equally well to any serial port that's used - I'm not > clear what's system-specific about it. The bit that connects the line > discipline to the line is a different matter but the bit that interacts > with the TTY layer after registration is working through a pluggable > abstraction layer and shouldn't, I'd expect, be specific to the > particular serial port. Mark, I think I can't tell anything more before I try to implement it in a way you suggest, so I will. What I would like to retain from the current codec driver are those two modes of operation: without and with the line discipline activated. Initially, the codec would be registered as a platform device, as it is now. Activation of the line discipline would deregister the codec device from the platform bus and reregister it again, now as the line discipline provided device. Is this possible with current ASoC framework? Thanks, Janusz -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
