From: Frank Rowand <frowand.list@gmail.com>
To: valdis.kletnieks@vt.edu
Cc: Rob Herring <robh+dt@kernel.org>,
pantelis.antoniou@konsulko.com,
Pantelis Antoniou <panto@antoniou-consulting.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
geert@linux-m68k.org, Alan Tull <atull@kernel.org>
Subject: Re: [PATCH v2] of: overlay: user space synchronization
Date: Mon, 15 Oct 2018 19:47:16 -0700 [thread overview]
Message-ID: <294737e8-f94e-5d53-acaf-ecb9a4ef42af@gmail.com> (raw)
In-Reply-To: <5408.1539650158@turing-police.cc.vt.edu>
On 10/15/18 17:35, valdis.kletnieks@vt.edu wrote:
> On Mon, 15 Oct 2018 17:27:01 -0700, frowand.list@gmail.com said:
>> From: Frank Rowand <frank.rowand@sony.com>
>>
>> When an overlay is applied or removed, the live devicetree visible in
>> /proc/device-tree/, aka /sys/firmware/devicetree/base/, reflects the
>> changes. There is no method for user space to determine whether the
>> live devicetree was modified by overlay actions.
>>
>> Provide a sysfs file, /sys/firmware/devicetree/tree_version, to allow
>> user space to determine if the live devicetree has remained unchanged
>> while a series of one or more accesses of /proc/device-tree/ occur.
>>
>> The use of both dynamic devicetree modifications and overlay apply and
>> removal are not supported during the same boot cycle. Thus non-overlay
>> dynamic modifications are not reflected in the value of tree_version.
>
> Is there an easy way from userspace to detect "yes/no dynamic modifications
> have been done since boot"?
>
Unfortunately not.
I considered adding detecting dynamic modifications in another patch, making
this a two patch series, but that feature will be much more intrusive than
detecting modifications made by overlays. I may add that feature in the
future, but not anytime soon.
If you want to understand a little bit about why dynamic modifications
occur, please see my reply to Geert in the thread about version 1 of
this patch.
next prev parent reply other threads:[~2018-10-16 2:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 0:27 [PATCH v2] of: overlay: user space synchronization frowand.list
2018-10-16 0:35 ` valdis.kletnieks
2018-10-16 2:47 ` Frank Rowand [this message]
2018-10-16 20:04 ` Alan Tull
2018-10-16 21:08 ` Frank Rowand
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=294737e8-f94e-5d53-acaf-ecb9a4ef42af@gmail.com \
--to=frowand.list@gmail.com \
--cc=atull@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=panto@antoniou-consulting.com \
--cc=robh+dt@kernel.org \
--cc=valdis.kletnieks@vt.edu \
/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).