From: Marco Pagani <marco.pagani@linux.dev>
To: Moritz Fischer <mdf@kernel.org>, Xu Yilun <yilun.xu@intel.com>,
Tom Rix <trix@redhat.com>
Cc: Marco Pagani <marco.pagani@linux.dev>,
linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH] fpga: region: Add support for FPGA region variants
Date: Mon, 8 Jun 2026 18:42:45 +0200 [thread overview]
Message-ID: <20260608164247.1998417-1-marco.pagani@linux.dev> (raw)
This RFC proposes a proof-of-concept implementation of FPGA region
variants, a mechanism that introduces a common way to handle
dynamic partial reconfiguration from userspace. The proposed approach
is safe and aligned with the mainline kernel's stance on hardware
management by constraining the hardware to a mutually exclusive set
of configurations (variants) defined upfront. This is a realistic
assumption for FPGAs, as regions are typically statically defined and
synthesized during the system design phase. To keep the architecture
realistic, the following additional constraints are introduced:
(i) variants cannot be nested, and (ii) variants cannot contain FPGA
bridges.
The interface and core logic for the variant mechanism are defined
in the fpga-region and implemented in a backwards-compatible way.
The fpga-region now optionally exports sysfs attributes that allow
the user to reconfigure a region that supports variants by selecting
one variant a list of pre-defined variants. Concrete regions can enable
variant support by implementing the new apply_variant and remove_variant
methods and adding them to fpga_region_info before registration.
As part of this RFC, the of-fpga-region concrete region has been extended
to implement the variant interface. Variants are statically specified in
the device tree using an fpga-variants node. Additionally, it introduces
a firmware-cached property to cache bitstreams in memory, enabling a fast
reconfiguration path for real-time (latency-sensitive) applications.
Below is an example of how variants can be statically defined in the
device tree under this architecture:
fake_mgr: fpga-mgr@0 {
compatible = "linux,fake-fpga-mgr";
};
fpga_region: fpga-region@0 {
compatible = "fpga-region";
#address-cells = <2>;
#size-cells = <2>;
ranges;
/* FPGA region properties */
fpga-mgr = <&fake_mgr>;
partial-fpga-config;
region-unfreeze-timeout-us = <10000>;
/* Base variant */
base-variant = "variant-1";
/* Variants container node */
fpga-variants {
#address-cells = <2>;
#size-cells = <2>;
ranges;
variant-1 {
firmware-name = "variant1-image.bin";
#address-cells = <2>;
#size-cells = <2>;
ranges;
variant_1_ip: ip_1@10000 {
compatible = "fake,ip_1";
reg = <0x0 0x10000 0x0 0x1000>;
};
};
variant-2 {
firmware-name = "variant2-image.bin";
firmware-cached;
#address-cells = <2>;
#size-cells = <2>;
ranges;
variant_2_ip: ip_2@10000 {
compatible = "fake,ip_2";
reg = <0x0 0x20000 0x0 0x1000>;
};
};
};
};
Marco Pagani (2):
fpga: region: Add support for FPGA region variants
fpga: of-fpga-region: Add support for region variants
drivers/fpga/fpga-region.c | 171 +++++++++++++++++++
drivers/fpga/of-fpga-region.c | 272 ++++++++++++++++++++++++++++++-
include/linux/fpga/fpga-region.h | 32 ++++
3 files changed, 473 insertions(+), 2 deletions(-)
--
2.54.0
next reply other threads:[~2026-06-08 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 16:42 Marco Pagani [this message]
2026-06-08 16:42 ` [RFC PATCH fpga/for-next 1/2] fpga: region: Add support for FPGA region variants Marco Pagani
2026-06-08 16:42 ` [RFC PATCH fpga/for-next 2/2] fpga: of-fpga-region: Add support for " Marco Pagani
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=20260608164247.1998417-1-marco.pagani@linux.dev \
--to=marco.pagani@linux.dev \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--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