Thank you for the clarification. Actually, our controller is still in the implementation stage. Basically, we can configure an ID for each mailbox.
________________________________ From: Wolfgang Grandegger <w...@grandegger.com> To: Subhasish Ghosh <subhasis...@yahoo.com> Cc: socketcan-users@lists.berlios.de Sent: Tue, 27 April, 2010 12:55:57 PM Subject: Re: [Socketcan-users] Socket can h/w filter Subhasish Ghosh wrote: > Hi!, > > The CAN controller that I am using allows configuring per-mailbox IDs. CAN > being a broadcast network, this feature reduces the interrupts to the > processor. What CAN controller are you using. > From Documentation/can.txt, what I understand is that the socketcan interface > does not provide any mechanism to configure the h/w for this purpose (chapter > 6.3). Right, hardware filtering is not yet supported. > Instead, the h/w is configured to receive all identifiers and the filtering > is done on the stack (like ti_hecc.c) and to avoid hogging the processor some > interrupt mitigation techniques like NAPI is implemented. > > Isn't this a work around? Well, software filtering is used for the sake of portability. > My question is, did I miss something, is there any way to configure the h/w > for this purpose. Is it a good idea if I cook up a sysfs interface for my > driver for this. The problem is that the filtering capabilities of CAN controllers are very hardware specific and providing a generic interface is not trivial. But that's definetely something on the to-do list for Socket-CAN. Any ideas, suggestions or even patches are welcome. What are your specific requirements? Wolfgang.
_______________________________________________ Socketcan-users mailing list Socketcan-users@lists.berlios.de https://lists.berlios.de/mailman/listinfo/socketcan-users
