[lkml]   [2011]   [Apr]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v4 01/11] mfd: add pruss mfd driver.
PRU's resulting in improved load sharing.
>> Signed-off-by: Subhasish Ghosh <>
> Hi Subhasish,
> This looks like great progress since the last time I looked at the
> pruss mfd driver, good work there!
> Thanks to your explanations and the documentation link, I now have
> a better understanding of what is actually going on here, but I'd
> still like to understandhow the decision is made regarding what programs
> are loaded into each PRU and how the MFD cells are set up.

> Is this a fixed setting for each board that strictly depends on how
> the external pins are connected, or is it possible to use the same
> hardware for different purposes based on the program?

SG -- The PRU pins are exposed as is on the main board,
we have separate add on daughter cards
specific to the protocol implemented on it.

> If I read your code correctly, you hardwire the usage of the two
> PRUs in the da850 board code, which makes it impossible to use
> them in different ways even if the hardware supports it. If this is
> indeed the case, using an MFD device might not be the best option
> and we should try to come up with a way to dynamically repurpose
> the PRU with some user interface.

SG -- It depends upon how the firmware is implemented. If another
firmware is downloaded on it, it will emulate another device.
Also, if a firmware emulated on it supports switching between
that too is possible. Its just a microcontroller, we can do
whatever we feel like
with it. Both the PRUs have separate instruction/data ram, so
both can be used
to implement two different devices.

 \ /
  Last update: 2011-04-27 15:39    [W:0.084 / U:0.084 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site