docs/designs/multihost-physical-led.md

12 The existing phosphor-led-sysfs design exposes one service per LED configuration
29 Based on the current design in phosphor-led-sysfs application, pairing groups
39       KERNEL                 META-PHOSPHOR           PHOSPHOR-LED-SYSFS SERVICE
73                                                  PHOSPHSOR-LED-SYSFS DAEMON
77 The existing design uses sysfs entry as udev events for particular LED and
104 - Add DBUS API method for phosphor-led-sysfs daemon.
112       KERNEL                               PHOSPHOR-LED-SYSFS DAEMON
116    |   LED 1    |  Event 2   |  UDEV  |      |  SYSFS  |      |  EXECUTABLE  |
153 - Dbus API method will be created in the phosphor-led-sysfs repository under
154   **_xyz.openbmc_project.Led.Sysfs.Internal_** interface name to add or remove
160     xyz.openbmc_project.Led.Sysfs.Internal interface -          -             -
169 - Executable will call Dbus API method in the phosphor-led-sysfs repository to
172 - Phosphor-led-sysfs will have a single systemd service (primary service)
176 - Once Dbus API method call invoked, phosphor-led-sysfs daemon will retrieve the
181 - The schema will be implemented in the phosphor-led-sysfs daemon. A group of
213 a file utilizing the script. Phosphor-led-sysfs will monitor the file using
219 udev events and phosphor-led-sysfs application. Since, udev events can be