From: Jassi Brar Subject: Re: [PATCH 1/6] mailbox: Add new API mbox_channel_device() for clients Date: Fri, 3 Feb 2017 17:35:42 +0530 Message-ID: References: <1486010836-25228-1-git-send-email-anup.patel@broadcom.com> <1486010836-25228-2-git-send-email-anup.patel@broadcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: Vinod Koul , Rob Herring , Mark Rutland , Herbert Xu , "David S . Miller" , Dan Williams , Ray Jui , Scott Branden , Jon Mason , Rob Rice , BCM Kernel Feedback , dmaengine@vger.kernel.org, Devicetree List , "linux-arm-kernel@lists.infradead.org" , Linux Kernel Mailing List , linux-crypto@vger.kernel.org, linux-raid@vger.kernel.org To: Anup Patel Return-path: In-Reply-To: <1486010836-25228-2-git-send-email-anup.patel@broadcom.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org On Thu, Feb 2, 2017 at 10:17 AM, Anup Patel wrote: > The remote processor can have DMAENGINE capabilities and client > can pass data to be processed via main memory. In such cases, > the client will require DMAble memory for remote processor. > > This patch adds new API mbox_channel_device() which can be > used by clients to get struct device pointer of underlying > mailbox controller. This struct device pointer of mailbox > controller can be used by clients to allocate DMAble memory > for remote processor. > IIUC, DT already provides a way for what you need.