Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp2519187rwb; Fri, 2 Dec 2022 10:53:52 -0800 (PST) X-Google-Smtp-Source: AA0mqf4s8U2d5rOyw3iJhmjpAQxTlTHeosQQmzHkDPemQ72gdjC0SoPxZ8F9OssBWtZf/RPOJkSl X-Received: by 2002:a17:907:16a5:b0:7be:42dc:4cfc with SMTP id hc37-20020a17090716a500b007be42dc4cfcmr26422328ejc.128.1670007232260; Fri, 02 Dec 2022 10:53:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1670007232; cv=none; d=google.com; s=arc-20160816; b=wiyJH7TUTydpUPcytKpwYWYYYNVYwQjyxpKkeKRjN/DW+8QTAUgFyX7895RWMSm0Z1 BewMkkpB7UOfT+Vw27yCwx7Vmk4tRO9T/rTXlTD24BDPXWDTBu8da854q71ghz5ai5jQ y8xGRAkFcKy/05VAmN2bXWEWnMhEH5uSJdWn+VnsA9Nj7cHuK2LkXWuPVkNLQWejcINW x9P5ZA/MTw2wRzxsyuBwM4Lo1A0n5Jl+6iOPhktwRrRnpXIRw9shBSXc7Y+8Yph6C5Es og0EaRsvEOow/qvLp9VBUZDFA9DvpRJ9uVAXiA3v7YFGFI/VNcRLBcpuMup3CP7+xu4d iK4A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=wvQ1xDmoE82XyHcjWzE7449aCw7Y023STVt3z9JJKBM=; b=uvVTbcmftzs+S3A8Nkgp3VlbYaqsMZYK6qQ5KxWnmYStNkKRb8CBes/wil99Pm0vlQ QcVSQ2JrdH1EGd+wP/8H2cUoiJdew6oMnT8Ubwv7DLt+qtHLZpVz9hcUZsM0WbujUt7a b1/VB6VBpMzvI7/qtjFVJQM+25yNOQoJNkwd0j8U+fu8bck7HnHdax9ESnxcMgqGqSVv 01iUJdK+wpx2rzjWwdwS/UTu3YV5xukdNn+MAIFI+PfuIaIBhyD5MtULS4ZZ5tNZCxYF Ry+ie0uS0WP84UV+2MCLv6lW5QQpY2RSMlRjgVrrmX8D8uAclTc3dEKuOeZMQJq5Z8vT VoyQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b="0+fKDG/p"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=lunn.ch Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m2-20020a056402430200b0046b13a6c40fsi5277529edc.54.2022.12.02.10.53.32; Fri, 02 Dec 2022 10:53:52 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b="0+fKDG/p"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=lunn.ch Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234039AbiLBScJ (ORCPT + 82 others); Fri, 2 Dec 2022 13:32:09 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37476 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234536AbiLBScH (ORCPT ); Fri, 2 Dec 2022 13:32:07 -0500 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 82FD8E7877; Fri, 2 Dec 2022 10:32:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=wvQ1xDmoE82XyHcjWzE7449aCw7Y023STVt3z9JJKBM=; b=0+fKDG/peW8yGj+nOx5Ta/F3Ga hpZtVtXheLMbgwgNPtHLyySm3ssFtkDql0TMug17WsbC46pwobKHMPcQdD4BSxbZ1ZKJb0ea0yRwH h2xxEy7UTm1YjpqZaHeQ0fLOd2lp0pKxG1AwfDopgP6IfrudxmrJ7McXOK57man1KGTQ=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1p1Aow-004CpA-60; Fri, 02 Dec 2022 19:31:34 +0100 Date: Fri, 2 Dec 2022 19:31:34 +0100 From: Andrew Lunn To: Michael Walle Cc: Xu Liang , Heiner Kallweit , Russell King , "David S . Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Rob Herring , Krzysztof Kozlowski , 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 Message-ID: References: <20221202151204.3318592-1-michael@walle.cc> <20221202151204.3318592-4-michael@walle.cc> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221202151204.3318592-4-michael@walle.cc> X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > --- > > 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 > + - Michael Walle > + > +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? Andrew