From: "Frank.Sae" <Frank.Sae@motor-comm.com>
To: Rob Herring <robh@kernel.org>
Cc: Peter Geis <pgwipeout@gmail.com>, Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
yanhong.wang@starfivetech.com, xiaogang.fan@motor-comm.com,
fei.zhang@motor-comm.com, hua.sun@motor-comm.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v3 1/5] dt-bindings: net: Add Motorcomm yt8xxx ethernet phy
Date: Tue, 31 Jan 2023 11:19:33 +0800 [thread overview]
Message-ID: <af6beebc-0a70-16f5-e0e9-5f4cbeea8955@motor-comm.com> (raw)
In-Reply-To: <20230130224158.GA3655289-robh@kernel.org>
Hi Rob,
On 2023/1/31 06:41, Rob Herring wrote:
> On Mon, Jan 30, 2023 at 02:35:35PM +0800, Frank Sae wrote:
>> Add a YAML binding document for the Motorcom yt8xxx Ethernet phy driver.
>
> Bindings are for h/w devices, not drivers.
>
>>
>> Signed-off-by: Frank Sae <Frank.Sae@motor-comm.com>
>> ---
>> .../bindings/net/motorcomm,yt8xxx.yaml | 102 ++++++++++++++++++
>> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
>> MAINTAINERS | 1 +
>> 3 files changed, 105 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/net/motorcomm,yt8xxx.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/net/motorcomm,yt8xxx.yaml b/Documentation/devicetree/bindings/net/motorcomm,yt8xxx.yaml
>> new file mode 100644
>> index 000000000000..8527576c15b3
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/net/motorcomm,yt8xxx.yaml
>> @@ -0,0 +1,102 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/net/motorcomm,yt8xxx.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: MotorComm yt8xxx Ethernet PHY
>> +
>> +maintainers:
>> + - frank sae <frank.sae@motor-comm.com>
>> +
>> +allOf:
>> + - $ref: ethernet-phy.yaml#
>
> This schema doesn't work because there is no way to determine whether to
> apply it or not. You need a compatible for your phy.
>
I don't understand how to add a compatible for my phy.
compatible:
oneOf:
- enum:
- fsl,imx25-fec
- fsl,imx27-fec
compatible usually like this, but it is usually for mac or mdio.
phy id list:
YT8511 0x0000010a
YT8521 0x0000011A
YT8531 0x4f51e91b
motorcomm,yt8xxx.yaml
mdio0 {
...
ethernet-phy@5 {
compatible = "ethernet-phy-id0000.010a",
"ethernet-phy-id0000.011a",
"ethernet-phy-id4f51.e91b",
"ethernet-phy-ieee802.3-c22";
reg = <5>;
...
};
};
Should i add compatible like this ?
If above is error, please give me an example, thanks!
> Rob
next prev parent reply other threads:[~2023-01-31 3:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 6:35 [PATCH net-next v3 0/5] add dts for yt8521 and yt8531s, add driver for yt8531 Frank Sae
2023-01-30 6:35 ` [PATCH net-next v3 1/5] dt-bindings: net: Add Motorcomm yt8xxx ethernet phy Frank Sae
2023-01-30 14:03 ` Andrew Lunn
2023-01-31 2:21 ` Frank.Sae
2023-01-31 13:42 ` Andrew Lunn
2023-01-30 22:41 ` Rob Herring
2023-01-31 3:19 ` Frank.Sae [this message]
2023-01-31 13:33 ` Andrew Lunn
2023-01-31 18:56 ` Krzysztof Kozlowski
2023-01-30 6:35 ` [PATCH net-next v3 2/5] net: phy: Add BIT macro for Motorcomm yt8521/yt8531 gigabit " Frank Sae
2023-01-30 6:35 ` [PATCH net-next v3 3/5] net: phy: Add dts support for Motorcomm yt8521 " Frank Sae
2023-01-30 6:35 ` [PATCH net-next v3 4/5] net: phy: Add dts support for Motorcomm yt8531s " Frank Sae
2023-01-30 6:35 ` [PATCH net-next v3 5/5] net: phy: Add driver for Motorcomm yt8531 " Frank Sae
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=af6beebc-0a70-16f5-e0e9-5f4cbeea8955@motor-comm.com \
--to=frank.sae@motor-comm.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=fei.zhang@motor-comm.com \
--cc=hkallweit1@gmail.com \
--cc=hua.sun@motor-comm.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pgwipeout@gmail.com \
--cc=robh@kernel.org \
--cc=xiaogang.fan@motor-comm.com \
--cc=yanhong.wang@starfivetech.com \
/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
all inboxes | Powered by JetHome®