From: Michael Walle <michael@walle.cc>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Xu Liang <lxu@maxlinear.com>,
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>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v1 3/4] dt-bindings: net: phy: add MaxLinear GPY2xx bindings
Date: Fri, 02 Dec 2022 23:50:18 +0100 [thread overview]
Message-ID: <56d66e0da56b33d668362e5701399499@walle.cc> (raw)
In-Reply-To: <Y4pEhjDOGmpmj/Kk@lunn.ch>
Am 2022-12-02 19:31, schrieb Andrew Lunn:
> On Fri, Dec 02, 2022 at 04:12:03PM +0100, Michael Walle wrote:
>> Add the device tree bindings for the MaxLinear GPY2xx PHYs.
>>
>> Signed-off-by: Michael Walle <michael@walle.cc>
>> ---
>>
>> Is the filename ok? I was unsure because that flag is only for the
>> GPY215
>> for now. But it might also apply to others. Also there is no
>> compatible
>> string, so..
>>
>> .../bindings/net/maxlinear,gpy2xx.yaml | 47
>> +++++++++++++++++++
>> 1 file changed, 47 insertions(+)
>> create mode 100644
>> Documentation/devicetree/bindings/net/maxlinear,gpy2xx.yaml
>>
>> diff --git
>> a/Documentation/devicetree/bindings/net/maxlinear,gpy2xx.yaml
>> b/Documentation/devicetree/bindings/net/maxlinear,gpy2xx.yaml
>> new file mode 100644
>> index 000000000000..d71fa9de2b64
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/net/maxlinear,gpy2xx.yaml
>> @@ -0,0 +1,47 @@
>> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/net/maxlinear,gpy2xx.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: MaxLinear GPY2xx PHY
>> +
>> +maintainers:
>> + - Andrew Lunn <andrew@lunn.ch>
>> + - Michael Walle <michael@walle.cc>
>> +
>> +allOf:
>> + - $ref: ethernet-phy.yaml#
>> +
>> +properties:
>> + maxlinear,use-broken-interrupts:
>> + description: |
>> + Interrupts are broken on some GPY2xx PHYs in that they keep the
>> + interrupt line asserted even after the interrupt status
>> register is
>> + cleared. Thus it is blocking the interrupt line which is
>> usually bad
>> + for shared lines. By default interrupts are disabled for this
>> PHY and
>> + polling mode is used. If one can live with the consequences,
>> this
>> + property can be used to enable interrupt handling.
>> +
>> + Affected PHYs (as far as known) are GPY215B and GPY215C.
>> + type: boolean
>> +
>> +dependencies:
>> + maxlinear,use-broken-interrupts: [ interrupts ]
>> +
>> +unevaluatedProperties: false
>> +
>> +examples:
>> + - |
>> + ethernet {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + ethernet-phy@0 {
>> + reg = <0>;
>> + interrupts-extended = <&intc 0>;
>> + maxlinear,use-broken-interrupts;
>> + };
>> + };
>
> I'm wondering if we want this in the example. We probably don't want
> people to use this property by accident, i.e. copy/paste without
> reading the rest of the document. This will becomes a bigger problem
> if more properties are added, RGMII delays etc.
>
> So maybe just skip the example?
I agree. Let's wait what the device tree maintainers say.
-michael
next prev parent reply other threads:[~2022-12-02 22:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 15:12 [PATCH net-next v1 0/4] net: phy: mxl-gpy: broken interrupt fixes Michael Walle
2022-12-02 15:12 ` [PATCH net-next v1 1/4] net: phy: mxl-gpy: add MDINT workaround Michael Walle
2022-12-02 18:23 ` Andrew Lunn
2022-12-02 22:53 ` Michael Walle
2022-12-02 15:12 ` [PATCH net-next v1 2/4] dt-bindings: vendor-prefixes: add MaxLinear Michael Walle
2022-12-02 15:28 ` Krzysztof Kozlowski
2022-12-02 15:12 ` [PATCH net-next v1 3/4] dt-bindings: net: phy: add MaxLinear GPY2xx bindings Michael Walle
2022-12-02 18:31 ` Andrew Lunn
2022-12-02 22:50 ` Michael Walle [this message]
2022-12-05 21:29 ` Rob Herring
2022-12-05 21:53 ` Michael Walle
2022-12-06 8:29 ` Michael Walle
2022-12-06 8:38 ` Krzysztof Kozlowski
2022-12-06 9:44 ` Michael Walle
2022-12-16 9:03 ` Michael Walle
2022-12-20 13:21 ` Andrew Lunn
2022-12-28 15:00 ` Michael Walle
2022-12-02 15:12 ` [PATCH net-next v1 4/4] net: phy: mxl-gpy: disable interrupts on GPY215 by default Michael Walle
2022-12-02 18:42 ` Andrew Lunn
2022-12-02 23:09 ` Michael Walle
2022-12-03 20:36 ` Andrew Lunn
2022-12-16 9:46 ` Michael Walle
2022-12-20 13:33 ` Andrew Lunn
2022-12-20 21:39 ` Michael Walle
2022-12-03 20:41 ` [PATCH net-next v1 0/4] net: phy: mxl-gpy: broken interrupt fixes Andrew Lunn
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=56d66e0da56b33d668362e5701399499@walle.cc \
--to=michael@walle.cc \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lxu@maxlinear.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).