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 3/3] fpga: zynqmp-fpga: Adds status interface
Date: Tue, 24 May 2022 15:17:45 +0530 [thread overview]
Message-ID: <20220524094745.287002-4-nava.manne@xilinx.com> (raw)
In-Reply-To: <20220524094745.287002-1-nava.manne@xilinx.com>
Adds status interface for zynqmp-fpga, It's a read only
interface which allows the user to get the PL status.
Usage:
To read the PL configuration status
cat /sys/class/fpga_manager/<fpga>/status
Signed-off-by: Nava kishore Manne <nava.manne@xilinx.com>
---
drivers/fpga/zynqmp-fpga.c | 52 ++++++++++++++++++++++++++++++++++++++
1 file changed, 52 insertions(+)
diff --git a/drivers/fpga/zynqmp-fpga.c b/drivers/fpga/zynqmp-fpga.c
index c60f20949c47..07c7b7326726 100644
--- a/drivers/fpga/zynqmp-fpga.c
+++ b/drivers/fpga/zynqmp-fpga.c
@@ -14,6 +14,19 @@
/* Constant Definitions */
#define IXR_FPGA_DONE_MASK BIT(3)
+#define READ_DMA_SIZE 256U
+
+/* Error Register */
+#define IXR_FPGA_ERR_CRC_ERR BIT(0)
+#define IXR_FPGA_ERR_SECURITY_ERR BIT(16)
+
+/* Signal Status Register. For details refer ug570 */
+#define IXR_FPGA_END_OF_STARTUP BIT(4)
+#define IXR_FPGA_GST_CFG_B BIT(5)
+#define IXR_FPGA_INIT_B_INTERNAL BIT(11)
+#define IXR_FPGA_DONE_INTERNAL_SIGNAL BIT(13)
+
+#define IXR_FPGA_CONFIG_STAT_OFFSET 7U
/**
* struct zynqmp_fpga_priv - Private data structure
@@ -77,8 +90,47 @@ static enum fpga_mgr_states zynqmp_fpga_ops_state(struct fpga_manager *mgr)
return FPGA_MGR_STATE_UNKNOWN;
}
+static u64 zynqmp_fpga_ops_status(struct fpga_manager *mgr)
+{
+ unsigned int *buf, reg_val;
+ dma_addr_t dma_addr;
+ u64 status = 0;
+ int ret;
+
+ buf = dma_alloc_coherent(mgr->dev.parent, READ_DMA_SIZE,
+ &dma_addr, GFP_KERNEL);
+ if (!buf)
+ return -ENOMEM;
+
+ ret = zynqmp_pm_fpga_read(IXR_FPGA_CONFIG_STAT_OFFSET, dma_addr,
+ PM_FPGA_READ_CONFIG_REG, ®_val);
+ if (ret) {
+ status = FPGA_MGR_STATUS_FIRMWARE_REQ_ERR;
+ goto free_dmabuf;
+ }
+
+ if (reg_val & IXR_FPGA_ERR_CRC_ERR)
+ status |= FPGA_MGR_STATUS_CRC_ERR;
+ if (reg_val & IXR_FPGA_ERR_SECURITY_ERR)
+ status |= FPGA_MGR_STATUS_SECURITY_ERR;
+ if (!(reg_val & IXR_FPGA_INIT_B_INTERNAL))
+ status |= FPGA_MGR_STATUS_DEVICE_INIT_ERR;
+ if (!(reg_val & IXR_FPGA_DONE_INTERNAL_SIGNAL))
+ status |= FPGA_MGR_STATUS_SIGNAL_ERR;
+ if (!(reg_val & IXR_FPGA_GST_CFG_B))
+ status |= FPGA_MGR_STATUS_HIGH_Z_STATE_ERR;
+ if (!(reg_val & IXR_FPGA_END_OF_STARTUP))
+ status |= FPGA_MGR_STATUS_EOS_ERR;
+
+free_dmabuf:
+ dma_free_coherent(mgr->dev.parent, READ_DMA_SIZE, buf, dma_addr);
+
+ return status;
+}
+
static const struct fpga_manager_ops zynqmp_fpga_ops = {
.state = zynqmp_fpga_ops_state,
+ .status = zynqmp_fpga_ops_status,
.write_init = zynqmp_fpga_ops_write_init,
.write = zynqmp_fpga_ops_write,
};
--
2.25.1
next prev parent reply other threads:[~2022-05-24 9:52 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 ` [PATCH 1/3] fpga: mgr: Update the status for fpga-manager Nava kishore Manne
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 ` Nava kishore Manne [this message]
2022-05-28 15:21 ` [PATCH 3/3] fpga: zynqmp-fpga: Adds status interface 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-4-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).