From: Jerin Jacob <jerinjacobk@gmail.com>
To: Srikanth Yalavarthi <syalavarthi@marvell.com>
Cc: dev@dpdk.org, sshankarnara@marvell.com, jerinj@marvell.com
Subject: Re: [PATCH 1/1] usertools/devbind: add ml device class
Date: Mon, 13 Mar 2023 23:00:50 +0530 [thread overview]
Message-ID: <CALBAE1O3OgMcnt1+_tugn-a-a3NLV5WKcVhH7P5RBsUrfdyHSw@mail.gmail.com> (raw)
In-Reply-To: <20230313172349.11716-1-syalavarthi@marvell.com>
On Mon, Mar 13, 2023 at 10:53 PM Srikanth Yalavarthi
<syalavarthi@marvell.com> wrote:
>
> Added new ML device class and support for cnxk ML device.
Please also add missing documentation connection at
https://doc.dpdk.org/guides/platform/cnxk.html
>
> Signed-off-by: Srikanth Yalavarthi <syalavarthi@marvell.com>
> ---
> usertools/dpdk-devbind.py | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/usertools/dpdk-devbind.py b/usertools/dpdk-devbind.py
> index 4d9c1be666..a278f5e7f3 100755
> --- a/usertools/dpdk-devbind.py
> +++ b/usertools/dpdk-devbind.py
> @@ -75,6 +75,9 @@
> virtio_blk = {'Class': '01', 'Vendor': "1af4", 'Device': '1001,1042',
> 'SVendor': None, 'SDevice': None}
>
> +cnxk_ml = {'Class': '08', 'Vendor': '177d', 'Device': 'a092',
> + 'SVendor': None, 'SDevice': None}
> +
> network_devices = [network_class, cavium_pkx, avp_vnic, ifpga_class]
> baseband_devices = [acceleration_class]
> crypto_devices = [encryption_class, intel_processor_class]
> @@ -84,6 +87,7 @@
> mempool_devices = [cavium_fpa, cnxk_npa]
> compress_devices = [cavium_zip]
> regex_devices = [cn9k_ree]
> +ml_devices = [cnxk_ml]
> misc_devices = [cnxk_bphy, cnxk_bphy_cgx, cnxk_inl_dev,
> intel_ntb_skx, intel_ntb_icx,
> virtio_blk]
> @@ -618,6 +622,9 @@ def show_status():
> if status_dev in ["regex", "all"]:
> show_device_status(regex_devices, "Regex")
>
> + if status_dev in ["ml", "all"]:
> + show_device_status(ml_devices, "ML")
> +
>
> def pci_glob(arg):
> '''Returns a list containing either:
> @@ -672,7 +679,7 @@ def parse_args():
> '--status-dev',
> help="Print the status of given device group.",
> choices=['baseband', 'compress', 'crypto', 'dma', 'event',
> - 'mempool', 'misc', 'net', 'regex'])
> + 'mempool', 'misc', 'net', 'regex', 'ml'])
> bind_group = parser.add_mutually_exclusive_group()
> bind_group.add_argument(
> '-b',
> @@ -758,6 +765,7 @@ def do_arg_actions():
> get_device_details(mempool_devices)
> get_device_details(compress_devices)
> get_device_details(regex_devices)
> + get_device_details(ml_devices)
> get_device_details(misc_devices)
> show_status()
>
> @@ -781,6 +789,7 @@ def main():
> get_device_details(mempool_devices)
> get_device_details(compress_devices)
> get_device_details(regex_devices)
> + get_device_details(ml_devices)
> get_device_details(misc_devices)
> do_arg_actions()
>
> --
> 2.17.1
>
next prev parent reply other threads:[~2023-03-13 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 17:23 Srikanth Yalavarthi
2023-03-13 17:30 ` Jerin Jacob [this message]
2023-03-13 17:41 ` [EXT] " Srikanth Yalavarthi
2023-03-14 6:31 ` Jerin Jacob
2023-03-19 16:42 ` 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=CALBAE1O3OgMcnt1+_tugn-a-a3NLV5WKcVhH7P5RBsUrfdyHSw@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=sshankarnara@marvell.com \
--cc=syalavarthi@marvell.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).