On 06/29/2017 05:36 PM, Kurt Van Dijck wrote:
>>>>
>>>> mcan@0 {
>>>> ...
>>>> fixed-transceiver {
>>>> max-canfd-speed = <2000>
>>>> };
>>>> ...
>>>> };
>
> Since when would a transceiver support different speeds for CAN & CANFD?
When I say CAN I'm referring to CAN 2.0 specification which mentioned
speeds upto 1 Mbit/s. While CAN FD supports higher bitrates.
> No transceivers were available, but they are now.
> I see no datalink problem applying 2MBit for regular CAN with apropriate
> physical layer, and CAN does not predefine the physical layer
> (advise != define).
>
> IMHO,
> fixed-transceiver {
> max-arbitration-speed = <2000000>
> max-data-speed = <4000000>
> };
> is way better to describe the hardware.
> Regular CAN chips would not consider max-data-speed...
What is arbitration speed?
Also if I understand you correctly then I agree drivers for traditional
CAN wouldn't care about this subnode. Although it may be helpful for
max-data-speed to become max-canfd-speed or something along those lines.
Just so the property's purpose is clear.
>
> Kind regards,
> Kurt
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
