All of lore.kernel.org
 help / color / mirror / Atom feed
From: <markus.stockhausen@gmx.de>
To: "'Rob Herring'" <robh@kernel.org>
Cc: <linux-phy@lists.infradead.org>,
	<chris.packham@alliedtelesis.co.nz>, <devicetree@vger.kernel.org>,
	<krzk@kernel.org>
Subject: AW: [PATCH v2 1/3] dt-bindings: phy: add realtek,otto-serdes PHY binding
Date: Tue, 8 Oct 2024 14:27:18 +0200	[thread overview]
Message-ID: <001f01db197d$6c842e90$458c8bb0$@gmx.de> (raw)
In-Reply-To: <20241007193044.GA2255474-robh@kernel.org>

> -----Ursprüngliche Nachricht-----
> Von: Rob Herring <robh@kernel.org> 
> Gesendet: Montag, 7. Oktober 2024 21:31
> An: Markus Stockhausen <markus.stockhausen@gmx.de>
> Cc: linux-phy@lists.infradead.org; chris.packham@alliedtelesis.co.nz;
devicetree@vger.kernel.org; krzk@kernel.org
> Betreff: Re: [PATCH v2 1/3] dt-bindings: phy: add realtek,otto-serdes PHY
binding
> ...
> > +
> > +properties:
> > +  $nodename:
> > +    pattern: "^serdes@[0-9a-f]+$"
>
> The node name for phy providers is 'phy'.

Hi Rob,

I found different configs in other files. E.g.

- torrent-phy@f0fb500000
- serdes: serdes@e2004010
- serdes_phy: phy@8901000

Do I understand correctly that I should go with "serdes: phy@1b00e780"? 
If yes, adapt the $nodename pattern accordingly or drop it as in most other
files?

Best regards.

Markus


-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

WARNING: multiple messages have this Message-ID (diff)
From: <markus.stockhausen@gmx.de>
To: "'Rob Herring'" <robh@kernel.org>
Cc: <linux-phy@lists.infradead.org>,
	<chris.packham@alliedtelesis.co.nz>, <devicetree@vger.kernel.org>,
	<krzk@kernel.org>
Subject: AW: [PATCH v2 1/3] dt-bindings: phy: add realtek,otto-serdes PHY binding
Date: Tue, 8 Oct 2024 14:27:18 +0200	[thread overview]
Message-ID: <001f01db197d$6c842e90$458c8bb0$@gmx.de> (raw)
In-Reply-To: <20241007193044.GA2255474-robh@kernel.org>

> -----Ursprüngliche Nachricht-----
> Von: Rob Herring <robh@kernel.org> 
> Gesendet: Montag, 7. Oktober 2024 21:31
> An: Markus Stockhausen <markus.stockhausen@gmx.de>
> Cc: linux-phy@lists.infradead.org; chris.packham@alliedtelesis.co.nz;
devicetree@vger.kernel.org; krzk@kernel.org
> Betreff: Re: [PATCH v2 1/3] dt-bindings: phy: add realtek,otto-serdes PHY
binding
> ...
> > +
> > +properties:
> > +  $nodename:
> > +    pattern: "^serdes@[0-9a-f]+$"
>
> The node name for phy providers is 'phy'.

Hi Rob,

I found different configs in other files. E.g.

- torrent-phy@f0fb500000
- serdes: serdes@e2004010
- serdes_phy: phy@8901000

Do I understand correctly that I should go with "serdes: phy@1b00e780"? 
If yes, adapt the $nodename pattern accordingly or drop it as in most other
files?

Best regards.

Markus


  reply	other threads:[~2024-10-08 12:31 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-07 16:36 [PATCH v2 0/3] phy: Realtek Otto SerDes: add new driver Markus Stockhausen
2024-10-07 16:36 ` Markus Stockhausen
2024-10-07 16:36 ` [PATCH v2 1/3] dt-bindings: phy: add realtek,otto-serdes PHY binding Markus Stockhausen
2024-10-07 16:36   ` Markus Stockhausen
2024-10-07 18:17   ` Rob Herring (Arm)
2024-10-07 18:17     ` Rob Herring (Arm)
2024-10-07 19:26   ` Krzysztof Kozlowski
2024-10-07 19:26     ` Krzysztof Kozlowski
2024-10-08  5:38     ` AW: " markus.stockhausen
2024-10-08  5:38       ` markus.stockhausen
2024-10-08  6:17       ` Krzysztof Kozlowski
2024-10-08  6:17         ` Krzysztof Kozlowski
2024-10-08  6:56         ` AW: " markus.stockhausen
2024-10-08  6:56           ` markus.stockhausen
2024-10-08  8:32           ` Krzysztof Kozlowski
2024-10-08  8:32             ` Krzysztof Kozlowski
2024-10-08  9:27             ` AW: " markus.stockhausen
2024-10-08  9:27               ` markus.stockhausen
2024-10-16 15:30     ` markus.stockhausen
2024-10-16 15:30       ` markus.stockhausen
2024-10-17  6:15       ` Krzysztof Kozlowski
2024-10-17  6:15         ` Krzysztof Kozlowski
2024-10-07 19:30   ` Rob Herring
2024-10-07 19:30     ` Rob Herring
2024-10-08 12:27     ` markus.stockhausen [this message]
2024-10-08 12:27       ` AW: " markus.stockhausen
2024-10-08  7:04   ` Krzysztof Kozlowski
2024-10-08  7:04     ` Krzysztof Kozlowski
2024-10-08  7:06   ` Krzysztof Kozlowski
2024-10-08  7:06     ` Krzysztof Kozlowski
2024-10-07 16:36 ` [PATCH v2 2/3] phy: Realtek Otto SerDes driver Markus Stockhausen
2024-10-07 16:36   ` Markus Stockhausen
2024-10-07 19:32   ` Krzysztof Kozlowski
2024-10-07 19:32     ` Krzysztof Kozlowski
2024-10-11 16:10     ` AW: " markus.stockhausen
2024-10-11 16:19       ` Krzysztof Kozlowski
2024-10-07 16:36 ` [PATCH v2 3/3] phy: Integrate Realtek Otto SerDes driver into build system Markus Stockhausen
2024-10-07 16:36   ` Markus Stockhausen
2024-10-07 19:27   ` Krzysztof Kozlowski
2024-10-07 19:27     ` Krzysztof Kozlowski
2024-10-08  6:38   ` kernel test robot
2024-10-08  6:38     ` kernel test robot
2024-10-08  7:20   ` kernel test robot
2024-10-08  7:20     ` kernel test robot
2024-10-08  8:21   ` kernel test robot
2024-10-08  8:21     ` kernel test robot

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='001f01db197d$6c842e90$458c8bb0$@gmx.de' \
    --to=markus.stockhausen@gmx.de \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.