From: Rob Herring <robh@kernel.org>
To: Alan Tull <atull@opensource.altera.com>
Cc: Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Frank Rowand <frowand.list@gmail.com>,
Grant Likely <grant.likely@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Moritz Fischer <moritz.fischer@ettus.com>,
Pantelis Antoniou <pantelis.antoniou@gmail.com>,
Alan Tull <delicious.quinoa@gmail.com>,
Dinh Nguyen <dinguyen@opensource.altera.com>
Subject: Re: [PATCH 1/1] of/overlay: of overlay callbacks
Date: Sun, 21 Feb 2016 20:55:17 -0600 [thread overview]
Message-ID: <20160222025517.GS15973@rob-hp-laptop> (raw)
In-Reply-To: <1455730885-1514-2-git-send-email-atull@opensource.altera.com>
On Wed, Feb 17, 2016 at 11:41:25AM -0600, Alan Tull wrote:
> Add overlay callback functionality.
>
> When DT overlays are being added, some drivers/subsystems
> will want to know about the changes before they go into the
> live tree. Similarly there is a need for post-remove
> callbacks.
>
> Each handler is registered with a of_device_id. When
> an overlay target matches a handler's id, the handler
> gets called.
>
> The following 4 cases are handled: pre-apply, post-apply,
> pre-remove, and post-remove.
So I know I suggested maybe not using notifiers, but this ends up just
looking like notifiers, so we might as well use them unless we somehow
change the flow. You would just need to add pre-apply and pre-remove
in of_attach_node and of_detach_node, right?
Rob
next prev parent reply other threads:[~2016-02-22 2:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 17:41 [PATCH 0/1] of overlay callbacks Alan Tull
2016-02-17 17:41 ` [PATCH 1/1] of/overlay: " Alan Tull
[not found] ` <1455730885-1514-2-git-send-email-atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
2016-02-18 5:13 ` Moritz Fischer
2016-02-18 15:10 ` atull
2016-02-22 2:55 ` Rob Herring [this message]
2016-02-22 15:38 ` Pantelis Antoniou
2016-02-22 15:48 ` Alan Tull
[not found] ` <6F671B0F-4F94-47F0-9CA2-04E6F905F20A-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
2016-02-22 21:40 ` atull
2016-02-24 22:36 ` atull
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=20160222025517.GS15973@rob-hp-laptop \
--to=robh@kernel.org \
--cc=atull@opensource.altera.com \
--cc=delicious.quinoa@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@opensource.altera.com \
--cc=frowand.list@gmail.com \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moritz.fischer@ettus.com \
--cc=pantelis.antoniou@gmail.com \
--cc=pantelis.antoniou@konsulko.com \
/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