[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5dadca68-f8ae-e708-5a5f-5d2a8876cf40@ti.com>
Date: Wed, 3 Jan 2018 17:51:40 +0530
From: Faiz Abbas <faiz_abbas@...com>
To: Marc Kleine-Budde <mkl@...gutronix.de>, <wg@...ndegger.com>,
<robh+dt@...nel.org>, <mark.rutland@....com>
CC: <linux-can@...r.kernel.org>, <netdev@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<nsekhar@...com>, <fcooper@...com>, <robh@...nel.org>,
<Wenyou.Yang@...rochip.com>, <sergei.shtylyov@...entembedded.com>
Subject: Re: [PATCH v6 1/6] can: dev: Add support for limiting configured
bitrate
Hi,
On Tuesday 02 January 2018 09:45 PM, Marc Kleine-Budde wrote:
> On 12/22/2017 02:31 PM, Faiz Abbas wrote:
>> From: Franklin S Cooper Jr <fcooper@...com>
>>
>> Various CAN or CAN-FD IP may be able to run at a faster rate than
>> what the transceiver the CAN node is connected to. This can lead to
>> unexpected errors. However, CAN transceivers typically have fixed
>> limitations and provide no means to discover these limitations at
>> runtime. Therefore, add support for a can-transceiver node that
>> can be reused by other CAN peripheral drivers to determine for both
>> CAN and CAN-FD what the max bitrate that can be used. If the user
>> tries to configure CAN to pass these maximum bitrates it will throw
>> an error.
>
> Please add support to read the maximum bitrate via netlink. Have a look
> at 12a6075cabc0 ("can: dev: add CAN interface termination API"). I think
> you need to extend the following functions: can_get_size() and
> can_fill_info().
Will add in the next version.
Thanks,
Faiz
>
> Marc
>
Powered by blists - more mailing lists