tree f33979810b85bd13a8bcf37bb540a840a2a09a26
parent 78972f7a4fc2ad28adf5445a6e2e965bf57c433e
author Jes B. Klinke <jbk@chromium.org> 1645407120 -0800
committer Timothy Trippel <5633066+timothytrippel@users.noreply.github.com> 1645640464 -0800

[opentitantool] Gracefully handle requests for unsupported interfaces

As we plan to introduce a session proxy process, it is not desirable
that the persistent session process could panic!() if a single command
line invocation asks for e.g. I2C, though the particular USB backend
does not support I2C at all.

We already have a TransportError value to be used if asking for e.g. a
UART instance which does not exist: InvalidInstance.  It would be sent
via the TCP protocol and presented by the command line invocation.

This change introduces a new InvalidInterface.  And modifies the
default implementation in the Transport trait to return that instead
of panicking, in case the transport does not support UART, I2C or
whatever kind of interface it is being asked about.

Signed-off-by: Jes B. Klinke <jbk@chromium.org>
Change-Id: I7c0ff6e66a87ccd444be603be0075663d99cc280