Re: [PATCH v2 1/4] can: dev: Consolidate and unify state change handling.

[Andri Yngvason <andri.yngvason@marel.com>]

On mán 20.okt 2014 19:45, Wolfgang Grandegger wrote:
> Hi Andri,
>
> sorry for the long delay...
That's all right. I've been quite busy myself.
>
> On 09/26/2014 08:25 PM, Andri Yngvason wrote:
>> The handling of can error states is different between platforms.
>> This is an attempt to correct that problem.
>>
>> I've moved this handling into a generic function for changing the
>> error state. This ensures that error state changes are handled
>> the same way everywhere (where this function is used).
>>
>> What's changed from the last version of this patch-set is that
>> can_change_state() now relies on the individual states of the rx/tx
>> counters rather than their individual count values.
> To see if the state changes occur as expected could you please record
> error message traces with candump for the following two scenarios:
>
> 1. send messages with cangen
>    disconnect the cable
>    reconnect the cable after a while until the error active state is
>    reached.
I tried this the other day with flexcan. If there is nothing else
happening on the bus, the error state will not go back down, regardless
of whether the patches are applied or not. However, this does work if
another device is also sending on the bus.

Sadly, I did not save the logs.
>
> 2. set restart-ms=100
>    send messages with cangen
>    provoke a bus-off short-circuiting CAN low and high
>    remove the short-circuit
That actually worked as expected. It's supposed to restart the bus, right?
>
> Start with the SJA100 first.
>
I'll try to find some time for these experiments.

Thanks,
Andri