From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Franklin S Cooper Jr <fcooper@ti.com>,
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,
socketcan@hartkopp.net
Subject: Re: [PATCH v3 3/4] dt-bindings: can: m_can: Include reference to new fixed transceiver binding
Date: Thu, 3 Aug 2017 12:20:20 +0300 [thread overview]
Message-ID: <53a5346e-9c04-738e-432c-16cdcc4c6e60@cogentembedded.com> (raw)
In-Reply-To: <20170803005150.9286-4-fcooper@ti.com>
On 8/3/2017 3:51 AM, 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@ti.com>
> ---
> Documentation/devicetree/bindings/net/can/m_can.txt | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/can/m_can.txt b/Documentation/devicetree/bindings/net/can/m_can.txt
> index 9e33177..0b62f47 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
Subnode is not a property.
> + that can be used for CAN/CAN-FD modes. See
> + Documentation/devicetree/bindings/net/can/fixed-transceiver.txt
> + for details.
> Example:
> SoC dtsi:
> m_can1: can@020e8000 {
> @@ -64,4 +69,8 @@ Board dts:
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_m_can1>;
> status = "enabled";
> +
> + fixed-transceiver@0 {
Same comments here as in previous patch.
[...]
MBR, Sergei
next prev parent reply other threads:[~2017-08-03 9:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 0:51 [PATCH v3 0/4] can: Support transceiver based bit rate limit Franklin S Cooper Jr
2017-08-03 0:51 ` [PATCH v3 1/4] can: dev: Add support for limiting configured bitrate Franklin S Cooper Jr
2017-08-03 0:51 ` [PATCH v3 2/4] dt-bindings: can: fixed-transceiver: Add new CAN fixed transceiver bindings Franklin S Cooper Jr
2017-08-03 9:18 ` Sergei Shtylyov
2017-08-03 9:48 ` Franklin S Cooper Jr
2017-08-03 12:22 ` Sergei Shtylyov
2017-08-03 15:38 ` Franklin S Cooper Jr
2017-08-10 1:00 ` Franklin S Cooper Jr
2017-08-03 0:51 ` [PATCH v3 3/4] dt-bindings: can: m_can: Include reference to new fixed transceiver binding Franklin S Cooper Jr
2017-08-03 9:20 ` Sergei Shtylyov [this message]
2017-08-03 9:54 ` Franklin S Cooper Jr
2017-08-03 0:51 ` [PATCH v3 4/4] can: m_can: Add call to of_can_transceiver_fixed Franklin S Cooper Jr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53a5346e-9c04-738e-432c-16cdcc4c6e60@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=andrew@lunn.ch \
--cc=dev.kurt@vandijck-laurijssen.be \
--cc=devicetree@vger.kernel.org \
--cc=fcooper@ti.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=quentin.schulz@free-electrons.com \
--cc=robh+dt@kernel.org \
--cc=socketcan@hartkopp.net \
--cc=wg@grandegger.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).