[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK=WgbaSD9tGVKhUkbL3JjtW9GuAR_fbWHG6rx1m_v9TDW0Osw@mail.gmail.com>
Date: Sat, 9 May 2015 10:54:18 +0300
From: Ohad Ben-Cohen <ohad@...ery.com>
To: Dave Gerlach <d-gerlach@...com>
Cc: linux-arm <linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Suman Anna <s-anna@...com>, Kevin Hilman <khilman@...aro.org>,
Tony Lindgren <tony@...mide.com>
Subject: Re: [PATCH v3 2/4] remoteproc: add a rproc ops for performing address translation
Hi Dave,
On Wed, Apr 1, 2015 at 10:37 PM, Dave Gerlach <d-gerlach@...com> wrote:
> From: Suman Anna <s-anna@...com>
>
> The rproc_da_to_va API is currently used to perform any device to
> kernel address translations to meet the different needs of the remoteproc
> core/drivers (eg: loading). The functionality is achieved within the
> remoteproc core, and is limited only for carveouts allocated within the
> core.
>
> A new rproc ops, da_to_va, is added to provide flexibility to platform
> implementations to perform the address translation themselves when the
> above conditions cannot be met by the implementations. The rproc_da_to_va()
> API is extended to invoke this ops if present, and fallback to regular
> processing if the platform implementation cannot provide the translation.
> This will allow any remoteproc implementations to translate addresses for
> dedicated memories like internal memories.
Can you please provide specific examples where this is needed and how
it is going to be used?
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