From: "Gupta, Nipun" <Nipun.Gupta@amd.com>
To: "Gangurde, Abhijit" <abhijit.gangurde@amd.com>,
"Agarwal, Nikhil" <nikhil.agarwal@amd.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"Yigit, Ferruh" <Ferruh.Yigit@amd.com>,
"Gangurde, Abhijit" <abhijit.gangurde@amd.com>
Subject: RE: [PATCH] bus/cdx: provide driver flag for optional resource mapping
Date: Fri, 7 Jul 2023 08:35:12 +0000 [thread overview]
Message-ID: <CH3PR12MB8308B941FA2D88A6DC50ADABE82DA@CH3PR12MB8308.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230626103958.3139-1-abhijit.gangurde@amd.com>
> -----Original Message-----
> From: Abhijit Gangurde <abhijit.gangurde@amd.com>
> Sent: Monday, June 26, 2023 4:10 PM
> To: Gupta, Nipun <Nipun.Gupta@amd.com>; Agarwal, Nikhil
> <nikhil.agarwal@amd.com>
> Cc: dev@dpdk.org; david.marchand@redhat.com; Yigit, Ferruh
> <Ferruh.Yigit@amd.com>; Gangurde, Abhijit <abhijit.gangurde@amd.com>
> Subject: [PATCH] bus/cdx: provide driver flag for optional resource mapping
>
> Provide driver flag which gives an option to map the cdx
> device resource before probing the device driver.
> Also, make rte_cdx_map_device() API as public to map
> device resource separately.
>
> Signed-off-by: Abhijit Gangurde <abhijit.gangurde@amd.com>
> ---
> drivers/bus/cdx/bus_cdx_driver.h | 26 ++---------------
> drivers/bus/cdx/cdx.c | 11 ++++---
> drivers/bus/cdx/rte_bus_cdx.h | 50 ++++++++++++++++++++++++++++++++
> drivers/bus/cdx/version.map | 11 +++++--
> 4 files changed, 69 insertions(+), 29 deletions(-)
> create mode 100644 drivers/bus/cdx/rte_bus_cdx.h
>
<snip>
> +/* Forward declarations */
> +struct rte_cdx_device;
> +
> +/**
> + * Map the CDX device resources in user space virtual memory address
> + *
> + * Note that driver should not call this function when flag
> + * RTE_CDX_DRV_NEED_MAPPING is set, as EAL will do that for
> + * you when it's on.
> + *
> + * @param dev
> + * A pointer to a rte_cdx_device structure describing the device
> + * to use
> + *
> + * @return
> + * 0 on success, negative on error and positive if no driver
> + * is found for the device.
> + */
> +int rte_cdx_map_device(struct rte_cdx_device *dev);
rte_experimental?
next prev parent reply other threads:[~2023-07-07 8:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 10:39 [PATCH] bus/cdx: provide driver flag for optional resource mapping Abhijit Gangurde
2023-07-04 11:22 ` Gupta, Nipun
2023-07-05 6:52 ` [PATCH v2] " Abhijit Gangurde
2023-07-11 5:51 ` [PATCH v3] " Abhijit Gangurde
2023-07-11 15:05 ` Gupta, Nipun
2023-09-29 15:17 ` David Marchand
2023-10-04 10:06 ` Gangurde, Abhijit
2023-10-04 12:54 ` David Marchand
2023-10-13 11:51 ` Gangurde, Abhijit
2023-10-13 12:15 ` David Marchand
2023-07-07 8:35 ` Gupta, Nipun [this message]
2023-10-16 9:16 ` [PATCH v4 1/1] " Abhijit Gangurde
2023-10-16 15:21 ` Thomas Monjalon
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=CH3PR12MB8308B941FA2D88A6DC50ADABE82DA@CH3PR12MB8308.namprd12.prod.outlook.com \
--to=nipun.gupta@amd.com \
--cc=Ferruh.Yigit@amd.com \
--cc=abhijit.gangurde@amd.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=nikhil.agarwal@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.