From: Jerin Jacob <jerinj@marvell.com>
To: Tomasz Duszynski <tduszynski@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Jakub Palider <jpalider@marvell.com>,
Tomasz Duszynski <tduszynski@marvell.com>
Subject: RE: [PATCH v4] raw/cnxk_gpio: switch to character based GPIO interface
Date: Tue, 1 Apr 2025 11:09:18 +0000 [thread overview]
Message-ID: <BY3PR18MB47855962B0DDF25508E26214C8AC2@BY3PR18MB4785.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250327091222.2472797-1-tduszynski@marvell.com>
> -----Original Message-----
> From: Tomasz Duszynski <tduszynski@marvell.com>
> Sent: Thursday, March 27, 2025 2:42 PM
> To: dev@dpdk.org; Jakub Palider <jpalider@marvell.com>; Tomasz Duszynski
> <tduszynski@marvell.com>
> Cc: Jerin Jacob <jerinj@marvell.com>
> Subject: [PATCH v4] raw/cnxk_gpio: switch to character based GPIO interface
>
> The direct passthrough interrupt mechanism, which allowed bypassing the
> kernel, was obscure and is no longer supported. So this driver won't work with
> latest SDK kernels. Additionally, the sysfs GPIO control interface has been
> deprecated by Linux kernel itself.
>
> That said, this change updates the PMD to use the current GPIO interface
> ensuring compatibility with current kernel standards while improving
> maintainability and security.
>
> Signed-off-by: Tomasz Duszynski <tduszynski@marvell.com>
> ---
> v2:
> - compile conditionally based on GPIO_V2_PRESENT
> v3:
> - fix compilation issues due to missing structure member
> - quiesce compiler warnings about maybe unused parameters
> v4:
> - rename GPIO_V2_PRESENT to CNXK_GPIO_V2_PRESENT to indicate
> it's PMD specific
Applied to dpdk-next-net-mrvl/for-main. Thanks
prev parent reply other threads:[~2025-04-01 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 12:57 [PATCH] " Tomasz Duszynski
2025-03-24 8:28 ` [PATCH v2] " Tomasz Duszynski
2025-03-25 4:14 ` [PATCH v3] " Tomasz Duszynski
2025-03-27 9:12 ` [PATCH v4] " Tomasz Duszynski
2025-04-01 11:09 ` Jerin Jacob [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=BY3PR18MB47855962B0DDF25508E26214C8AC2@BY3PR18MB4785.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=jpalider@marvell.com \
--cc=tduszynski@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).