DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Smith, Eleanor" <eleanor.smith@intel.com>
To: dev@dpdk.org
Cc: ferruh.yigit@intel.com, pablo.de.lara.guarch@intel.com,
	akhil.goyal@nxp.com
Subject: [dpdk-dev] [PATCH v1 4/4] librte_bbdev: update device info structure to use rte_device
Date: Fri,  1 Mar 2019 17:23:30 +0000	[thread overview]
Message-ID: <1551461010-881-5-git-send-email-eleanor.smith@intel.com> (raw)
In-Reply-To: <1551461010-881-1-git-send-email-eleanor.smith@intel.com>

This patch update bbdev API rte_bbdev_info struct to use rte_device
instead of rte_bus.

Signed-off-by: Smith, Eleanor <eleanor.smith@intel.com>
---
 doc/guides/prog_guide/bbdev.rst | 4 ++--
 lib/librte_bbdev/rte_bbdev.c    | 6 +++---
 lib/librte_bbdev/rte_bbdev.h    | 2 +-
 3 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/doc/guides/prog_guide/bbdev.rst b/doc/guides/prog_guide/bbdev.rst
index 9de1444..a570e48 100644
--- a/doc/guides/prog_guide/bbdev.rst
+++ b/doc/guides/prog_guide/bbdev.rst
@@ -255,7 +255,7 @@ This allows the user to query a specific bbdev PMD and get all the device
 capabilities. The ``rte_bbdev_info`` structure provides two levels of
 information:
 
-- Device relevant information, like: name and related rte_bus.
+- Device relevant information, like: name and related rte_device.
 
 - Driver specific information, as defined by the ``struct rte_bbdev_driver_info``
   structure, this is where capabilities reside along with other specifics like:
@@ -266,7 +266,7 @@ information:
     struct rte_bbdev_info {
         int socket_id;
         const char *dev_name;
-        const struct rte_bus *bus;
+        const struct rte_device *device;
         uint16_t num_queues;
         bool started;
         struct rte_bbdev_driver_info drv;
diff --git a/lib/librte_bbdev/rte_bbdev.c b/lib/librte_bbdev/rte_bbdev.c
index c4cc18d..6ca3c8e 100644
--- a/lib/librte_bbdev/rte_bbdev.c
+++ b/lib/librte_bbdev/rte_bbdev.c
@@ -498,7 +498,7 @@ rte_bbdev_queue_configure(uint16_t dev_id, uint16_t queue_id,
 		if (conf->op_type == RTE_BBDEV_OP_TURBO_DEC &&
 			conf->priority > dev_info.max_ul_queue_priority) {
 			rte_bbdev_log(ERR,
-					"Priority (%u) of queue %u of bdev %u must be <= %u",
+					"Priority (%u) of queue %u of bbdev %u must be <= %u",
 					conf->priority, queue_id, dev_id,
 					dev_info.max_ul_queue_priority);
 			return -EINVAL;
@@ -506,7 +506,7 @@ rte_bbdev_queue_configure(uint16_t dev_id, uint16_t queue_id,
 		if (conf->op_type == RTE_BBDEV_OP_TURBO_ENC &&
 			conf->priority > dev_info.max_dl_queue_priority) {
 			rte_bbdev_log(ERR,
-					"Priority (%u) of queue %u of bdev %u must be <= %u",
+					"Priority (%u) of queue %u of bbdev %u must be <= %u",
 					conf->priority, queue_id, dev_id,
 					dev_info.max_dl_queue_priority);
 			return -EINVAL;
@@ -795,7 +795,7 @@ rte_bbdev_info_get(uint16_t dev_id, struct rte_bbdev_info *dev_info)
 	memset(dev_info, 0, sizeof(*dev_info));
 	dev_info->dev_name = dev->data->name;
 	dev_info->num_queues = dev->data->num_queues;
-	dev_info->bus = rte_bus_find_by_device(dev->device);
+	dev_info->device = dev->device;
 	dev_info->socket_id = dev->data->socket_id;
 	dev_info->started = dev->data->started;
 
diff --git a/lib/librte_bbdev/rte_bbdev.h b/lib/librte_bbdev/rte_bbdev.h
index bec1ef6..7b3891a 100644
--- a/lib/librte_bbdev/rte_bbdev.h
+++ b/lib/librte_bbdev/rte_bbdev.h
@@ -313,7 +313,7 @@ struct rte_bbdev_driver_info {
 struct rte_bbdev_info {
 	int socket_id;  /**< NUMA socket that device is on */
 	const char *dev_name;  /**< Unique device name */
-	const struct rte_bus *bus;  /**< Bus information */
+	const struct rte_device *device; /**< Device Information */
 	uint16_t num_queues;  /**< Number of queues currently configured */
 	bool started;  /**< Set if device is currently started */
 	struct rte_bbdev_driver_info drv;  /**< Info from device driver */
-- 
2.7.4

---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

      parent reply	other threads:[~2019-03-01 17:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-01 17:23 [dpdk-dev] [PATCH v1 0/4] baseband/fpga_lte_fec: BBDEV FPGA driver for 4G turbo FEC Smith, Eleanor
2019-03-01 17:23 ` [dpdk-dev] [PATCH v1 1/4] baseband/fpga_lte_fec: addition of driver for 4G turbo FEC with PAC N300 FPGA card Smith, Eleanor
2019-03-09  1:24   ` Thomas Monjalon
2019-03-26 11:25     ` Akhil Goyal
2019-03-26 11:25       ` Akhil Goyal
2019-03-01 17:23 ` [dpdk-dev] [PATCH v1 2/4] usertools: update to usertool to allow binding of baseband device Smith, Eleanor
2019-03-01 17:23 ` [dpdk-dev] [PATCH v1 3/4] test-bbdev: update bbdev test-app for FPGA driver testing Smith, Eleanor
2019-03-01 17:23 ` Smith, Eleanor [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1551461010-881-5-git-send-email-eleanor.smith@intel.com \
    --to=eleanor.smith@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).