From: Dimitri Fedrau <dimitri.fedrau@liebherr.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@microchip.com>
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 73252fe56fe6c8e9fd19142208bb655dc86d47cd..a7b9ae2b2546b801623117179e16c4ffc11a234e 100644
--- a/Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml
+++ b/Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml
@@ -77,6 +77,9 @@ properties:
xceiver-supply:
description: Regulator that powers the CAN transceiver.
+ phys:
+ maxItems: 1
+
big-endian:
$ref: /schemas/types.yaml#/definitions/flag
description: |
--
2.39.5
On 20.02.2025 09:22:10, Dimitri Fedrau via B4 Relay wrote: > From: Dimitri Fedrau <dimitri.fedrau@liebherr.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@microchip.com> > Signed-off-by: Dimitri Fedrau <dimitri.fedrau@liebherr.com> Is it possible express in the biding that we either want to have xceiver-supply or phys? regards, Marc > --- > 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 73252fe56fe6c8e9fd19142208bb655dc86d47cd..a7b9ae2b2546b801623117179e16c4ffc11a234e 100644 > --- a/Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml > +++ b/Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml > @@ -77,6 +77,9 @@ properties: > xceiver-supply: > description: Regulator that powers the CAN transceiver. > > + phys: > + maxItems: 1 > + > big-endian: > $ref: /schemas/types.yaml#/definitions/flag > description: | > > -- > 2.39.5 > > > -- 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 |
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@liebherr.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@microchip.com> > > Signed-off-by: Dimitri Fedrau <dimitri.fedrau@liebherr.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. Best regards, Dimitri Fedrau [...]
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@liebherr.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@microchip.com> > > > Signed-off-by: Dimitri Fedrau <dimitri.fedrau@liebherr.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 |
On Thu, Feb 20, 2025 at 05:02:56PM +0100, Marc Kleine-Budde wrote:
> 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@liebherr.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@microchip.com>
> > > > Signed-off-by: Dimitri Fedrau <dimitri.fedrau@liebherr.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"]
# the internal reference buffer always requires high-z mode
- if:
required:
- refin-supply
then:
properties:
adi,no-ref-high-z: false
Do it like so ;)
Cheers,
Conor.
© 2016 - 2025 Red Hat, Inc.