[2/4] raw/cnxk_bphy: keep leading zero in device name
Checks
Commit Message
Device naming might be misleading which is especially true if one takes
it from lspci output. In order to keep naming consistent keep leading
zero in front of pci bus number.
Signed-off-by: Tomasz Duszynski <tduszynski@marvell.com>
Reviewed-by: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Reviewed-by: Jakub Palider <jpalider@marvell.com>
---
doc/guides/rawdevs/cnxk_bphy.rst | 6 ++++--
drivers/raw/cnxk_bphy/cnxk_bphy.c | 2 +-
drivers/raw/cnxk_bphy/cnxk_bphy_cgx.c | 2 +-
3 files changed, 6 insertions(+), 4 deletions(-)
@@ -146,8 +146,10 @@ the raw devices. The rawdev ID of the device can be obtained using invocation
of ``rte_rawdev_get_dev_id("NAME:x")`` from the test application, where:
- NAME is the desired subsystem: use "BPHY" for regular, and "BPHY_CGX" for
- RFOE module,
-- x is the device's bus id specified in "bus:device.func" (BDF) format.
+ RFOE module.
+- x is the device's bus id specified in "bus:device.func" (BDF) format. BDF follows convention
+ used by lspci i.e bus, device and func are specified using respectively two, two and one hex
+ digit(s).
Use this identifier for further rawdev function calls.
@@ -158,7 +158,7 @@ bphy_rawdev_selftest(uint16_t dev_id)
static void
bphy_rawdev_get_name(char *name, struct rte_pci_device *pci_dev)
{
- snprintf(name, RTE_RAWDEV_NAME_MAX_LEN, "BPHY:%x:%02x.%x",
+ snprintf(name, RTE_RAWDEV_NAME_MAX_LEN, "BPHY:%02x:%02x.%x",
pci_dev->addr.bus, pci_dev->addr.devid,
pci_dev->addr.function);
}
@@ -28,7 +28,7 @@ static void
cnxk_bphy_cgx_format_name(char *name, unsigned int len,
struct rte_pci_device *pci_dev)
{
- snprintf(name, len, "BPHY_CGX:%x:%02x.%x", pci_dev->addr.bus,
+ snprintf(name, len, "BPHY_CGX:%02x:%02x.%x", pci_dev->addr.bus,
pci_dev->addr.devid, pci_dev->addr.function);
}