From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.1 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 73A71C31E74 for ; Mon, 10 Jun 2019 14:31:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 3F50A207E0 for ; Mon, 10 Jun 2019 14:31:52 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b="m06qR7H0" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2403907AbfFJObv (ORCPT ); Mon, 10 Jun 2019 10:31:51 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:41730 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2403864AbfFJObu (ORCPT ); Mon, 10 Jun 2019 10:31:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=JRYueMLRQECogmZaB6ntHx4NwLFSr0m7XU9IdQBzel4=; b=m06qR7H0rnzOHJEwWUJ9aqNCao yHKplEn/FE3sVKF8/vKlMlQq8dwQiN+HnzaDdA17NCQ6HIftnvxJAonp8myb6r9qOI0EY0bhzEx8S cBOeIg3pl/zsC8/rW8TJMUcf1A7TMYAWVagSWhyTJUV1ElJpgOzXe+VGBh2nXURittk8=; Received: from andrew by vps0.lunn.ch with local (Exim 4.89) (envelope-from ) id 1haLKl-0007g3-EW; Mon, 10 Jun 2019 16:31:39 +0200 Date: Mon, 10 Jun 2019 16:31:39 +0200 From: Andrew Lunn To: Maxime Ripard Cc: Mark Rutland , Rob Herring , Frank Rowand , "David S . Miller" , Chen-Yu Tsai , Maxime Coquelin , Alexandre Torgue , netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, Maxime Chevallier , Antoine =?iso-8859-1?Q?T=E9nart?= , Florian Fainelli , Heiner Kallweit Subject: Re: [PATCH v2 05/11] dt-bindings: net: sun4i-emac: Convert the binding to a schemas Message-ID: <20190610143139.GG28724@lunn.ch> References: <91618c7e9a5497462afa74c6d8a947f709f54331.1560158667.git-series.maxime.ripard@bootlin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org > +required: > + - compatible > + - reg > + - interrupts > + - clocks > + - phy > + - allwinner,sram Quoting ethernet.txt: - phy: the same as "phy-handle" property, not recommended for new bindings. - phy-handle: phandle, specifies a reference to a node representing a PHY device; this property is described in the Devicetree Specification and so preferred; Can this be expressed in Yaml? Accept phy, but give a warning. Accept phy-handle without a warning? Enforce that one or the other is present? Thanks Andrew