From: Alan Tull <atull@kernel.org>
To: Moritz Fischer <mdf@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>
Cc: Alan Tull <atull@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fpga@vger.kernel.org
Subject: [PATCH 0/2] of: dynamic: restrict overlay by targets
Date: Mon, 4 Dec 2017 13:13:55 -0600 [thread overview]
Message-ID: <20171204191357.3211-1-atull@kernel.org> (raw)
Restrict which nodes are valid targets for a DT overlay.
Add a flag bit to struct device_node allowing nodes to be marked as
valid target for overlays.
A driver that is always intended to handle DT overlays can
enable overlays by calling a function for its DT node.
For individual nodes that need to be opened up for a specific use,
adding the property "overlay-allowed" enables overlays targeting
that node. I'll need to document the DT property, not sure where
specifically. New file bindings/overlay.txt?
This patchset differs from the RFC:
* Added a flag bit and got rid of the whitelist
* Renamed the functions that enable a node
* Added a DT property
Alan Tull (2):
of: overlay: add flag enabling overlays and enable fpga-region
overlays
of: dynamic: add overlay-allowed DT property
drivers/fpga/of-fpga-region.c | 4 ++++
drivers/of/base.c | 4 ++--
drivers/of/dynamic.c | 3 +++
drivers/of/fdt.c | 3 +++
drivers/of/of_private.h | 2 ++
drivers/of/overlay.c | 26 ++++++++++++++++++++++++++
include/linux/of.h | 19 +++++++++++++++++++
7 files changed, 59 insertions(+), 2 deletions(-)
--
2.7.4
next reply other threads:[~2017-12-04 19:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 19:13 Alan Tull [this message]
2017-12-04 19:13 ` [PATCH 1/2] of: overlay: add flag enabling overlays and enable fpga-region overlays Alan Tull
2017-12-04 19:13 ` Alan Tull
2017-12-04 19:13 ` [PATCH 2/2] of: dynamic: add overlay-allowed DT property Alan Tull
2017-12-04 19:13 ` Alan Tull
2017-12-04 20:04 ` Rob Herring
2017-12-04 20:04 ` Rob Herring
2017-12-04 20:12 ` Alan Tull
2017-12-04 20:12 ` Alan Tull
2017-12-04 19:18 ` [PATCH 0/2] of: dynamic: restrict overlay by targets Moritz Fischer
2017-12-04 19:18 ` Moritz Fischer
2017-12-04 19:20 ` Moritz Fischer
2017-12-05 1:14 ` Frank Rowand
2017-12-05 17:07 ` Alan Tull
2017-12-06 11:58 ` Frank Rowand
2017-12-06 11:58 ` 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=20171204191357.3211-1-atull@kernel.org \
--to=atull@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh+dt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.