devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Ricardo Ribalda Delgado
	<ricardo.ribalda-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: HOWTO Undo/Revert of_platform_populate?
Date: Mon, 15 Apr 2013 14:40:09 +0100	[thread overview]
Message-ID: <20130415134009.0A70E3E0AA8@localhost> (raw)
In-Reply-To: <51392BD9.4010209-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On Thu, 07 Mar 2013 18:07:53 -0600, Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> On 03/07/2013 04:32 AM, Ricardo Ribalda Delgado wrote:
> > Hi
> > 
> > I have an FPGA attached to the pci bus. The FPGA has an internal bus
> > with multiple cores that are already supported in the kernel.
> > 
> > I have made a driver that populates those cores using a user provided
> > device tree. I use the function of_platform_populate for that.
> > 
> > All this is working fine, but now I need a method to undo what
> > of_platform_populate does when the fpga is reprogrammed.
> > 
> > I haven't found any function that does this in the api.
> > 
> > Before implementing my own I would like to know if am I missing something?
> 
> It's not possible in the current kernel. You need DT overlay support
> that was posted recently.

In the mean time you can merely recurse all the children of the parent
struct device, unregister them from the device model, and release them.

g.

      parent reply	other threads:[~2013-04-15 13:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07 10:32 HOWTO Undo/Revert of_platform_populate? Ricardo Ribalda Delgado
2013-03-08  0:07 ` Rob Herring
     [not found]   ` <51392BD9.4010209-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-04-15 13:40     ` Grant Likely [this message]

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=20130415134009.0A70E3E0AA8@localhost \
    --to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ricardo.ribalda-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).