public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
To: "Robert P. J. Day" <rpjday-L09J2beyid0N/H6P543EQg@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: still unclear on a couple DT questions from my initial post
Date: Fri, 1 Sep 2017 09:51:44 +0100	[thread overview]
Message-ID: <20170901085144.GA1933@leverpostej> (raw)
In-Reply-To: <alpine.LFD.2.21.1709010121140.20957-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>

On Fri, Sep 01, 2017 at 01:29:31AM -0400, Robert P. J. Day wrote:
>   again, more nitpicky pedantry, but from my initial post, i'm still
> unclear on a couple things.
> 
>   first, a number of powerpc .dts files contain the line:
> 
>     dcr-parent = <&{/cpus/cpu@0}>;
> 
> and it's not clear to me why there are curly braces there. that is the
> only example of that, but i see no mention of that in the spec. is it
> meaningful? or are they superfluous?

This syntax allows us to refer to a node by path, even if it doesn't
have an existing label. The &foo syntax only allows us to refer to an
existing label called foo.

>   also, the spec states that status could be set to "okay", but a pile
> of .dts files in the current kernel have the shorter form:
> 
>   status = "ok";
> 
> and the current kernel code in drivers/of explicitly accepts both
> forms. is that a formal spec property, or is the kernel code simply
> allowing people to be sloppy?

The kernel is catering for sloppiness. We should probably fix those up
in the kernel tree.

Thanks,
Mark.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-09-01  8:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-01  5:29 still unclear on a couple DT questions from my initial post Robert P. J. Day
     [not found] ` <alpine.LFD.2.21.1709010121140.20957-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2017-09-01  8:51   ` Mark Rutland [this message]
2017-09-01 17:14     ` Robert P. J. Day
     [not found]       ` <alpine.LFD.2.21.1709011314001.2699-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2017-09-01 18:21         ` Rob Herring

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=20170901085144.GA1933@leverpostej \
    --to=mark.rutland-5wv7dgnigg8@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rpjday-L09J2beyid0N/H6P543EQg@public.gmane.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