diff options
author | David Gibson <david@gibson.dropbear.id.au> | 2018-03-06 14:45:50 +1100 |
---|---|---|
committer | David Gibson <david@gibson.dropbear.id.au> | 2018-03-06 14:45:50 +1100 |
commit | afbddcd418fbf70467419b91f73cce972482449c (patch) | |
tree | dd93ab89a5daca50504b373ce14ee99a9dbc7cdb | |
parent | 119e27300359b309e27bfd94b506ea5ad24f1cfc (diff) | |
download | device-tree-compiler-afbddcd418fbf70467419b91f73cce972482449c.tar.gz |
Suppress warnings on overlay fragments
Overlay fragments are traditionally named "fragment@NNN" but don't have
have a 'reg' property, amongst other differences from normal nodes. Really
we should treat overlay fragments fundamentally differently, but for the
moment, suppress the common warnings about the fragment names with this
simple hack.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
-rw-r--r-- | checks.c | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -317,6 +317,11 @@ static void check_unit_address_vs_reg(struct check *c, struct dt_info *dti, const char *unitname = get_unitname(node); struct property *prop = get_property(node, "reg"); + if (get_subnode(node, "__overlay__")) { + /* HACK: Overlay fragments are a special case */ + return; + } + if (!prop) { prop = get_property(node, "ranges"); if (prop && !prop->val.len) |