On 10/9/2018 10:32 AM, Igor Russkikh wrote: > Signed-off-by: Igor Russkikh <igor.russk...@aquantia.com> > Signed-off-by: Pavel Belous <pavel.bel...@aquantia.com>
<...> > +/** > + * This is a custom API for adapter's LED controls. > + * > + * @param dev > + * Ethernet device to apply control to > + * @param control > + * 6 bit value (3 leds each 2bit): > + * - bits 0-1: LED0 control > + * - bits 2-3: LED1 control > + * - bits 4-5: LED2 control > + * Each two bit control value is: > + * - 0: Firmware manages this LED activity > + * - 1: Permanent ON > + * - 2: Blinking > + * - 3: Permanent OFF > + * > + * @return > + * - (0) if successful. > + * - (-ENOTSUP) if hardware doesn't support. > + */ > +int rte_pmd_atl_dev_led_control(int port, int control); What is the intention here, making PMD specific public API? If so .map file is missing but we discourage using PMD specific APIs, can't it be possible to extend exiting led related dev_ops in a generic way to cover your use case?
