[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160830211532.GE24683@hector.attlocal.net>
Date: Tue, 30 Aug 2016 16:15:32 -0500
From: Andy Gross <andy.gross@...aro.org>
To: "Gupta, Puja" <pujag@...eaurora.org>
Cc: Stanimir Varbanov <stanimir.varbanov@...aro.org>,
Ohad Ben-Cohen <ohad@...ery.com>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Stephen Boyd <sboyd@...eaurora.org>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Rob Clark <robdclark@...il.com>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-remoteproc@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH 2/4] firmware: qcom: scm: add iommu scm calls for pg table
On Wed, Aug 24, 2016 at 11:35:29AM -0700, Gupta, Puja wrote:
> On 8/19/2016 8:53 AM, Stanimir Varbanov wrote:
> >Those two scm calls are used to get the size of secure iommu
> >page table and to pass physical memory address for this page
> >table. The calls are used by remoteproc venus driver to load
> >the firmware.
> Do we really need these additional scm calls for venus? why can't we just
> reuse existing __qcom_scm_pas_mem_setup() call?
Keep in mind this is with the smmu-v1 on 8916. It seems like the downstream
kernel has to do extra stuff when dealing with the older smmu. The newer
platforms handle this quasi-transparently.
Regards,
Andy
Powered by blists - more mailing lists