From: Peng Fan <van.freenix@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] fdt: introduce fdtdec_get_child_count
Date: Mon, 1 Feb 2016 13:31:15 +0800 [thread overview]
Message-ID: <1454304675-3768-1-git-send-email-van.freenix@gmail.com> (raw)
Introduce fdtdec_get_child_count for get the number of subnodes
of one parent node.
Signed-off-by: Peng Fan <van.freenix@gmail.com>
Cc: Simon Glass <sjg@chromium.org>
---
V2:
correct spell error.
renamed to fdtdec_get_child_count, move code to lib/fdtdec.c and add
prototype in include/fdtdec.h
include/fdtdec.h | 9 +++++++++
lib/fdtdec.c | 11 +++++++++++
2 files changed, 20 insertions(+)
diff --git a/include/fdtdec.h b/include/fdtdec.h
index dd82916..d1c29a8 100644
--- a/include/fdtdec.h
+++ b/include/fdtdec.h
@@ -722,6 +722,15 @@ const u32 *fdtdec_locate_array(const void *blob, int node,
*/
int fdtdec_get_bool(const void *blob, int node, const char *prop_name);
+/*
+ * Count child nodes of one parent node.
+ *
+ * @param blob FDT blob
+ * @param node parent node
+ * @return number of child node; 0 if there is not child node
+ */
+int fdtdec_get_child_count(const void *blob, int node);
+
/**
* Look in the FDT for a config item with the given name and return its value
* as a 32-bit integer. The property must have at least 4 bytes of data. The
diff --git a/lib/fdtdec.c b/lib/fdtdec.c
index 0eb56af..1b1ca02 100644
--- a/lib/fdtdec.c
+++ b/lib/fdtdec.c
@@ -831,6 +831,17 @@ int fdtdec_parse_phandle_with_args(const void *blob, int src_node,
return rc;
}
+int fdtdec_get_child_count(const void *blob, int node)
+{
+ int subnode;
+ int num = 0;
+
+ fdt_for_each_subnode(blob, subnode, node)
+ num++;
+
+ return num;
+}
+
int fdtdec_get_byte_array(const void *blob, int node, const char *prop_name,
u8 *array, int count)
{
--
2.6.2
next reply other threads:[~2016-02-01 5:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 5:31 Peng Fan [this message]
2016-02-02 0:05 ` [U-Boot] [PATCH V2] fdt: introduce fdtdec_get_child_count Simon Glass
2016-02-06 13:49 ` Anatolij Gustschin
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=1454304675-3768-1-git-send-email-van.freenix@gmail.com \
--to=van.freenix@gmail.com \
--cc=u-boot@lists.denx.de \
/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