[dpdk-dev] [PATCH v3 21/23] bus/dpaa: enhance checks for bus and device detection

[Hemant Agrawal]

1. It is not a error if no network device available. One can
only use crypto device
2. Improve logging for failure in detecting the bus

Signed-off-by: Hemant Agrawal <hemant.agra...@nxp.com>
---
 drivers/bus/dpaa/dpaa_bus.c | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/drivers/bus/dpaa/dpaa_bus.c b/drivers/bus/dpaa/dpaa_bus.c
index 37cf55d60b..173041c026 100644
--- a/drivers/bus/dpaa/dpaa_bus.c
+++ b/drivers/bus/dpaa/dpaa_bus.c
@@ -521,16 +521,18 @@ rte_dpaa_bus_dev_build(void)
        /* Get the interface configurations from device-tree */
        dpaa_netcfg = netcfg_acquire();
        if (!dpaa_netcfg) {
-               DPAA_BUS_LOG(ERR, "netcfg_acquire failed");
+               DPAA_BUS_LOG(ERR,
+                       "netcfg failed: /dev/fsl_usdpaa device not available");
+               DPAA_BUS_WARN(
+                       "Check if you are using USDPAA based device tree");
                return -EINVAL;
        }
 
        RTE_LOG(NOTICE, EAL, "DPAA Bus Detected\n");
 
        if (!dpaa_netcfg->num_ethports) {
-               DPAA_BUS_LOG(INFO, "no network interfaces available");
+               DPAA_BUS_LOG(INFO, "NO DPDK mapped net interfaces available");
                /* This is not an error */
-               return 0;
        }
 
 #ifdef RTE_LIBRTE_DPAA_DEBUG_DRIVER
-- 
2.17.1