On 04/17/2012 10:08 AM, Tanu Kaskinen wrote: > In my mind a port is an "atomic routing unit", and a port > that can be used for both input and output is not atomic (it > defines two routes). An example of practical problems having > two routes in one port: you can't set a property for output > without setting it also for input. Mark, do you have any opinion on this? IIRC you've been advocating for keeping e g headset jacks as one entity, but my memory might fail me. Also does it have any implication on the pending UCM patches? For desktops / HDA, we only have single-direction ports so far, and I don't see that changing in the foreseeable future, so not much to worry about there. -- David Henningsson, Canonical Ltd. http://launchpad.net/~diwic
