[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250220-intelligent-serious-badger-978793-mkl@pengutronix.de>
Date: Thu, 20 Feb 2025 17:02:56 +0100
From: Marc Kleine-Budde <mkl@...gutronix.de>
To: Dimitri Fedrau <dima.fedrau@...il.com>
Cc: Dimitri Fedrau via B4 Relay <devnull+dimitri.fedrau.liebherr.com@...nel.org>,
Vincent Mailhol <mailhol.vincent@...adoo.fr>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, linux-can@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
Dimitri Fedrau <dimitri.fedrau@...bherr.com>, Conor Dooley <conor.dooley@...rochip.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: can: fsl,flexcan: add transceiver
capabilities
On 20.02.2025 16:56:42, Dimitri Fedrau wrote:
> Am Thu, Feb 20, 2025 at 09:44:50AM +0100 schrieb Marc Kleine-Budde:
> > On 20.02.2025 09:22:10, Dimitri Fedrau via B4 Relay wrote:
> > > From: Dimitri Fedrau <dimitri.fedrau@...bherr.com>
> > >
> > > Currently the flexcan driver does only support adding PHYs by using the
> > > "old" regulator bindings. Add support for CAN transceivers as a PHY.
> > >
> > > Acked-by: Conor Dooley <conor.dooley@...rochip.com>
> > > Signed-off-by: Dimitri Fedrau <dimitri.fedrau@...bherr.com>
> >
> > Is it possible express in the biding that we either want to have
> > xceiver-supply or phys?
> >
> I didn't found anything to express that in the binding.
What about something like this:
| dependencies:
| prop-a: ["!prop-b"]
| prop-b: ["!prop-a"]
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung Nürnberg | Phone: +49-5121-206917-129 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists