devicetree-compiler.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kyle Evans <kevans-h+KGxgPPiopAfugRpC6u6w@public.gmane.org>
To: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Overlay syntactic sugar clarification
Date: Mon, 8 Jan 2018 23:36:57 -0600	[thread overview]
Message-ID: <CACNAnaFASS-1dC4Vp7JbwEjtF0vbAxOP248AtPabPLhZ_MHVoQ@mail.gmail.com> (raw)

Hello!

I see the syntactic sugar patch was merged in late September this
year. I have some resulting questions:

1.) Are there plans to deprecate the handcrafted fragment syntax? I
find it somewhat useful for hacking things into /soc (via target-path)
for development since this node is often not labelled, so it's
probably a good idea to ask this up front. =)

2.) Is it expected and/or OK that the output/behavior of this dtc(1)
gets kind of funky when combining handcrafted fragments with these
generated fragments?

"funky" ranges from outright errors to silently merging a handcrafted
fragment into a generated fragment in a way that yields an overlay
that you're definitely not expecting. If this isn't a supported
use-case, then I suppose this is OK.

I ask because I recently implemented this syntax into our BSDL dtc,
and naturally in my work I had it generate fragments for these nodes,
merge them all into one /, and renumber any handcrafted fragments
based on their position and the "fragment delta" (highest generated
auto-fragment at that point).

The reasoning being that there's likely no good way to merge a manual
fragment with one of these auto-fragments, and with our implementation
is was almost easier to do this than it is to just discard the
handcrafted if we start out with the sugary versions.

Thanks,

Kyle Evans

             reply	other threads:[~2018-01-09  5:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09  5:36 Kyle Evans [this message]
     [not found] ` <CACNAnaFASS-1dC4Vp7JbwEjtF0vbAxOP248AtPabPLhZ_MHVoQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-09 16:50   ` Overlay syntactic sugar clarification Kyle Evans
2018-01-10  8:43   ` David Gibson

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=CACNAnaFASS-1dC4Vp7JbwEjtF0vbAxOP248AtPabPLhZ_MHVoQ@mail.gmail.com \
    --to=kevans-h+kgxgppiopafugrpc6u6w@public.gmane.org \
    --cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
    --cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@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;
as well as URLs for NNTP newsgroup(s).