From: Joe Perches <joe@perches.com>
To: Rob Herring <robh@kernel.org>
Cc: Frank Rowand <frowand.list@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] of: Custom printk format specifier for device node
Date: Thu, 15 Jun 2017 14:50:05 -0700 [thread overview]
Message-ID: <1497563405.14396.17.camel@perches.com> (raw)
In-Reply-To: <20170615212616.2uakwphhphkdds4g@rob-hp-laptop>
On Thu, 2017-06-15 at 16:26 -0500, Rob Herring wrote:
> On Wed, Jun 14, 2017 at 01:56:48PM -0700, Joe Perches wrote:
> > On Wed, 2017-06-14 at 15:30 -0500, Rob Herring wrote:
> > > From: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
[]
> > > diff --git a/lib/vsprintf.c b/lib/vsprintf.c
> > > []
> > > @@ -1470,6 +1471,123 @@ char *flags_string(char *buf, char *end, void *flags_ptr, const char *fmt)
> > > return format_flags(buf, end, flags, names);
> > > }
> > >
> > > +static noinline_for_stack
> > > +char *device_node_gen_full_name(const struct device_node *np, char *buf, char *end)
> > > +{
> > > + int len, ret;
> > > +
> > > + if (!np || !np->parent)
> > > + return buf;
> > > +
> > > + buf = device_node_gen_full_name(np->parent, buf, end);
> >
> > This is recursive. How many levels of parents could there be?
> > Perhaps there should be a recursion limit.
>
> Okay, unlike unflattening code, we can easily calculate the depth and
> then allocate an array on the stack. So this is what I've ended up
> with:
>
> static int device_node_calc_depth(const struct device_node *np)
> {
> int d;
>
> for (d = 0; np; d++)
> np = np->parent;
>
> return d;
> }
>
> static noinline_for_stack
> char *device_node_gen_full_name(const struct device_node *np, char *buf, char *end)
> {
> int i;
> int depth = device_node_calc_depth(np);
> const struct device_node *nodes[depth];
> const struct printf_spec strspec = {
> .field_width = -1,
> .precision = -1,
> };
static const struct printf_spec strspec = { etc...
and please move strspec above *nodes
>
> if (!depth)
> return buf;
> /* special case for root node */
> if (depth == 1)
> return string(buf, end, "/", strspec);
>
> depth--;
> for (i = depth - 1; i >= 0; i--) {
> nodes[i] = np;
> np = np->parent;
> }
> for (i = 0; i < depth; i++) {
> buf = string(buf, end, "/", strspec);
> buf = string(buf, end, kbasename(nodes[i]->full_name), strspec);
> }
> return buf;
> }
next prev parent reply other threads:[~2017-06-15 21:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 20:30 [PATCH 0/4] DT printf format specifiers Rob Herring
2017-06-14 20:30 ` [PATCH 1/4] of: use kbasename instead of open coding Rob Herring
2017-06-17 17:30 ` Andy Shevchenko
2017-06-14 20:30 ` [PATCH 2/4] of: find_node_by_full_name rewrite to compare each level Rob Herring
2017-06-14 20:30 ` [PATCH 3/4] of: Custom printk format specifier for device node Rob Herring
2017-06-14 20:56 ` Joe Perches
2017-06-15 12:30 ` Rob Herring
2017-06-15 16:51 ` Joe Perches
2017-06-15 21:26 ` Rob Herring
2017-06-15 21:50 ` Joe Perches [this message]
2017-06-22 20:44 ` [PATCH v2] vsprintf: Add %p extension "%pOF" for device tree Rob Herring
2017-06-22 22:44 ` Randy Dunlap
2017-06-23 14:08 ` Rob Herring
2017-06-23 3:01 ` Joe Perches
2017-06-23 14:13 ` Rob Herring
2017-06-23 17:30 ` [PATCH v3] " Rob Herring
2017-06-23 17:38 ` Joe Perches
2017-06-14 20:30 ` [PATCH 4/4] of: Convert to using %pOF instead of full_name Rob Herring
2017-06-14 20:58 ` Joe Perches
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=1497563405.14396.17.camel@perches.com \
--to=joe@perches.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh@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
Powered by JetHome