[PATCH v2] dt-bindings: phy: ti,tcan104x-can: Document TI TCAN1046

[Lad, Prabhakar]

Hi Conor,

On Wed, Dec 10, 2025 at 6:21 PM Conor Dooley <conor at kernel.org> wrote:
>
> On Wed, Dec 10, 2025 at 08:52:58AM +0100, Marc Kleine-Budde wrote:
> > On 09.12.2025 16:21:19, Prabhakar wrote:
> > > From: Lad Prabhakar <prabhakar.mahadev-lad.rj at bp.renesas.com>
> > >
> > > Document the TI TCAN1046 automotive CAN transceiver. The TCAN1046 is a
> > > dual high-speed CAN transceiver with sleep-mode support and no EN pin,
> > > mirroring the behaviour of the NXP TJA1048, which also provides dual
> > > channels and STB1/2 sleep-control lines.
> > >
> > > Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj at bp.renesas.com>
> > > ---
> > > TCAN 1046, https://www.ti.com/lit/ds/symlink/tcan1046v-q1.pdf?ts=1765297159307&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FTCAN1046V-Q1
> > > NXP TJA1048, https://www.nxp.com/docs/en/data-sheet/TJA1048.pdf
> >
> > The polarity of the standby line of the chips is different.
> >
> > You must set the correct active high/low property for the GPIO, as the
> > driver uses logical levels.
> >
> > Reviewed-by: Marc Kleine-Budde <mkl at pengutronix.de>
>
> What you're saying seems to contradict the tag you've given, is a
> fallback really suitable if the standby polarity is not the same?
>
On the RZ/V2H I have,

    can_phy: can-phy {
        compatible = "ti,tcan1046", "nxp,tja1048";
        max-bitrate = <8000000>;
        #phy-cells = <1>;
        status = "okay";
        standby-gpios = <&pinctrl RZV2H_GPIO(7, 0) GPIO_ACTIVE_HIGH>,
                                  <&pinctrl RZV2H_GPIO(7, 2) GPIO_ACTIVE_HIGH>;
    };

When the CAN interface is brought up 0 is written to GPIO which brings
the CAN transceiver to Normal mode  and when the CAN chip is brought
down `1` is written to GPIO and it puts the CAN transceiver to Standby
mode. Which matches to the behaviour of TCAN1046 CAN transceiver. Am I
missing something?

Cheers,
Prabhakar