Re: Losing CAN messages with socket-CAN

[Wolfgang Grandegger <wg@grandegger.com>]

Hi Jeroen,

On 04/24/2013 11:11 AM, j.p.lammertink wrote:
> Hi Wolfgang,
> 
> I think I have a patch for the "Loosing CAN messages problem"
> See at the bottom Appendix 7 Sugested patch.
> I realize that this patch has a performance penalty, but I didn't dare
> to make more rigorous changes.
> I've put the patch on top of Patch 1, of the patches that you sugested (see
> text below)
> 
> I'm interested in all feedback.

Well, we want to get rid of the pch_can driver sooner than later.
Therefore I would appreciate if you could test and improve the c_can
driver instead.

Wolfgang.

...
> --------------------------------------------------------------------------
> Appendix 7 Suggested patch
> 
> diff --git a/drivers/net/can/pch_can.c b/drivers/net/can/pch_can.c
> index 44b9a7a..81d599f 100644
> --- a/drivers/net/can/pch_can.c
> +++ b/drivers/net/can/pch_can.c
> @@ -912,7 +912,6 @@ static netdev_tx_t pch_xmit(struct sk_buff *skb, struct net_device *ndev)
>  
>  	tx_obj_no = priv->tx_obj;
>  	if (priv->tx_obj == PCH_TX_OBJ_END) {
> -		if (ioread32(&priv->regs->treq2) & PCH_TREQ2_TX_MASK)

This means that there are pending TX messages. If there are none, there
is no need to stop the queue. I'm puzzled!

>  			netif_stop_queue(ndev);
>  
>  		priv->tx_obj = PCH_TX_OBJ_START;
> 

Hm, is this code protected by spin_lock_irqsave/spin_unlock_irqrestore?

Wolfgang.