devicetree-compiler.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Gnau <andreas.gnau@iopsys.eu>
To: Ayush Singh <ayush@beagleboard.org>,
	David Gibson <david@gibson.dropbear.id.au>,
	d-gole@ti.com, lorforlinux@beagleboard.org,
	jkridner@beagleboard.org, robertcnelson@beagleboard.org,
	Andrew Davis <afd@ti.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Simon Glass <sjg@chromium.org>
Cc: devicetree-compiler@vger.kernel.org
Subject: Re: [PATCH v2 3/4] dtc: Add /./
Date: Tue, 11 Mar 2025 16:49:37 +0100	[thread overview]
Message-ID: <b43777dc-6c24-48e5-9830-143e468bc0e3@iopsys.eu> (raw)
In-Reply-To: <20250311-previous-value-v2-3-e4a8611e956f@beagleboard.org>

On 2025-03-11 16:35, Ayush Singh wrote:
 > Allow constructing new values for a property using old property values.
 > Can be used to append, pre-append, duplicate, etc.
 >
 > In practice, it looks as follows:
 >
 > dts-v1/;
 >
 > / {
 > 	str-prop = "0";
 > 	int-prop = <0>;
 > };
 >
 > / {
 > 	str-prop = /./, "1", /./;
 > 	int-prop = /./, <1>, /./;
 > };
 >
 > dts to source output with -T -T also works as expected:
 >
 > /dts-v1/;
 >
 > / { /* base.dts:3:3-5:3, base.dts:7:3-9:3 */
 >          int-prop = <0x00 0x01>, <0x02 0x03>, <0x00 0x01>; /* 
base.dts:4:9-4:26, base.dts:8:9-8:36 */
 > }; /* base.dts:3:3-5:3, base.dts:7:3-9:3 */

I think it will be a bit easier to understand if the two examples 
correspond to another, i.e. to have both int-prop and str-prop with the 
matching value from the first example in this example.

  reply	other threads:[~2025-03-11 15:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11 15:35 [PATCH v2 0/4] Add capability to create property from old property Ayush Singh
2025-03-11 15:35 ` [PATCH v2 1/4] Add alloc_marker Ayush Singh
2025-05-28  5:13   ` David Gibson
2025-03-11 15:35 ` [PATCH v2 2/4] srcpos: Define srcpos_free Ayush Singh
2025-05-28  5:16   ` David Gibson
2025-03-11 15:35 ` [PATCH v2 3/4] dtc: Add /./ Ayush Singh
2025-03-11 15:49   ` Andreas Gnau [this message]
2025-06-02  8:20   ` David Gibson
2025-03-11 15:35 ` [PATCH v2 4/4] tests: Add test for /./ Ayush Singh

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=b43777dc-6c24-48e5-9830-143e468bc0e3@iopsys.eu \
    --to=andreas.gnau@iopsys.eu \
    --cc=afd@ti.com \
    --cc=ayush@beagleboard.org \
    --cc=d-gole@ti.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=devicetree-compiler@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=jkridner@beagleboard.org \
    --cc=lorforlinux@beagleboard.org \
    --cc=robertcnelson@beagleboard.org \
    --cc=sjg@chromium.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).