Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Peng Fan <peng.fan@nxp.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
	Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
	Vinod Koul <vkoul@kernel.org>,
	Kishon Vijay Abraham I <kishon@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Aswath Govindraju <a-govindraju@ti.com>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>, Frank Li <frank.li@nxp.com>,
	Haibo Chen <haibo.chen@nxp.com>,
	linux-can@vger.kernel.org, linux-phy@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 1/6] dt-bindings: phy: ti,tcan104x-can: Document NXP TJA105X/1048
Date: Mon, 1 Sep 2025 20:00:25 +0100	[thread overview]
Message-ID: <20250901-uproar-shrill-07d51ea21a29@spud> (raw)
In-Reply-To: <20250901-diligent-dreaded-59b9ad5c3976@spud>

[-- Attachment #1: Type: text/plain, Size: 3266 bytes --]

On Mon, Sep 01, 2025 at 07:54:01PM +0100, Conor Dooley wrote:
> On Mon, Sep 01, 2025 at 11:18:11AM +0800, Peng Fan wrote:
> > The TJA105[1,7] is a high-speed CAN transceiver which is a pin-compatible
> > alternative for TI TCAN1043 with sleep mode supported, and has a compatible
> > programming model, therefore use ti,tcan1043 as fallback compatible.
> > 
> > The TJA1048 is a dual high-speed CAN transceiver with sleep mode supported.
> > 
> > Reviewed-by: Frank Li <Frank.Li@nxp.com>
> > Signed-off-by: Peng Fan <peng.fan@nxp.com>
> > ---
> >  .../devicetree/bindings/phy/ti,tcan104x-can.yaml   | 30 ++++++++++++++++++++--
> >  1 file changed, 28 insertions(+), 2 deletions(-)
> > 
> > diff --git a/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml b/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml
> > index 4a8c3829d85d3c4a4963750d03567c1c345beb91..f8e0c24856a2ba83b5c988b246464f47e11a032f 100644
> > --- a/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml
> > +++ b/Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml
> > @@ -19,18 +19,25 @@ properties:
> >            - enum:
> >                - microchip,ata6561
> >            - const: ti,tcan1042
> > +      - items:
> > +          - enum:
> > +              - nxp,tja1051
> > +              - nxp,tja1057
> > +          - const: ti,tcan1043
> >        - enum:
> >            - ti,tcan1042
> >            - ti,tcan1043
> > +          - nxp,tja1048
> >            - nxp,tjr1443
> >  
> >    '#phy-cells':
> > -    const: 0
> > +    enum: [0, 1]
> >  
> >    standby-gpios:
> >      description:
> >        gpio node to toggle standby signal on transceiver
> > -    maxItems: 1
> > +    minItems: 1
> > +    maxItems: 2
> 
> You're adding a second standby gpio, which one is which?
> I assume you mean that item 1 is stbn1 and item 2 is stbn 2 for tja1048.
> Might be kinda obvious, but I think it should be mentioned.
> 
> tja105{1,7} don't have a standby gpio, but they do have a silent mode.
> silent mode seems fundamentally different to standby, since the receiver
> still works. Seems like that should be handled differently, no?

The docs for standby mode for the tcan1043 don't match with the tja1051,
"Standby mode is a low power mode where the driver and receiver are
disabled," so does the fallback compatible even make sense? Seems like a
combination of enable and standby gpios are used to put the tcan device
into silent mode but the tja1051 has a pin for that alone and seemingly
does not support standby at all?

> 
> >  
> >    enable-gpios:
> >      description:
> > @@ -53,6 +60,25 @@ required:
> >    - compatible
> >    - '#phy-cells'
> >  
> > +allOf:
> > +  - if:
> > +      properties:
> > +        compatible:
> > +          contains:
> > +            const: nxp,tja1048
> > +    then:
> > +      properties:
> > +        '#phy-cells':
> > +          const: 1
> > +        standby-gpios:
> > +          minItems: 2
> > +    else:
> > +      properties:
> > +        '#phy-cells':
> > +          const: 0
> > +        standby-gpios:
> > +          maxItems: 1
> > +
> >  additionalProperties: false
> >  
> >  examples:
> > 
> > -- 
> > 2.37.1
> > 



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-09-02  0:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-01  3:18 [PATCH v4 0/6] phy: phy-can-transceiver: Support TJA1048/TJA1051 Peng Fan
2025-09-01  3:18 ` [PATCH v4 1/6] dt-bindings: phy: ti,tcan104x-can: Document NXP TJA105X/1048 Peng Fan
2025-09-01 18:54   ` Conor Dooley
2025-09-01 19:00     ` Conor Dooley [this message]
2025-09-02  2:24       ` Peng Fan
2025-09-02 19:31         ` Conor Dooley
2025-09-03  6:00           ` Peng Fan
2025-09-03  6:49             ` Peng Fan
2025-09-03 16:25               ` Conor Dooley
2025-09-01  3:18 ` [PATCH v4 2/6] phy: phy-can-transceiver: Introduce can_transceiver_priv Peng Fan
2025-09-01  3:18 ` [PATCH v4 3/6] phy: phy-can-transceiver: Add dual channel support for TJA1048 Peng Fan
2025-09-01  3:18 ` [PATCH v4 4/6] arm64: dts: imx95-15x15-evk: Use phys to replace xceiver-supply Peng Fan
2025-09-01  3:18 ` [PATCH v4 5/6] arm64: dts: imx8mp-evk: " Peng Fan
2025-09-01  3:18 ` [PATCH v4 6/6] arm64: dts: imx93-11x11-evk: " Peng Fan

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=20250901-uproar-shrill-07d51ea21a29@spud \
    --to=conor@kernel.org \
    --cc=a-govindraju@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=frank.li@nxp.com \
    --cc=haibo.chen@nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=kishon@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=mailhol.vincent@wanadoo.fr \
    --cc=mkl@pengutronix.de \
    --cc=peng.fan@nxp.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=vkoul@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