[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171214003427.GD17344@builder>
Date: Wed, 13 Dec 2017 16:34:27 -0800
From: Bjorn Andersson <bjorn.andersson@...aro.org>
To: Loic Pallardy <loic.pallardy@...com>
Cc: ohad@...ery.com, linux-remoteproc@...r.kernel.org,
linux-kernel@...r.kernel.org, arnaud.pouliquen@...com,
benjamin.gaignard@...aro.org
Subject: Re: [PATCH v2 02/16] remoteproc: add release ops in rproc_mem_entry
struct
On Thu 30 Nov 08:46 PST 2017, Loic Pallardy wrote:
> +static int rproc_release_carveout(struct rproc *rproc, struct rproc_mem_entry *mem)
> +{
> + struct device *dev = &rproc->dev;
> +
> + /* clean up carveout allocations */
> + dma_free_coherent(dev->parent, mem->len, mem->va, mem->dma);
> + list_del(&mem->node);
The core is responsible for putting the node on a list, so let the
cleanup take if off the list.
> + kfree(mem);
> + return 0;
> +}
> +
[..]
> @@ -319,12 +322,11 @@ struct rproc_mem_entry {
> dma_addr_t dma;
> int len;
> u32 da;
> + int (*release)(struct rproc *rproc, struct rproc_mem_entry *mem);
The placement here seems random, please move it last in the struct.
> void *priv;
> struct list_head node;
> };
>
Regards,
Bjorn
Powered by blists - more mailing lists