linux-stable.git/drivers/phy/phy-can-transceiver.c, branch linux-rolling-stable

phy: phy-can-transceiver: Check driver match and driver data against NULL

2026-07-24T14:20:00+00:00

[ Upstream commit ebee9004cc0200b2b708ebf7ac625d35c71c049f ]

Every platform driver can be forced to match a device that doesn't
match its list of device IDs because of device_match_driver_override()
so platform drivers that rely on the existence of a device's driver
data need to verify its presence.

Accordingly, add requisite match and driver data checks against NULL
to the driver where they are missing.

Fixes: a4a86d273ff1 ("phy: phy-can-transceiver: Add support for generic CAN transceiver driver")
Signed-off-by: Andy Shevchenko 
Link: https://patch.msgid.link/20260513220336.369628-2-andriy.shevchenko@linux.intel.com
Signed-off-by: Vinod Koul 
Signed-off-by: Sasha Levin

phy: can-transceiver: drop temporary helper getting optional mux-state

2026-03-09T12:44:45+00:00

Multiplexer subsystem has now added helpers for getting managed optional
mux-state.

Switch to the new devm_mux_state_get_optional helper.

This change is only compile-tested.

Acked-by: Vinod Koul 
Reviewed-by: Geert Uytterhoeven 
Reviewed-by: Wolfram Sang 
Signed-off-by: Josua Mayer 
Signed-off-by: Ulf Hansson

phy: can-transceiver: rename temporary helper function to avoid conflict

2026-03-09T12:44:44+00:00

Rename the temporary devm_mux_state_get_optional function to avoid
conflict with upcoming implementation in multiplexer subsystem.

Signed-off-by: Josua Mayer 
Acked-by: Vinod Koul 
Reviewed-by: Wolfram Sang 
Signed-off-by: Ulf Hansson

phy: phy-can-transceiver: Add support for TJA105{1,7}

2025-11-12T14:41:16+00:00

Support TJA105{1,7} which are a single channel high-speed CAN transceiver
with silent mode supported.

phy mode is not implemented as of now. silent settings are kept in
phy_power_on and phy_power_off. After phy mode is supported, the silent
settings could be moved to phy_set_mode.

Reviewed-by: Frank Li 
Signed-off-by: Peng Fan 
Acked-by: Marc Kleine-Budde 
Link: https://patch.msgid.link/20251001-can-v7-5-fad29efc3884@nxp.com
Signed-off-by: Vinod Koul

phy: phy-can-transceiver: Drop the gpio desc check

2025-11-12T14:41:15+00:00

gpiod_set_value_cansleep has an internal check on gpio_desc using
'VALIDATE_DESC(desc)', the check before invoking gpiod_set_value_cansleep
could be removed.

Reviewed-by: Frank Li 
Signed-off-by: Peng Fan 
Acked-by: Marc Kleine-Budde 
Link: https://patch.msgid.link/20251001-can-v7-4-fad29efc3884@nxp.com
Signed-off-by: Vinod Koul

phy: phy-can-transceiver: Add dual channel support for TJA1048

2025-11-12T14:41:15+00:00

- Introduce new flag CAN_TRANSCEIVER_DUAL_CH to indicate the phy has two
  channels.
- Alloc a phy for each channel
- Support TJA1048 which is a dual high-speed CAN transceiver with sleep
  mode supported.
- Add can_transceiver_phy_xlate for parsing phy

Reviewed-by: Frank Li 
Signed-off-by: Peng Fan 
Acked-by: Marc Kleine-Budde 
Link: https://patch.msgid.link/20251001-can-v7-3-fad29efc3884@nxp.com
Signed-off-by: Vinod Koul

phy: phy-can-transceiver: Introduce can_transceiver_priv

2025-11-12T14:41:15+00:00

To prepare for dual-channel phy support, introduce can_transceiver_priv as
a higher level encapsulation for phy.

No functional changes.

Reviewed-by: Frank Li 
Signed-off-by: Peng Fan 
Acked-by: Marc Kleine-Budde 
Link: https://patch.msgid.link/20251001-can-v7-2-fad29efc3884@nxp.com
Signed-off-by: Vinod Koul

phy: can-transceiver: Re-instate "mux-states" property presence check

2025-04-11T11:30:15+00:00

On the Renesas Gray Hawk Single development board:

    can-transceiver-phy can-phy0: /can-phy0: failed to get mux-state (0)

"mux-states" is an optional property for CAN transceivers.  However,
mux_get() always prints an error message in case of an error, including
when the property is not present, confusing the user.

Fix this by re-instating the property presence check (this time using
the proper API) in a wrapper around devm_mux_state_get().  When the
multiplexer subsystem gains support for optional muxes, the wrapper can
just be removed.

In addition, propagate all real errors upstream, instead of ignoring
them.

Fixes: d02dfd4ceb2e9f34 ("phy: can-transceiver: Drop unnecessary "mux-states" property presence check")
Signed-off-by: Geert Uytterhoeven 
Tested-by: Biju Das 
Reviewed-by: Biju Das 
Reviewed-by: Vincent Mailhol 
Link: https://lore.kernel.org/r/3d7e0d723908284e8cf06ad1f7950c03173178f3.1742483710.git.geert+renesas@glider.be
Signed-off-by: Vinod Koul

phy: can-transceiver: Drop unnecessary "mux-states" property presence check

2025-02-10T17:10:19+00:00

It doesn't matter whether "mux-states" is not present or there is some
other issue parsing it causing an error. Drop the presence check and
rework the error handling to ignore anything other than deferred probe.

Acked-by: Marc Kleine-Budde 
Signed-off-by: Rob Herring (Arm) 
Link: https://lore.kernel.org/r/20250203185421.3383805-2-robh@kernel.org
Signed-off-by: Vinod Koul

phy: phy-can-transceiver: insert space after include

2023-12-21T17:09:59+00:00

Maintain Consistent Formatting: Insert Space after #include

Signed-off-by: Wang Jinchao 
Reviewed-by: Marc Kleine-Budde 
Link: https://lore.kernel.org/r/202312151407+0800-wangjinchao@xfusion.com
Signed-off-by: Vinod Koul