From: Wei Huang <wei.huang@intel.com>
To: dev@dpdk.org, thomas@monjalon.net, nipun.gupta@nxp.com,
hemant.agrawal@nxp.com
Cc: stable@dpdk.org, rosen.xu@intel.com, tianfei.zhang@intel.com,
qi.z.zhang@intel.com, Wei Huang <wei.huang@intel.com>
Subject: [PATCH v3 0/4] introduce PMCI driver
Date: Fri, 17 Jun 2022 03:19:31 -0400 [thread overview]
Message-ID: <1655450375-10739-1-git-send-email-wei.huang@intel.com> (raw)
In-Reply-To: <1654827900-10023-1-git-send-email-wei.huang@intel.com>
The first patch introduce PMCI base driver to provide interface to access
MAX10 register.
The second patch support new board information.
The third patch update flash access interfaces.
The fourth patch support new board sensors.
Changes from v2:
1. split PMCI driver into three parts: base driver, flash driver and
sensor driver.
2. remove RSU related patch from this patch set.
Wei Huang (4):
raw/ifpga/base: add PMCI base driver
raw/ifpga/base: update board information
raw/ifpga/base: update flash operation interface
raw/ifpga/base: add PMCI sensor driver
drivers/raw/ifpga/base/ifpga_api.c | 9 +
drivers/raw/ifpga/base/ifpga_defines.h | 103 ++-
drivers/raw/ifpga/base/ifpga_feature_dev.c | 2 +
drivers/raw/ifpga/base/ifpga_feature_dev.h | 3 +
drivers/raw/ifpga/base/ifpga_fme.c | 271 +++++--
drivers/raw/ifpga/base/ifpga_fme_error.c | 2 +
drivers/raw/ifpga/base/ifpga_port_error.c | 2 +-
drivers/raw/ifpga/base/opae_hw_api.c | 49 ++
drivers/raw/ifpga/base/opae_hw_api.h | 3 +
drivers/raw/ifpga/base/opae_intel_max10.c | 940 +++++++++++++++++++++--
drivers/raw/ifpga/base/opae_intel_max10.h | 313 +++++++-
drivers/raw/ifpga/base/opae_osdep.h | 43 +-
drivers/raw/ifpga/base/osdep_rte/osdep_generic.h | 10 +
13 files changed, 1556 insertions(+), 194 deletions(-)
--
1.8.3.1
next prev parent reply other threads:[~2022-06-17 7:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 1:51 [PATCH v1 0/2] Update rsu implementation Wei Huang
2022-05-25 1:51 ` [PATCH v1 1/2] raw/ifpga/base: add pmci driver Wei Huang
2022-05-25 1:51 ` [PATCH v1 2/2] raw/ifpga: update secure rsu Wei Huang
2022-06-10 2:24 ` [PATCH v2 0/2] update rsu implementation Wei Huang
2022-06-10 2:24 ` [PATCH v2 1/2] raw/ifpga/base: add pmci driver Wei Huang
2022-06-13 7:01 ` Zhang, Tianfei
2022-06-13 7:29 ` Huang, Wei
2022-06-10 2:25 ` [PATCH v2 2/2] raw/ifpga: update secure rsu Wei Huang
2022-06-17 7:19 ` Wei Huang [this message]
2022-06-17 7:19 ` [PATCH v3 1/4] raw/ifpga/base: add PMCI base driver Wei Huang
2022-06-17 8:57 ` Zhang, Tianfei
2022-06-17 14:41 ` Xu, Rosen
2022-06-17 7:19 ` [PATCH v3 2/4] raw/ifpga/base: update board information Wei Huang
2022-06-17 8:57 ` Zhang, Tianfei
2022-06-17 14:42 ` Xu, Rosen
2022-06-17 7:19 ` [PATCH v3 3/4] raw/ifpga/base: update flash operation interface Wei Huang
2022-06-17 8:58 ` Zhang, Tianfei
2022-06-17 14:42 ` Xu, Rosen
2022-06-17 7:19 ` [PATCH v3 4/4] raw/ifpga/base: add PMCI sensor driver Wei Huang
2022-06-17 8:58 ` Zhang, Tianfei
2022-06-17 14:43 ` Xu, Rosen
2022-06-20 15:35 ` [PATCH v3 0/4] introduce PMCI driver Thomas Monjalon
2023-09-29 15:31 ` [PATCH v2 0/2] update rsu implementation David Marchand
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=1655450375-10739-1-git-send-email-wei.huang@intel.com \
--to=wei.huang@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=nipun.gupta@nxp.com \
--cc=qi.z.zhang@intel.com \
--cc=rosen.xu@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=tianfei.zhang@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).