Re: [PATCH 0/5] can: enable multi-queue for SocketCAN devices
From: Oleksij Rempel
Date: Mon Jun 11 2018 - 00:42:06 EST
On 07.06.2018 17:14, Jonas Mark (BT-FIR/ENG1) wrote:
> Hi Andy,
>>> The functionality bases on an external peripheral chip named Companion.
>>> It offers two CAN interfaces, each has 8 prioritized transmit FIFOs as
>>> well as one receive FIFO. Besides CAN, undisclosed additional functions
>>> can be accessed through the char device.
>>> A standard SPI interface with two additional lines for flow control is
>>> used. The Companion chip is the SPI slave.
>> Can remoteproc API be utilized here?
> So far I wasn't aware of the remoteproc API. It appears to me that is
> limited to power on/off and loading firmware in an AMP scenario. Here,
> the Companion has a fixed firmware in it. It must already be running
> quickly after power-up, even before the boot loader.
yes, remoteproc is not quite suitable for this task.
> Does remoteproc also contain a communication framework?
it is using VirtIO
> Do you mean rpmsg? Here, I do not see how we could benefit from it.
using same message format instead of inventing new one will be really
(less code duplicating same functionality)
Looks like every company trying to solve the same problem over and over
again. We have point to point link between two systems. Each system has
multiple functionalities/applications so we should be able to address
this functionality. So we end to some thing with source address and
destination address. In all protocols used for inter processor/chip
communication, the difference is only the layout of 3 common fields:
source, destination and size. In many cases the ISO/OSI layer model is
badly broken and
> Can you point me to an example where rpmsg is used over SPI?
RPMsg is just transport layer, 5 or 6 wire SPI is in this case Physical
layer with flow control support. Currently i'm not sure if VirtIO with
queue support do make sense here.
Description: OpenPGP digital signature