lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 9 Aug 2017 20:02:16 -0500 From: Franklin S Cooper Jr <fcooper@...com> To: Rob Herring <robh@...nel.org> CC: <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>, <netdev@...r.kernel.org>, <linux-can@...r.kernel.org>, <wg@...ndegger.com>, <mkl@...gutronix.de>, <quentin.schulz@...e-electrons.com>, <dev.kurt@...dijck-laurijssen.be>, <andrew@...n.ch>, <sergei.shtylyov@...entembedded.com>, <socketcan@...tkopp.net> Subject: Re: [PATCH v2 3/4] can: m_can: Update documentation to mention new fixed transceiver binding Hi Rob, On 08/03/2017 12:07 PM, Rob Herring wrote: > On Mon, Jul 24, 2017 at 06:05:20PM -0500, Franklin S Cooper Jr wrote: >> Add information regarding fixed transceiver binding. This is especially >> important for MCAN since the IP allows CAN FD mode to run significantly >> faster than what most transceivers are capable of. >> >> Signed-off-by: Franklin S Cooper Jr <fcooper@...com> >> --- >> Version 2 changes: >> Drop unit address >> >> Documentation/devicetree/bindings/net/can/m_can.txt | 10 ++++++++++ >> 1 file changed, 10 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/net/can/m_can.txt b/Documentation/devicetree/bindings/net/can/m_can.txt >> index 9e33177..e4abd2c 100644 >> --- a/Documentation/devicetree/bindings/net/can/m_can.txt >> +++ b/Documentation/devicetree/bindings/net/can/m_can.txt >> @@ -43,6 +43,11 @@ Required properties: >> Please refer to 2.4.1 Message RAM Configuration in >> Bosch M_CAN user manual for details. >> >> +Optional properties: >> +- fixed-transceiver : Fixed-transceiver subnode describing maximum speed > > This is a node, not a property. Sub nodes should have their own section. Fixed in my v4 that I just sent. > >> + that can be used for CAN and/or CAN-FD modes. See >> + Documentation/devicetree/bindings/net/can/fixed-transceiver.txt >> + for details. >> Example: >> SoC dtsi: >> m_can1: can@...e8000 { >> @@ -64,4 +69,9 @@ Board dts: >> pinctrl-names = "default"; >> pinctrl-0 = <&pinctrl_m_can1>; >> status = "enabled"; >> + >> + fixed-transceiver { >> + max-arbitration-speed = <1000000>; >> + max-data-speed = <5000000>; >> + }; >> }; >> -- >> 2.10.0 >>
Powered by blists - more mailing lists