From: Nava kishore Manne <nava.manne@xilinx.com>
To: <michal.simek@xilinx.com>, <mdf@kernel.org>, <hao.wu@intel.com>,
<yilun.xu@intel.com>, <trix@redhat.com>,
<gregkh@linuxfoundation.org>, <ronak.jain@xilinx.com>,
<abhyuday.godhasara@xilinx.com>, <rajan.vaja@xilinx.com>,
<nava.manne@xilinx.com>,
<lakshmi.sai.krishna.potthuri@xilinx.com>,
<piyush.mehta@xilinx.com>, <harsha.harsha@xilinx.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-fpga@vger.kernel.org>,
<git@xilinx.com>
Subject: [PATCH 1/3] fpga: mgr: Update the status for fpga-manager
Date: Tue, 24 May 2022 15:17:43 +0530 [thread overview]
Message-ID: <20220524094745.287002-2-nava.manne@xilinx.com> (raw)
In-Reply-To: <20220524094745.287002-1-nava.manne@xilinx.com>
This patch update the below status values for
fpga-manager.
-Device Initialization error.
-Device internal signal error.
-All I/Os are placed in High-Z state.
-Device start-up sequence error.
-Firmware error.
Signed-off-by: Nava kishore Manne <nava.manne@xilinx.com>
---
drivers/fpga/fpga-mgr.c | 13 +++++++++++++
include/linux/fpga/fpga-mgr.h | 6 ++++++
2 files changed, 19 insertions(+)
diff --git a/drivers/fpga/fpga-mgr.c b/drivers/fpga/fpga-mgr.c
index a3595ecc3f79..be693fd531ea 100644
--- a/drivers/fpga/fpga-mgr.c
+++ b/drivers/fpga/fpga-mgr.c
@@ -475,6 +475,19 @@ static ssize_t status_show(struct device *dev,
len += sprintf(buf + len, "reconfig IP protocol error\n");
if (status & FPGA_MGR_STATUS_FIFO_OVERFLOW_ERR)
len += sprintf(buf + len, "reconfig fifo overflow error\n");
+ if (status & FPGA_MGR_STATUS_SECURITY_ERR)
+ len += sprintf(buf + len, "reconfig security error\n");
+ if (status & FPGA_MGR_STATUS_DEVICE_INIT_ERR)
+ len += sprintf(buf + len, "Device Initialization error\n");
+ if (status & FPGA_MGR_STATUS_SIGNAL_ERR)
+ len += sprintf(buf + len, "Device internal signal error\n");
+ if (status & FPGA_MGR_STATUS_HIGH_Z_STATE_ERR)
+ len += sprintf(buf + len,
+ "All I/Os are placed in High-Z state\n");
+ if (status & FPGA_MGR_STATUS_EOS_ERR)
+ len += sprintf(buf + len, "Device start-up sequence error\n");
+ if (status & FPGA_MGR_STATUS_FIRMWARE_REQ_ERR)
+ len += sprintf(buf + len, "firmware error\n");
return len;
}
diff --git a/include/linux/fpga/fpga-mgr.h b/include/linux/fpga/fpga-mgr.h
index 0f9468771bb9..91accba14ba2 100644
--- a/include/linux/fpga/fpga-mgr.h
+++ b/include/linux/fpga/fpga-mgr.h
@@ -172,6 +172,12 @@ struct fpga_manager_ops {
#define FPGA_MGR_STATUS_INCOMPATIBLE_IMAGE_ERR BIT(2)
#define FPGA_MGR_STATUS_IP_PROTOCOL_ERR BIT(3)
#define FPGA_MGR_STATUS_FIFO_OVERFLOW_ERR BIT(4)
+#define FPGA_MGR_STATUS_SECURITY_ERR BIT(5)
+#define FPGA_MGR_STATUS_DEVICE_INIT_ERR BIT(6)
+#define FPGA_MGR_STATUS_SIGNAL_ERR BIT(7)
+#define FPGA_MGR_STATUS_HIGH_Z_STATE_ERR BIT(8)
+#define FPGA_MGR_STATUS_EOS_ERR BIT(9)
+#define FPGA_MGR_STATUS_FIRMWARE_REQ_ERR BIT(10)
/**
* struct fpga_manager - fpga manager structure
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-05-24 9:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 9:47 [PATCH 0/3]Adds status interface for zynqmp-fpga Nava kishore Manne
2022-05-24 9:47 ` Nava kishore Manne [this message]
2022-05-24 9:47 ` [PATCH 2/3] firmware: xilinx: Add pm api function for PL readback Nava kishore Manne
2022-05-24 13:10 ` kernel test robot
2022-05-24 14:41 ` kernel test robot
2022-05-24 9:47 ` [PATCH 3/3] fpga: zynqmp-fpga: Adds status interface Nava kishore Manne
2022-05-28 15:21 ` Xu Yilun
2022-06-07 5:41 ` Nava kishore Manne
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=20220524094745.287002-2-nava.manne@xilinx.com \
--to=nava.manne@xilinx.com \
--cc=abhyuday.godhasara@xilinx.com \
--cc=git@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=hao.wu@intel.com \
--cc=harsha.harsha@xilinx.com \
--cc=lakshmi.sai.krishna.potthuri@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=michal.simek@xilinx.com \
--cc=piyush.mehta@xilinx.com \
--cc=rajan.vaja@xilinx.com \
--cc=ronak.jain@xilinx.com \
--cc=trix@redhat.com \
--cc=yilun.xu@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).