From: Ray Clinton <mr.ray.clinton@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org
Subject: of_n_{addr,size}_cells(struct device_node *np) - Allow for returning value of node passed in
Date: Fri, 29 Jun 2018 09:45:28 -0400 [thread overview]
Message-ID: <CAPMnawsaPg-KogsyfeMEdr7ykyux9HDBy8s7jfn1KOZAdeVnCA@mail.gmail.com> (raw)
(I accidentally sent this originally with HTML formatting, sorry if
you are getting this twice.)
Hi,
I only just started doing anything with kernel development, this is my
first email on this list, so I'm sorry if I ask a dumb question or
mess up on any rules of etiquette, I'm trying to follow them.
I'm sure there is a reason for this, but of_n_{addr,size}_cells() will
only return a parent's #address-cells or #size-cells values. I realize
of_property_read_u32(np, "#address-cells", &cells), for example, could
be called on the current node to get that value, but is seems to be
that of_n_{addr,size}_cells() is a little bit of a misleading name; I
expected it to return the above mentioned values of the node passed
in, and if that was not explicitly defined it would look to the
parents. I ask because I ran into a problem when working on a driver
and trying to include an .dtsi that contained a node with different
values for #address-cells and #size-cells; I could never get the
correct values returned, I only got the parents'. So my questions are
1) If the methods are not meant to return the values for
#address-cells and #size-cells should it be named something like
of_n_parent_{addr,size}_cells?
2) If they are meant to return the values for the current node could
there be a check that looks something like this?:
int of_n_addr_cells(struct device_node *np)
{
u32 cells;
if (!of_property_read_u32(np, "#address-cells", &cells))
return cells;
do {
if (np->parent)
np = np->parent;
if (!of_property_read_u32(np, "#address-cells", &cells))
return cells;
} while (np->parent);
/* No #address-cells property for the root node */
return OF_ROOT_NODE_ADDR_CELLS_DEFAULT;
}
I realize I could be missing something and that this isn't an
important change, but I just thought I'd ask. Thanks so much!
Ray
next reply other threads:[~2018-06-29 13:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 13:45 Ray Clinton [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-28 16:16 of_n_{addr,size}_cells(struct device_node *np) - Allow for returning value of node passed in Ray Clinton
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=CAPMnawsaPg-KogsyfeMEdr7ykyux9HDBy8s7jfn1KOZAdeVnCA@mail.gmail.com \
--to=mr.ray.clinton@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).