From: Xu Yilun <yilun.xu@linux.intel.com>
To: Nava kishore Manne <nava.kishore.manne@amd.com>
Cc: git@amd.com, mdf@kernel.org, hao.wu@intel.com,
yilun.xu@intel.com, trix@redhat.com, robh@kernel.org,
saravanak@google.com, linux-fpga@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [RFC 1/1] of-fpga-region: Add sysfs interface support for FPGA configuration
Date: Mon, 29 Jul 2024 23:56:58 +0800 [thread overview]
Message-ID: <Zqe7yoAMIJ+Qv8YC@yilunxu-OptiPlex-7050> (raw)
In-Reply-To: <20240726063819.2274324-2-nava.kishore.manne@amd.com>
On Fri, Jul 26, 2024 at 12:08:19PM +0530, Nava kishore Manne wrote:
> Adds sysfs interface as part of the of-fpga-region. This newly added
> sysfs interface uses Device Tree Overlay (DTO) files to configure/reprogram
> an FPGA while an operating system is running.This solution will not change
> the existing sequence When a DT overlay that targets an FPGA Region is
> applied.
> - Disable appropriate FPGA bridges.
> - Program the FPGA using the FPGA manager.
> - Enable the FPGA bridges.
> - The Device Tree overlay is accepted into the live tree.
> - Child devices are populated.
>
> When the overlay is removed, the child nodes will be removed, and the FPGA
> Region will disable the bridges.
>
> Usage:
> To configure/reprogram an FPGA region:
> echo "fpga.dtbo" > /sys/class/fpga_region/<region>/device/load
IIRC, last time we are considering some generic interface for both OF &
non-OF FPGA region, but this is still OF specific.
Thanks,
Yilun
next prev parent reply other threads:[~2024-07-29 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 6:38 [RFC 0/1]Add user space interaction for FPGA programming Nava kishore Manne
2024-07-26 6:38 ` [RFC 1/1] of-fpga-region: Add sysfs interface support for FPGA configuration Nava kishore Manne
2024-07-29 15:56 ` Xu Yilun [this message]
2024-08-01 4:25 ` Manne, Nava kishore
2024-08-05 18:20 ` Xu Yilun
2024-09-17 11:16 ` Manne, Nava kishore
2024-09-18 8:19 ` Xu Yilun
2024-09-23 4:28 ` Manne, Nava kishore
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=Zqe7yoAMIJ+Qv8YC@yilunxu-OptiPlex-7050 \
--to=yilun.xu@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=git@amd.com \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=nava.kishore.manne@amd.com \
--cc=robh@kernel.org \
--cc=saravanak@google.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