* Suman Anna [150213 08:17]:
> Ohad,
>
> On 02/12/2015 11:20 PM, Ohad Ben-Cohen wrote:
> > On Thu, Feb 12, 2015 at 10:54 PM, Suman Anna wrote:
> >> My original motivation was that it would only need to be added on
> >> firmwares requiring support for loading into internal memories,
> >> otherwis
Ohad,
On 02/12/2015 11:20 PM, Ohad Ben-Cohen wrote:
> On Thu, Feb 12, 2015 at 10:54 PM, Suman Anna wrote:
>> My original motivation was that it would only need to be added on
>> firmwares requiring support for loading into internal memories,
>> otherwise, these are something left to be managed by
On Thu, Feb 12, 2015 at 10:54 PM, Suman Anna wrote:
> My original motivation was that it would only need to be added on
> firmwares requiring support for loading into internal memories,
> otherwise, these are something left to be managed by the software
> running on the remote processor completely
Hi Ohad,
On 02/12/2015 03:09 AM, Ohad Ben-Cohen wrote:
> On Wed, Feb 11, 2015 at 10:57 PM, Tony Lindgren wrote:
+static int rproc_handle_intmem(struct rproc *rproc, struct fw_rsc_intmem
*rsc,
+ int offset, int avail)
+{
>>> ...
+ va = (
On Wed, Feb 11, 2015 at 10:57 PM, Tony Lindgren wrote:
>> > +static int rproc_handle_intmem(struct rproc *rproc, struct fw_rsc_intmem
>> > *rsc,
>> > + int offset, int avail)
>> > +{
>> ...
>> > + va = (__force void *)ioremap_nocache(rsc->pa, rsc->len);
>>
>> Ba
On 02/11/2015 06:18 PM, Tony Lindgren wrote:
> * Suman Anna [150211 16:05]:
>> On 02/11/2015 04:48 PM, Tony Lindgren wrote:
>>> * Suman Anna [150211 14:32]:
On 02/11/2015 02:57 PM, Tony Lindgren wrote:
> * Ohad Ben-Cohen [150210 02:14]:
>> Hi Suman,
>>
>> On Fri, Jan 9, 2015
* Suman Anna [150211 16:05]:
> On 02/11/2015 04:48 PM, Tony Lindgren wrote:
> > * Suman Anna [150211 14:32]:
> >> On 02/11/2015 02:57 PM, Tony Lindgren wrote:
> >>> * Ohad Ben-Cohen [150210 02:14]:
> Hi Suman,
>
> On Fri, Jan 9, 2015 at 11:21 PM, Suman Anna wrote:
> > A remot
On 02/11/2015 04:48 PM, Tony Lindgren wrote:
> * Suman Anna [150211 14:32]:
>> On 02/11/2015 02:57 PM, Tony Lindgren wrote:
>>> * Ohad Ben-Cohen [150210 02:14]:
Hi Suman,
On Fri, Jan 9, 2015 at 11:21 PM, Suman Anna wrote:
> A remote processor may need to load certain firmware
* Suman Anna [150211 14:32]:
> On 02/11/2015 02:57 PM, Tony Lindgren wrote:
> > * Ohad Ben-Cohen [150210 02:14]:
> >> Hi Suman,
> >>
> >> On Fri, Jan 9, 2015 at 11:21 PM, Suman Anna wrote:
> >>> A remote processor may need to load certain firmware sections into
> >>> internal memories (eg: RAM a
* Ohad Ben-Cohen [150210 02:14]:
> Hi Suman,
>
> On Fri, Jan 9, 2015 at 11:21 PM, Suman Anna wrote:
> > A remote processor may need to load certain firmware sections into
> > internal memories (eg: RAM at L1 or L2 levels) for performance or
> > other reasons. Introduce a new resource type (RSC_I
On 02/11/2015 02:57 PM, Tony Lindgren wrote:
> * Ohad Ben-Cohen [150210 02:14]:
>> Hi Suman,
>>
>> On Fri, Jan 9, 2015 at 11:21 PM, Suman Anna wrote:
>>> A remote processor may need to load certain firmware sections into
>>> internal memories (eg: RAM at L1 or L2 levels) for performance or
>>> ot
Hi Suman,
On Fri, Jan 9, 2015 at 11:21 PM, Suman Anna wrote:
> A remote processor may need to load certain firmware sections into
> internal memories (eg: RAM at L1 or L2 levels) for performance or
> other reasons. Introduce a new resource type (RSC_INTMEM) and add
> an associated handler functio
A remote processor may need to load certain firmware sections into
internal memories (eg: RAM at L1 or L2 levels) for performance or
other reasons. Introduce a new resource type (RSC_INTMEM) and add
an associated handler function to handle such memories. The handler
creates a kernel mapping for the
13 matches
Mail list logo
