From: Alan Tull <atull@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Moritz Fischer <mdf@kernel.org>, Alan Tull <atull@kernel.org>,
linux-kernel@vger.kernel.org, linux-fpga@vger.kernel.org
Subject: [PATCH v6 07/18] fpga: region: check for child regions before allocing image info
Date: Wed, 15 Nov 2017 14:20:17 -0600 [thread overview]
Message-ID: <1510777228-4291-8-git-send-email-atull@kernel.org> (raw)
In-Reply-To: <1510777228-4291-1-git-send-email-atull@kernel.org>
During a device tree overlay pre-apply notification, the check
for child FPGA regions can happen slightly earlier. This saves
us from allocating the FPGA image info that just gets thrown
away.
This is a baby step in refactoring the FPGA region code to
separate out common FPGA region code from FPGA region
Device Tree overlay support.
Signed-off-by: Alan Tull <atull@kernel.org>
Acked-by: Moritz Fischer <mdf@kernel.org>
---
v2: split out from another patch
v3: s/dev/®ion->dev/ in one place
add Moritz' ack
v4: no change to this patch in this version of patchset
v5: no change to this patch in this version of patchset
v6: no change to this patch in this version of patchset
---
drivers/fpga/fpga-region.c | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/drivers/fpga/fpga-region.c b/drivers/fpga/fpga-region.c
index d78f444..afac543 100644
--- a/drivers/fpga/fpga-region.c
+++ b/drivers/fpga/fpga-region.c
@@ -355,15 +355,19 @@ static int fpga_region_notify_pre_apply(struct fpga_region *region,
const char *firmware_name;
int ret;
- info = fpga_image_info_alloc(dev);
- if (!info)
- return -ENOMEM;
-
- /* Reject overlay if child FPGA Regions have firmware-name property */
+ /*
+ * Reject overlay if child FPGA Regions added in the overlay have
+ * firmware-name property (would mean that an FPGA region that has
+ * not been added to the live tree yet is doing FPGA programming).
+ */
ret = child_regions_with_firmware(nd->overlay);
if (ret)
return ret;
+ info = fpga_image_info_alloc(dev);
+ if (!info)
+ return -ENOMEM;
+
/* Read FPGA region properties from the overlay */
if (of_property_read_bool(nd->overlay, "partial-fpga-config"))
info->flags |= FPGA_MGR_PARTIAL_RECONFIG;
--
2.7.4
next prev parent reply other threads:[~2017-11-15 20:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 20:20 [PATCH v6 00/18] patches for FPGA Alan Tull
2017-11-15 20:20 ` [PATCH v6 01/18] fpga: bridge: support getting bridge from device Alan Tull
2017-11-15 20:20 ` [PATCH v6 02/18] fpga: mgr: API change to replace fpga load functions with single function Alan Tull
2017-11-15 20:20 ` [PATCH v6 03/18] fpga: mgr: separate getting/locking FPGA manager Alan Tull
2017-11-15 20:20 ` [PATCH v6 04/18] fpga: region: use dev_err instead of pr_err Alan Tull
2017-11-15 20:20 ` [PATCH v6 05/18] fpga: region: remove unneeded of_node_get and put Alan Tull
2017-11-15 20:20 ` [PATCH v6 06/18] fpga: region: get mgr early on Alan Tull
2017-11-15 20:20 ` Alan Tull [this message]
2017-11-15 20:20 ` [PATCH v6 08/18] fpga: region: fix slow warning with more than one overlay Alan Tull
2017-11-15 20:20 ` [PATCH v6 09/18] fpga: region: use image info as parameter for programming region Alan Tull
2017-11-15 20:20 ` [PATCH v6 10/18] fpga: region: separate out code that parses the overlay Alan Tull
2017-11-15 20:20 ` [PATCH v6 11/18] fpga: region: add fpga-region.h header Alan Tull
2017-11-15 20:20 ` [PATCH v6 12/18] fpga: region: rename some functions prior to moving Alan Tull
2017-11-15 20:20 ` [PATCH v6 13/18] fpga: region: add register/unregister functions Alan Tull
2017-11-15 20:20 ` [PATCH v6 14/18] fpga: region: add fpga_region_class_find Alan Tull
2017-11-15 20:20 ` [PATCH v6 15/18] fpga: region: move device tree support to of-fpga-region.c Alan Tull
2017-11-15 20:20 ` [PATCH v6 16/18] fpga: of-fpga-region: accept overlays that don't program FPGA Alan Tull
2017-11-15 20:20 ` [PATCH v6 17/18] fpga: clean up fpga Kconfig Alan Tull
2017-11-15 20:20 ` [PATCH v6 18/18] fpga: add attribute groups Alan Tull
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=1510777228-4291-8-git-send-email-atull@kernel.org \
--to=atull@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
/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
Powered by JetHome