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 v3 1/2] dt-bindings: can: fsl,flexcan: add transceiver capabilities
Date: Sat, 22 Feb 2025 08:22:41 +0100 [thread overview]
Message-ID: <20250222072241.GA3458@debian> (raw)
In-Reply-To: <20250221-drinking-tantrum-6e0bf9051160@spud>
Am Fri, Feb 21, 2025 at 04:59:16PM +0000 schrieb Conor Dooley:
> On Fri, Feb 21, 2025 at 08:40:04AM +0100, 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.
> >
> > Signed-off-by: Dimitri Fedrau <dimitri.fedrau@liebherr.com>
> > ---
> > .../devicetree/bindings/net/can/fsl,flexcan.yaml | 15 +++++++++++++++
> > 1 file changed, 15 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml b/Documentation/devicetree/bindings/net/can/fsl,flexcan.yaml
> > index 73252fe56fe6c8e9fd19142208bb655dc86d47cd..81125883cf86b9d19616bde378f74bdb6a32f1b2 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: |
> > @@ -171,6 +174,18 @@ allOf:
> > interrupts:
> > maxItems: 1
> > interrupt-names: false
> > + - if:
> > + required:
> > + - xceiver-supply
> > + then:
> > + properties:
> > + phys: false
> > + - if:
> > + required:
> > + - phys
> > + then:
> > + properties:
> > + xceiver-supply: false
>
> The duplication here is not needed, they both will cause errors in the
> same situation. With one dropped,
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
>
Thanks for your help, will drop one and sent out a V4.
Best regards,
Dimitri Fedrau
next prev parent reply other threads:[~2025-02-22 7:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 7:40 [PATCH v3 0/2] can: flexcan: add transceiver capabilities Dimitri Fedrau via B4 Relay
2025-02-21 7:40 ` [PATCH v3 1/2] dt-bindings: can: fsl,flexcan: " Dimitri Fedrau via B4 Relay
2025-02-21 16:59 ` Conor Dooley
2025-02-22 7:22 ` Dimitri Fedrau [this message]
2025-02-21 7:40 ` [PATCH v3 2/2] can: flexcan: " Dimitri Fedrau via B4 Relay
2025-02-21 8:11 ` [PATCH v3 0/2] " Marc Kleine-Budde
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=20250222072241.GA3458@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 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).