> > I think we just disagree about implementing a version that “works” in a quite specific > > setup (there are necessary assumptions about OMAP pinmux and omap-serial) with > > existing APIs versus a general one that might need a lot of changes outside the driver > > and introduce new APIs. > > After re-thinking what we have discussed so far (and considering other recommendations > I have received off-list) I currently see these options/questions: > > * who could modify the serial drivers and APIs so that this driver can become > a subnode (“bus client”) of an UART? How long does it take to > become available? I believe that is called "tty line discipline". > * would it be an option to simply rename the driver to “w2sg0004-power” > to make clear that it is not at all related to the UART data communication > channel but only controlling the power of the w2sg0004 chip? Sounds sane. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
