[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2BFFDAA0A0DE4820876E5549867938EC@subhasishg>
Date: Tue, 10 May 2011 17:51:12 +0530
From: "Subhasish Ghosh" <subhasish@...tralsolutions.com>
To: "Alan Cox" <alan@...rguk.ukuu.org.uk>
Cc: "Wolfgang Grandegger" <wg@...ndegger.com>,
"Arnd Bergmann" <arnd@...db.de>,
<linux-arm-kernel@...ts.infradead.org>,
"Marc Kleine-Budde" <mkl@...gutronix.de>,
<sachi@...tralsolutions.com>,
<davinci-linux-open-source@...ux.davincidsp.com>,
<Netdev@...r.kernel.org>, <nsekhar@...com>,
"open list" <linux-kernel@...r.kernel.org>,
"CAN NETWORK DRIVERS" <socketcan-core@...ts.berlios.de>,
<m-watkins@...com>
Subject: Re: [PATCH v4 1/1] can: add pruss CAN driver.
>> Yes, In case if we allow the ALL implementation, it hogs the CPU.
>> In that case we do not need the PRU. The whole purpose of the PRU
>> is to offload the processor for any such implementations.
>
> So the kernel presumably needs to switch between using the PRU and native
> according to the number of ids being requested at the time ?
All the IDs are programmed into the PRU data RAM.
The Kernel receives interrupts based upon these IDs.
I could not clearly follow "PRU and native", could you please elaborate.
> That would be roughly what we do with other things (eg IP multicast) so
> that apps don't need to know all the innards
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists