qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "john.liuli" <john.liuli@huawei.com>
To: peter.crosthwaite@xilinx.com, agraf@suse.de
Cc: Li Liu <john.liuli@huawei.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 1/6] device_tree.c: Introduce a function to check multiple strings for dts
Date: Mon, 25 Aug 2014 12:00:32 +0800	[thread overview]
Message-ID: <1408939237-8444-2-git-send-email-john.liuli@huawei.com> (raw)
In-Reply-To: <1408939237-8444-1-git-send-email-john.liuli@huawei.com>

From: Li Liu <john.liuli@huawei.com>

dts property's value can be multiple strings. So introduce a function
to check a data with a given length to see if it is all printable and
has a valid terminator. It can contain either a single string, or
multiple strings each of non-zero length.

Signed-off-by: Li Liu <john.liuli@huawei.com>
---
 device_tree.c |   32 ++++++++++++++++++++++++++++++++
 1 file changed, 32 insertions(+)

diff --git a/device_tree.c b/device_tree.c
index ca83504..29d9acc 100644
--- a/device_tree.c
+++ b/device_tree.c
@@ -345,3 +345,35 @@ int qemu_fdt_setprop_sized_cells_from_array(void *fdt,
     return qemu_fdt_setprop(fdt, node_path, property, propcells,
                             cellnum * sizeof(uint32_t));
 }
+
+/*
+ * Check a data of a given length to see if it is all printable and
+ * has a valid terminator. The data can contain either a single string,
+ * or multiple strings each of non-zero length.
+ */
+static int dts_is_printable_strings(const void *data, int len)
+{
+    const char *str = (char *)data;
+    int substrs = 0;
+    int substr_len = 0;
+    int i;
+
+    for (i = 0; i < len; i++) {
+        if (str[i] == '\0') {
+            if (substr_len) {
+                substr_len = 0;
+                substrs++;
+                continue;
+            } else {
+                /* substr is empty */
+                return 0;
+            }
+        } else if (isprint(str[i])) {
+            substr_len++;
+        } else {
+            return 0;
+        }
+    }
+
+    return substrs && !substr_len;
+}
-- 
1.7.9.5

  reply	other threads:[~2014-08-25  4:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-25  4:00 [Qemu-devel] [PATCH 0/6] add dumpdts ability to convert dtb to dts john.liuli
2014-08-25  4:00 ` john.liuli [this message]
2014-08-25  4:00 ` [Qemu-devel] [PATCH 2/6] device_tree.c: dump three kind data types of dts to a file desciptor john.liuli
2014-08-25  4:00 ` [Qemu-devel] [PATCH 3/6] device_tree.c: Format a blob in memory as dts stream and dump to a file john.liuli
2014-08-25  4:00 ` [Qemu-devel] [PATCH 4/6] device_tree.c: add the main function to analyse the parameter 'dumpdts' john.liuli
2014-08-25  4:00 ` [Qemu-devel] [PATCH 5/6] machine: add 'dumpdts' parameter to 'machine' optslist john.liuli
2014-08-25  4:00 ` [Qemu-devel] [PATCH 6/6] arm: Allow dumping generated dtb to dts file john.liuli
2014-08-25 12:22 ` [Qemu-devel] [PATCH 0/6] add dumpdts ability to convert dtb to dts Peter Maydell
2014-08-26  2:04   ` Li Liu
2014-08-26  2:41     ` Peter Crosthwaite

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=1408939237-8444-2-git-send-email-john.liuli@huawei.com \
    --to=john.liuli@huawei.com \
    --cc=agraf@suse.de \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).