linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sonal Santan <sonal.santan@xilinx.com>
To: <linux-kernel@vger.kernel.org>
Cc: Sonal Santan <sonal.santan@xilinx.com>,
	<linux-fpga@vger.kernel.org>, <maxz@xilinx.com>,
	<lizhih@xilinx.com>, <michal.simek@xilinx.com>,
	<stefanos@xilinx.com>, <devicetree@vger.kernel.org>
Subject: [PATCH Xilinx Alveo libfdt prep 1/1] Export subset of libfdt symbols for use by other drivers.
Date: Sat, 28 Nov 2020 15:56:59 -0800	[thread overview]
Message-ID: <20201128235659.24679-2-sonals@xilinx.com> (raw)
In-Reply-To: <20201128235659.24679-1-sonals@xilinx.com>

From: Sonal Santan <sonal.santan@xilinx.com>

Some drivers may want to use device tree as metadata format to discover HW
subsystems behind PCIe BAR. This is particularly useful for PCIe FPGA
devices.

Signed-off-by: Sonal Santan <sonal.santan@xilinx.com>
---
 lib/fdt.c            |  6 ++++++
 lib/fdt_empty_tree.c |  3 +++
 lib/fdt_ro.c         | 11 +++++++++++
 lib/fdt_rw.c         |  6 ++++++
 4 files changed, 26 insertions(+)

diff --git a/lib/fdt.c b/lib/fdt.c
index 97f20069fc37..9747513b50e7 100644
--- a/lib/fdt.c
+++ b/lib/fdt.c
@@ -1,2 +1,8 @@
 #include <linux/libfdt_env.h>
+#include <linux/export.h>
 #include "../scripts/dtc/libfdt/fdt.c"
+
+EXPORT_SYMBOL_GPL(fdt_next_node);
+EXPORT_SYMBOL_GPL(fdt_first_subnode);
+EXPORT_SYMBOL_GPL(fdt_next_subnode);
+EXPORT_SYMBOL_GPL(fdt_subnode_offset);
diff --git a/lib/fdt_empty_tree.c b/lib/fdt_empty_tree.c
index 5d30c58150ad..3dab578c9d22 100644
--- a/lib/fdt_empty_tree.c
+++ b/lib/fdt_empty_tree.c
@@ -1,2 +1,5 @@
 #include <linux/libfdt_env.h>
+#include <linux/export.h>
 #include "../scripts/dtc/libfdt/fdt_empty_tree.c"
+
+EXPORT_SYMBOL_GPL(fdt_create_empty_tree);
diff --git a/lib/fdt_ro.c b/lib/fdt_ro.c
index f73c04ea7be4..ec96cf3d0d7a 100644
--- a/lib/fdt_ro.c
+++ b/lib/fdt_ro.c
@@ -1,2 +1,13 @@
 #include <linux/libfdt_env.h>
+#include <linux/export.h>
 #include "../scripts/dtc/libfdt/fdt_ro.c"
+
+EXPORT_SYMBOL_GPL(fdt_getprop_by_offset);
+EXPORT_SYMBOL_GPL(fdt_node_check_compatible);
+EXPORT_SYMBOL_GPL(fdt_get_name);
+EXPORT_SYMBOL_GPL(fdt_next_property_offset);
+EXPORT_SYMBOL_GPL(fdt_getprop);
+EXPORT_SYMBOL_GPL(fdt_node_offset_by_compatible);
+EXPORT_SYMBOL_GPL(fdt_parent_offset);
+EXPORT_SYMBOL_GPL(fdt_stringlist_get);
+EXPORT_SYMBOL_GPL(fdt_first_property_offset);
diff --git a/lib/fdt_rw.c b/lib/fdt_rw.c
index 0c1f0f4a4b13..ec3939ed3d7d 100644
--- a/lib/fdt_rw.c
+++ b/lib/fdt_rw.c
@@ -1,2 +1,8 @@
 #include <linux/libfdt_env.h>
+#include <linux/export.h>
 #include "../scripts/dtc/libfdt/fdt_rw.c"
+
+EXPORT_SYMBOL_GPL(fdt_del_node);
+EXPORT_SYMBOL_GPL(fdt_add_subnode);
+EXPORT_SYMBOL_GPL(fdt_pack);
+EXPORT_SYMBOL_GPL(fdt_setprop);
-- 
2.17.1


      reply	other threads:[~2020-11-28 23:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-28 23:56 [PATCH Xilinx Alveo libfdt prep 0/1] Expose libfdt for use by Alveo/XRT Sonal Santan
2020-11-28 23:56 ` Sonal Santan [this message]

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=20201128235659.24679-2-sonals@xilinx.com \
    --to=sonal.santan@xilinx.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizhih@xilinx.com \
    --cc=maxz@xilinx.com \
    --cc=michal.simek@xilinx.com \
    --cc=stefanos@xilinx.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).