From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v4 40/41] net/dpaa: support for firmware version get API Date: Mon, 18 Sep 2017 15:57:06 +0100 Message-ID: <1682977c-c5dd-939f-bc77-e18a6803de07@intel.com> References: <20170823141213.25476-1-shreyansh.jain@nxp.com> <20170909112132.13936-1-shreyansh.jain@nxp.com> <20170909112132.13936-41-shreyansh.jain@nxp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: hemant.agrawal@nxp.com To: Shreyansh Jain , dev@dpdk.org Return-path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 050651B162 for ; Mon, 18 Sep 2017 16:57:09 +0200 (CEST) In-Reply-To: <20170909112132.13936-41-shreyansh.jain@nxp.com> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 9/9/2017 12:21 PM, Shreyansh Jain wrote: > From: Hemant Agrawal > > Signed-off-by: Hemant Agrawal <...> > +static int > +dpaa_fw_version_get(struct rte_eth_dev *dev __rte_unused, > + char *fw_version, > + size_t fw_size) > +{ > + int ret; > + FILE *svr_file = NULL; > + unsigned int svr_ver = 0; > + > + PMD_INIT_FUNC_TRACE(); > + > + svr_file = fopen("/sys/devices/soc0/soc_id", "r"); Is this sysfs file fixed, can it be enumerated as soc1 etc.. in some systems? > + if (!svr_file) { > + DPAA_PMD_ERR("Unable to open SoC device"); > + return -ENOTSUP; /* Not supported on this infra */ > + } > + > + ret = fscanf(svr_file, "svr:%x", &svr_ver); > + if (ret <= 0) { > + DPAA_PMD_ERR("Unable to read SoC device"); > + return -ENOTSUP; /* Not supported on this infra */ > + } > + > + ret = snprintf(fw_version, fw_size, > + "svr:%x-fman-v%x", > + svr_ver, > + fman_ip_rev); > + > + ret += 1; /* add the size of '\0' */ > + if (fw_size < (uint32_t)ret) > + return ret; > + else > + return 0; > +} <...>