devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Faiz Abbas <faiz_abbas@ti.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	netdev@vger.kernel.org, linux-can@vger.kernel.org,
	wg@grandegger.com, mkl@pengutronix.de, mark.rutland@arm.com,
	kishon@ti.com
Subject: Re: [PATCH 4/6] dt-bindings: can: m_can: Document transceiver implementation as a phy
Date: Mon, 12 Nov 2018 11:04:33 -0600	[thread overview]
Message-ID: <5bea0ea0.1c69fb81.31ed4.2cdf@mx.google.com> (raw)
In-Reply-To: <20181102192616.28291-5-faiz_abbas@ti.com>

On Sat, Nov 03, 2018 at 12:56:14AM +0530, Faiz Abbas wrote:
> Some transceivers need a configuration step (for example, pulling
> a standby line low) for them to start sending messages. Instead of a
> parent child relationship, the transceiver can be implemented as a
> phy with the configuration done in the phy driver. The bitrate
> limitations can then be obtained by the driver using said phy
> node.
> 
> Document the above implementation.
> 
> Signed-off-by: Faiz Abbas <faiz_abbas@ti.com>
> ---
>  .../devicetree/bindings/net/can/m_can.txt     | 24 ++++++++++++-------
>  1 file changed, 16 insertions(+), 8 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/net/can/m_can.txt b/Documentation/devicetree/bindings/net/can/m_can.txt
> index ed614383af9c..c11548e74278 100644
> --- a/Documentation/devicetree/bindings/net/can/m_can.txt
> +++ b/Documentation/devicetree/bindings/net/can/m_can.txt
> @@ -42,12 +42,14 @@ Required properties:
>  
>  			  Please refer to 2.4.1 Message RAM Configuration in
>  			  Bosch M_CAN user manual for details.
> +Optional properties:
> +- phy-names		: must be "can_transceiver". The transceiver
> +			  typically limits the maximum bitrate of the
> +			  system. The phy node is used to discover this
> +			  limitation.

A name with a single phy is pointless.

> +- phys			: phandle to the transceiver implemented as a phy
> +			  node.
>  
> -Optional Subnode:
> -- can-transceiver	: Can-transceiver subnode describing maximum speed
> -			  that can be used for CAN/CAN-FD modes. See
> -			  Documentation/devicetree/bindings/net/can/can-transceiver.txt
> -			  for details.

You can't just remove this and break existing users.

>  Example:
>  SoC dtsi:
>  m_can1: can@20e8000 {
> @@ -64,12 +66,18 @@ m_can1: can@20e8000 {
>  };
>  
>  Board dts:
> +
>  &m_can1 {
>  	pinctrl-names = "default";
>  	pinctrl-0 = <&pinctrl_m_can1>;
>  	status = "enabled";
> +	phy-names = "can_transceiver";
> +	phys = <&transceiver1>;
> +};
>  
> -	can-transceiver {
> -		max-bitrate = <5000000>;
> -	};
> +transceiver1: can-transceiver {
> +	compatible = "simple-phy";
> +	max-bitrate = <5000000>;
> +	pwr-supply = <&transceiver1_fixed>;
> +	#phy-cells = <0>;
>  };
> -- 
> 2.18.0
> 

  reply	other threads:[~2018-11-12 17:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-02 19:26 [PATCH 0/6] Add Support for MCAN transceivers in AM65x-evm Faiz Abbas
2018-11-02 19:26 ` [PATCH 1/6] phy: Add max_bitrate attribute & phy_get_max_bitrate() Faiz Abbas
2018-11-03  9:36   ` Marc Kleine-Budde
2018-11-05  6:27     ` Faiz Abbas
2018-11-05  9:37       ` Marc Kleine-Budde
2018-11-05 11:14         ` Faiz Abbas
2018-11-05 11:47           ` Marc Kleine-Budde
2018-11-05 13:22             ` Faiz Abbas
2018-11-02 19:26 ` [PATCH 2/6] dt-bindings: phy: phy-of-simple: Document new binding Faiz Abbas
2018-11-06 20:55   ` Rob Herring
2018-11-02 19:26 ` [PATCH 3/6] phy: phy-of-simple: Add support for simple generic phy driver Faiz Abbas
2018-11-03  5:04   ` kbuild test robot
2018-11-02 19:26 ` [PATCH 4/6] dt-bindings: can: m_can: Document transceiver implementation as a phy Faiz Abbas
2018-11-12 17:04   ` Rob Herring [this message]
2018-11-02 19:26 ` [PATCH 5/6] dt-bindings: can: can-transceiver: Remove legacy binding documentation Faiz Abbas
2018-11-03 20:12   ` Sergei Shtylyov
2018-11-12 17:05   ` Rob Herring
2018-11-02 19:26 ` [PATCH 6/6] can: m_can: Add support for transceiver as phy Faiz Abbas

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=5bea0ea0.1c69fb81.31ed4.2cdf@mx.google.com \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=faiz_abbas@ti.com \
    --cc=kishon@ti.com \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --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).