[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK=Wgbb1e6O574Bpicy4Y623vtiigauT22H-zk+JXGCz070i5g@mail.gmail.com>
Date: Thu, 18 Jun 2015 12:04:16 +0300
From: Ohad Ben-Cohen <ohad@...ery.com>
To: Dave Gerlach <d-gerlach@...com>
Cc: linux-arm <linux-arm-kernel@...ts.infradead.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
Suman Anna <s-anna@...com>, Tony Lindgren <tony@...mide.com>
Subject: Re: [PATCH v5 1/4] remoteproc: introduce rproc_get_by_phandle API
Hi Dave,
On Wed, Jun 17, 2015 at 9:46 PM, Dave Gerlach <d-gerlach@...com> wrote:
> Allow users of remoteproc the ability to get a handle to an rproc by
> passing a phandle supplied in the user's device tree node. This is
> useful in situations that require manual booting of the rproc.
>
> This patch uses the code removed by commit 40e575b1d0b3 ("remoteproc:
> remove the get_by_name/put API") for the ref counting but is modified
> to use a simple list and locking mechanism and has rproc_get_by_name
> replaced with an rproc_get_by_phandle API.
>
> Signed-off-by: Dave Gerlach <d-gerlach@...com>
> Signed-off-by: Suman Anna <s-anna@...com>
> ---
> v4->v5: Fixed build error from of_find_node_by_phandle when !CONFIG_OF
> based on offline discussion.
We can't rebase our for-next branch, so I've applied a
similar fix in a separate patch.
Please check our for-next branch to make sure things still work for you.
Thanks,
Ohad.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists