From af02d1e2f733dbfd3fc88e61f878ba260abc6701 Mon Sep 17 00:00:00 2001 From: Rohit Raj Date: Wed, 6 Oct 2021 22:31:28 +0530 Subject: [PATCH] net/dpaa: explain behaviour with FMC policy This patch adds comment to explain how dpaa_port_fmc_ccnode_parse function is working to get the HW queue from FMC policy file Signed-off-by: Rohit Raj Acked-by: Hemant Agrawal --- drivers/net/dpaa/dpaa_fmc.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/drivers/net/dpaa/dpaa_fmc.c b/drivers/net/dpaa/dpaa_fmc.c index 5195053361..f8c9360311 100644 --- a/drivers/net/dpaa/dpaa_fmc.c +++ b/drivers/net/dpaa/dpaa_fmc.c @@ -1,5 +1,5 @@ /* SPDX-License-Identifier: BSD-3-Clause - * Copyright 2017-2020 NXP + * Copyright 2017-2021 NXP */ /* System headers */ @@ -338,6 +338,12 @@ static int dpaa_port_fmc_ccnode_parse(struct fman_if *fif, fqid = keys_params->key_params[j].cc_next_engine_params .params.enqueue_params.new_fqid; + /* We read DPDK queue from last classification rule present in + * FMC policy file. Hence, this check is required here. + * Also, the last classification rule in FMC policy file must + * have userspace queue so that it can be used by DPDK + * application. + */ if (keys_params->key_params[j].cc_next_engine_params .next_engine != e_IOC_FM_PCD_DONE) { DPAA_PMD_WARN("FMC CC next engine not support"); -- 2.20.1