<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - module-switch-on-port-available will only select unavailable ports when a new sink or source appears"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100451#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - module-switch-on-port-available will only select unavailable ports when a new sink or source appears"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100451">bug 100451</a>
from <span class="vcard"><a class="email" href="mailto:tanuk@iki.fi" title="Tanu Kaskinen <tanuk@iki.fi>"> <span class="fn">Tanu Kaskinen</span></a>
</span></b>
<pre>(In reply to Vivek Dasmohapatra from <a href="show_bug.cgi?id=100451#c7">comment #7</a>)
<span class="quote">> One last question: You say “I would suggest removing the port selection
> logic from module-switch-on-port-available” — I can't see any documentation
> in the module itself: Isn't port selection why it exists?</span >
The way I see it, this module exists to do automatic profile and port switches
when things are plugged in and out. The module doesn't provide any extra value
for choosing the initial port. Or well, currently it provides some value,
because module-device-restore doesn't take the port availability into account
when it restores the port, so module-switch-on-port-available helps by fixing
stupid choices made by module-device-restore, but I think that's a bug in
module-device-restore.
To be clear, when I said "removing the port selection logic", I meant only the
initial port selection for new sinks and sources.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>