From: Ayush Singh <ayush@beagleboard.org>
To: CVS <cvs268@gmail.com>
Cc: Simon Glass <sjg@chromium.org>,
d-gole@ti.com, lorforlinux@beagleboard.org,
jkridner@beagleboard.org, robertcnelson@beagleboard.org,
nenad.marinkovic@mikroe.com, Andrew Davis <afd@ti.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Robert Nelson <robertcnelson@gmail.com>,
devicetree-compiler@vger.kernel.org
Subject: Re: [PATCH v2 2/2] tests: Add test for append-property
Date: Fri, 30 Aug 2024 13:37:16 +0530 [thread overview]
Message-ID: <a9422c17-75dd-46f3-b661-668771137f50@beagleboard.org> (raw)
In-Reply-To: <CAK-9PRCWNN8x6zOw6sk+sXZSZ2Z93UOisQhg+gK17C_GqnV=vA@mail.gmail.com>
On 8/30/24 08:58, CVS wrote:
> Also, how does the existing -T / --annotate option behave with this
> proposed feature ?
> i.e. when a line in the device-tree is modified using /append-property
> what (all) would the annotation comment contain ?
>
> regards
> CVS
I was not aware of this option, so just tried using it and here are the
results:
Input file:
```
/dts-v1/;
/ {
str-prop = "0";
num-prop = <2>;
subnode{
str-prop = "0";
num-prop = <2>;
};
};
/ {
/append-property/ str-prop = "1";
/append-property/ num-prop = <1>;
subnode{
/append-property/ str-prop = "1";
/append-property/ num-prop = <1>;
};
};
```
Command:
./dtc -T -o temp.dts ../tests/append_prop.dts
Results:
```
/dts-v1/;
/ { /* append_prop.dts:3, append_prop.dts:13 */
str-prop = "0", "1"; /* append_prop.dts:14 */
num-prop = <0x02>, <0x01>; /* append_prop.dts:15 */
subnode { /* append_prop.dts:7, append_prop.dts:17 */
str-prop = "0", "1"; /* append_prop.dts:18 */
num-prop = <0x02>, <0x01>; /* append_prop.dts:19 */
}; /* append_prop.dts:10, append_prop.dts:20 */
}; /* append_prop.dts:11, append_prop.dts:21 */
```
For more detaild information using -T -T:
```
/dts-v1/;
/ { /* ../tests/append_prop.dts:3:3-11:3,
../tests/append_prop.dts:13:3-21:3 */
str-prop = "0", "1"; /* ../tests/append_prop.dts:14:2-14:35 */
num-prop = <0x02>, <0x01>; /* ../tests/append_prop.dts:15:2-15:35 */
subnode { /* ../tests/append_prop.dts:7:9-10:4,
../tests/append_prop.dts:17:9-20:4 */
str-prop = "0", "1"; /* ../tests/append_prop.dts:18:3-18:36 */
num-prop = <0x02>, <0x01>; /*
../tests/append_prop.dts:19:3-19:36 */
}; /* ../tests/append_prop.dts:7:9-10:4,
../tests/append_prop.dts:17:9-20:4 */
}; /* ../tests/append_prop.dts:3:3-11:3,
../tests/append_prop.dts:13:3-21:3 */
```
Does this look acceptable?
Ayush Singh
next prev parent reply other threads:[~2024-08-30 8:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 20:03 [PATCH v2 0/2] Add capability to append to property Ayush Singh
2024-08-29 20:03 ` [PATCH v2 1/2] dtc: Add /append-property/ Ayush Singh
2024-08-29 20:03 ` [PATCH v2 2/2] tests: Add test for append-property Ayush Singh
2024-08-30 1:06 ` Simon Glass
2024-08-30 3:28 ` CVS
2024-08-30 8:07 ` Ayush Singh [this message]
2024-08-30 8:01 ` Ayush Singh
2024-09-12 11:06 ` CVS
2024-09-17 17:23 ` Ayush Singh
2024-08-30 8:09 ` [PATCH v2 0/2] Add capability to append to property Geert Uytterhoeven
2024-08-30 15:43 ` Andrew Davis
2024-09-12 3:59 ` David Gibson
2024-10-10 6:31 ` 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=a9422c17-75dd-46f3-b661-668771137f50@beagleboard.org \
--to=ayush@beagleboard.org \
--cc=afd@ti.com \
--cc=cvs268@gmail.com \
--cc=d-gole@ti.com \
--cc=devicetree-compiler@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=jkridner@beagleboard.org \
--cc=lorforlinux@beagleboard.org \
--cc=nenad.marinkovic@mikroe.com \
--cc=robertcnelson@beagleboard.org \
--cc=robertcnelson@gmail.com \
--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).