From: Dimitri Fedrau <dima.fedrau@gmail.com>
To: Conor Dooley <conor@kernel.org>
Cc: dimitri.fedrau@liebherr.com,
Marc Kleine-Budde <mkl@pengutronix.de>,
Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: can: fsl,flexcan: add transceiver capabilities
Date: Fri, 14 Feb 2025 06:05:40 +0100 [thread overview]
Message-ID: <20250214050540.GA3602@debian> (raw)
In-Reply-To: <20250213-scariness-enhance-56eda6901f69@spud>
Am Thu, Feb 13, 2025 at 08:07:22PM +0000 schrieb Conor Dooley:
> On Wed, Feb 12, 2025 at 08:52:04PM +0100, Dimitri Fedrau wrote:
> > Am Tue, Feb 11, 2025 at 04:38:48PM +0000 schrieb Conor Dooley:
> > > On Tue, Feb 11, 2025 at 02:12:33PM +0100, Dimitri Fedrau via B4 Relay wrote:
> > > > From: Dimitri Fedrau <dimitri.fedrau@liebherr.com>
> > > >
> > > > Currently the flexcan driver does not support adding PHYs. Add the
> > > > capability to ensure that the PHY is in operational state when the link
> > > > is set to an "up" state.
> > > >
> > > > Signed-off-by: Dimitri Fedrau <dimitri.fedrau@liebherr.com>
> > > > ---
> > > > Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml | 3 +++
> > > > 1 file changed, 3 insertions(+)
> > > >
> > > > diff --git a/Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml b/Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml
> > > > index 97dd1a7c5ed26bb7f1b2f78c326d91e2c299938a..397957569588a61111a313cf9107e29dacc9e667 100644
> > > > --- a/Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml
> > > > +++ b/Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml
> > > > @@ -70,6 +70,9 @@ properties:
> > > > xceiver-supply:
> > > > description: Regulator that powers the CAN transceiver.
> > > >
> > > > + phys:
> > > > + maxItems: 1
> > >
> > > Can all devices in this binding support external phy? Are all devices
> > > limited to a single external phy?
> > >
> > As far as I know, these devices are controllers without integrated PHY.
> > So they need a single external PHY. Transceivers can be very simple like
> > xceiver-supply in the binding, but I want to use "ti,tcan1043" in
> > drivers/phy/phy-can-transceiver.
>
> I'm not quite following, do all of these devices need to have an
> external phy but the property did not exist until now? How did any of
> them work, if that's the case?
The property xceiver-supply is used to describe connected transceiver
which do only rely on corresponding regulator configuration.
For example here:
https://elixir.bootlin.com/linux/v6.14-rc2/source/arch/arm/boot/dts/nxp/imx/imx6qdl-sabreauto.dtsi#L105
But I want to enable support for these:
https://elixir.bootlin.com/linux/v6.14-rc2/source/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml
Best regards,
Dimitri Fedrau
next prev parent reply other threads:[~2025-02-14 5:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 13:12 [PATCH 0/2] can: flexcan: add transceiver capabilities Dimitri Fedrau
2025-02-11 13:12 ` Dimitri Fedrau via B4 Relay
2025-02-11 13:12 ` [PATCH 1/2] dt-bindings: can: fsl,flexcan: " Dimitri Fedrau
2025-02-11 13:12 ` Dimitri Fedrau via B4 Relay
2025-02-11 16:38 ` Conor Dooley
2025-02-12 19:52 ` Dimitri Fedrau
2025-02-13 20:07 ` Conor Dooley
2025-02-14 5:05 ` Dimitri Fedrau [this message]
2025-02-18 17:15 ` Conor Dooley
2025-02-19 9:15 ` Marc Kleine-Budde
2025-02-19 10:28 ` Dimitri Fedrau
2025-02-11 13:12 ` [PATCH 2/2] can: flexcan: " Dimitri Fedrau
2025-02-11 13:12 ` Dimitri Fedrau via B4 Relay
2025-02-19 9:41 ` Marc Kleine-Budde
2025-02-19 10:39 ` Dimitri Fedrau
2025-02-19 11:00 ` Marc Kleine-Budde
-- strict thread matches above, loose matches on Subject: below --
2025-02-19 10:14 [PATCH 1/2] dt-bindings: can: fsl,flexcan: " Fedrau Dimitri (LED)
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=20250214050540.GA3602@debian \
--to=dima.fedrau@gmail.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dimitri.fedrau@liebherr.com \
--cc=krzk+dt@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=robh@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.