From: Alan Tull <atull@kernel.org>
To: Rob Herring <robh+dt@kernel.org>
Cc: Moritz Fischer <mdf@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-fpga@vger.kernel.org
Subject: Re: [PATCH 2/2] of: dynamic: add overlay-allowed DT property
Date: Mon, 4 Dec 2017 14:12:16 -0600 [thread overview]
Message-ID: <CANk1AXQ0KuzFucbTQ1LtF8F-XMqTw4y2xmVA-rqHcMAQH7hsnw@mail.gmail.com> (raw)
In-Reply-To: <CAL_Jsq+f4q=8rvxndbJNkp5KNMYRoKHs-zKOL1zwXfS0T2A3mA@mail.gmail.com>
On Mon, Dec 4, 2017 at 2:04 PM, Rob Herring <robh+dt@kernel.org> wrote:
> On Mon, Dec 4, 2017 at 1:13 PM, Alan Tull <atull@kernel.org> wrote:
>> Allow DT nodes to be marked as valid targets for DT
>> overlays by the added "overlay-allowed" property.
>
> Why do you need a property for this? I'm not all that keen on putting
> this policy into the DT. It can change over time in the kernel. For
> example, as we define use cases that work, then we can loosen
> restrictions in the kernel.
For FPGA regions, I don't need it. Yes, if the other patch is
accepted, I'm sure we will hear more from people who will need some
specific loosening. I was trying to anticipate that, but I don't have
a specific need.
Alan
>
> Rob
WARNING: multiple messages have this Message-ID (diff)
From: Alan Tull <atull-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Moritz Fischer <mdf-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Frank Rowand
<frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Pantelis Antoniou
<pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-fpga-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/2] of: dynamic: add overlay-allowed DT property
Date: Mon, 4 Dec 2017 14:12:16 -0600 [thread overview]
Message-ID: <CANk1AXQ0KuzFucbTQ1LtF8F-XMqTw4y2xmVA-rqHcMAQH7hsnw@mail.gmail.com> (raw)
In-Reply-To: <CAL_Jsq+f4q=8rvxndbJNkp5KNMYRoKHs-zKOL1zwXfS0T2A3mA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Mon, Dec 4, 2017 at 2:04 PM, Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:
> On Mon, Dec 4, 2017 at 1:13 PM, Alan Tull <atull-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:
>> Allow DT nodes to be marked as valid targets for DT
>> overlays by the added "overlay-allowed" property.
>
> Why do you need a property for this? I'm not all that keen on putting
> this policy into the DT. It can change over time in the kernel. For
> example, as we define use cases that work, then we can loosen
> restrictions in the kernel.
For FPGA regions, I don't need it. Yes, if the other patch is
accepted, I'm sure we will hear more from people who will need some
specific loosening. I was trying to anticipate that, but I don't have
a specific need.
Alan
>
> Rob
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-12-04 20:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 19:13 [PATCH 0/2] of: dynamic: restrict overlay by targets Alan Tull
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 [this message]
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=CANk1AXQ0KuzFucbTQ1LtF8F-XMqTw4y2xmVA-rqHcMAQH7hsnw@mail.gmail.com \
--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.