tree 8aea9cbe0a1d89acaffb32a1e8ecf1cf1b7ee4a3
parent b377362110f93a6eeabfb7f7a0e5cbb1eba65089
author Ninad Palsule <ninadpalsule@us.ibm.com> 1682561915 -0500
committer Ninad Palsule <ninadpalsule@us.ibm.com> 1682643079 -0500

Fixed broken dbus interface for multiple consoles

There is a console server instance per console. So if there are two
consoles then two console server instances will be started. The issue
is that each instance is sharing same bus name and object path. The
issue is fixed by keeping the interface name same as before
(xyz.openbmc_project.console) but changing the bus name and object path
name by appending socket-id which makes them unique. So the bus name
becomes xyz.openbmc_project.Console.<socket-id> and the object name
becomes /xyz/openbmc_project/Console/<socket-id>. Each console server
has its own socket-id hence there should not be any conflict between two
consoles.

Testing:
    -> Ran busctl to check object changes
    $ busctl get-property xyz.openbmc_project.Console.console0 /xyz/openbmc_project/console/console0 xyz.openbmc_project.console baudrate
    u 0
    $ busctl introspect xyz.openbmc_project.Console.console0 /xyz/openbmc_project/console/console0    ....
    xyz.openbmc_project.Console         interface -         -            -
    .setBaudRate                        method    u         x            -
    .baudrate                           property  u         0            -

Change-Id: Ic1aacd8f284a867416081b4965b55ba7c3cb34e3
Signed-off-by: Ninad Palsule <ninadpalsule@us.ibm.com>