Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964987AbdGTJqC (ORCPT ); Thu, 20 Jul 2017 05:46:02 -0400 Received: from mail-lf0-f46.google.com ([209.85.215.46]:37846 "EHLO mail-lf0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934055AbdGTJp7 (ORCPT ); Thu, 20 Jul 2017 05:45:59 -0400 Subject: Re: [PATCH 2/4] can: fixed-transceiver: Add documentation for CAN fixed transceiver bindings To: Franklin S Cooper Jr , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, netdev@vger.kernel.org, linux-can@vger.kernel.org, wg@grandegger.com, mkl@pengutronix.de, robh+dt@kernel.org, quentin.schulz@free-electrons.com, dev.kurt@vandijck-laurijssen.be, andrew@lunn.ch References: <20170719233654.25908-1-fcooper@ti.com> <20170719233654.25908-3-fcooper@ti.com> From: Sergei Shtylyov Message-ID: Date: Thu, 20 Jul 2017 12:45:56 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20170719233654.25908-3-fcooper@ti.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1624 Lines: 47 Hello! On 7/20/2017 2:36 AM, Franklin S Cooper Jr wrote: > Add documentation to describe usage of the new fixed transceiver binding. > This new binding is applicable for any CAN device therefore it exist as Exists. > its own document. > > Signed-off-by: Franklin S Cooper Jr > --- > .../bindings/net/can/fixed-transceiver.txt | 31 ++++++++++++++++++++++ > 1 file changed, 31 insertions(+) > create mode 100644 Documentation/devicetree/bindings/net/can/fixed-transceiver.txt > > diff --git a/Documentation/devicetree/bindings/net/can/fixed-transceiver.txt b/Documentation/devicetree/bindings/net/can/fixed-transceiver.txt > new file mode 100644 > index 0000000..7c093c3 > --- /dev/null > +++ b/Documentation/devicetree/bindings/net/can/fixed-transceiver.txt > @@ -0,0 +1,31 @@ > +Fixed transceiver Device Tree binding > +------------------------------ > + > +CAN transceiver typically limits the max speed in standard CAN and CAN FD > +modes. Typically these limitations are static and the transceivers themselves > +provide no way to detect this limitation at runtime. For this situation, > +the "fixed-transceiver" node can be used. > + > +Properties: > + > +Optional: > + max-arbitration-speed: a positive value non 0 value that determines the max Too many values. :-) > + speed CAN can run in non CAN-FD mode or during the > + arbitration phase in CAN-FD mode. > + > + max-data-speed: a positive value that determines the max data rate > + that can be used in CAN-FD mode. A value of 0 > + implies CAN-FD is not supported by the transceiver. [...] MBR, Sergei