From: Dimitri Fedrau via B4 Relay <devnull+dimitri.fedrau.liebherr.com@kernel.org>
To: 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>
Cc: linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
Dimitri Fedrau <dimitri.fedrau@liebherr.com>,
Dimitri Fedrau <dima.fedrau@gmail.com>,
Conor Dooley <conor.dooley@microchip.com>
Subject: [PATCH RESEND v4 0/2] can: flexcan: add transceiver capabilities
Date: Wed, 12 Mar 2025 18:45:21 +0100 [thread overview]
Message-ID: <20250312-flexcan-add-transceiver-caps-v4-0-29e89ae0225a@liebherr.com> (raw)
Currently the flexcan driver does only support adding PHYs by using the
"old" regulator bindings. Add support for CAN transceivers as a PHY. 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>
---
Changes in v4:
- Dropped "if: required: phys" in bindings
- Link to v3: https://lore.kernel.org/r/20250221-flexcan-add-transceiver-caps-v3-0-a947bde55a62@liebherr.com
Changes in v3:
- Have xceiver-supply or phys properties in bindings
- Switch do dev_err_probe in flexcan_probe when checking error of call
devm_phy_optional_get
- Link to v2: https://lore.kernel.org/r/20250220-flexcan-add-transceiver-caps-v2-0-a81970f11846@liebherr.com
Changes in v2:
- Rename variable xceiver to transceiver in struct flexcan_priv and in
flexcan_probe
- Set priv->can.bitrate_max if transceiver is found
- Fix commit messages which claim that transceivers are not supported
- Do not print error on EPROBE_DEFER after calling devm_phy_optional_get in
flexcan_probe
- Link to v1: https://lore.kernel.org/r/20250211-flexcan-add-transceiver-caps-v1-0-c6abb7817b0f@liebherr.com
---
Dimitri Fedrau (2):
dt-bindings: can: fsl,flexcan: add transceiver capabilities
can: flexcan: add transceiver capabilities
.../devicetree/bindings/net/can/fsl,flexcan.yaml | 9 ++++++++
drivers/net/can/flexcan/flexcan-core.c | 27 +++++++++++++++++-----
drivers/net/can/flexcan/flexcan.h | 1 +
3 files changed, 31 insertions(+), 6 deletions(-)
---
base-commit: 6a24171b9625471abfc90c7b28c4b45bee64b3a4
change-id: 20241209-flexcan-add-transceiver-caps-7cff9400c926
Best regards,
--
Dimitri Fedrau <dimitri.fedrau@liebherr.com>
next reply other threads:[~2025-03-12 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 17:45 Dimitri Fedrau via B4 Relay [this message]
2025-03-12 17:45 ` [PATCH RESEND v4 1/2] dt-bindings: can: fsl,flexcan: add transceiver capabilities Dimitri Fedrau via B4 Relay
2025-03-12 17:45 ` [PATCH RESEND v4 2/2] can: flexcan: " Dimitri Fedrau via B4 Relay
2025-03-14 8:44 ` [PATCH RESEND v4 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=20250312-flexcan-add-transceiver-caps-v4-0-29e89ae0225a@liebherr.com \
--to=devnull+dimitri.fedrau.liebherr.com@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=dima.fedrau@gmail.com \
--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).