Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753869AbdIDO02 (ORCPT ); Mon, 4 Sep 2017 10:26:28 -0400 Received: from lb2-smtp-cloud8.xs4all.net ([194.109.24.25]:40601 "EHLO lb2-smtp-cloud8.xs4all.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753727AbdIDO01 (ORCPT ); Mon, 4 Sep 2017 10:26:27 -0400 Date: Mon, 4 Sep 2017 16:26:19 +0200 From: Antony Antony To: Maxime Ripard Cc: Antony Antony , Chen-Yu Tsai , Icenowy Zheng , linux-sunxi@googlegroups.com, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, Linux Kernel Mailing List Subject: Re: [PATCH v5] arm64: allwinner: h5: add support for NanoPi NEO Plus2 Message-ID: <20170904142619.zq4x2l2qwtpukdc7@AntonyAntony.local> References: <20170824231716.2623-1-antony@phenome.org> <20170830125057.38529-1-antony@phenome.org> <20170831145859.rief3fqo36ns23rm@flea> <20170901105313.m26y2re3ulskua43@AntonyAntony.local> <20170904082732.g2q2tjd6qlvhaea7@flea> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170904082732.g2q2tjd6qlvhaea7@flea> User-Agent: NeoMutt/20170602 (1.8.3) X-CMAE-Envelope: MS4wfKoJeF+oWocmjd6+ROr3FLkkUJIheqasNTOvFP3nbrMR3B0rIgEAiWP3+8Pr/6/9EcqhRUQZAI4uWa9VGbIGhrC8e6mnB3kpWJWzw4D9oPJ1RjKAbjmn fctY8u0kTrHxPr8OPEzaUUOcYAJGiNQGZOL3fD41k9+BLIxzQ+JXa857SgrLGJu2KsGMj6QJwiZ2lJ94kQ4JxwgNnd4ZkQSATYMpPAgF+z8H1w+TWIxgrOm8 +HZQdWmV6aPFGALo2B2v0u658gLko3BckXxzAgJAN2EfUt+F40dIAo3dr/StyU5cjm80ygy6X0uVioOkZBjUSCrFvvaJRPU2zGIYaaXyuIV3pZ78xcyz3mDj 9PR+Uh5B6O9kXXR+ZMhzx+KYDCCE6TQ38pOnSg0oXfABwwT7GdZxIvsM7iYIYpdo7xMBOxvg Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3368 Lines: 116 Hi Maxime, On Mon, Sep 04, 2017 at 10:27:32AM +0200, Maxime Ripard wrote: > On Fri, Sep 01, 2017 at 12:53:13PM +0200, Antony Antony wrote: > > > > +&emac { > > > > + pinctrl-names = "default"; > > > > + pinctrl-0 = <&emac_rgmii_pins>; > > > > + phy-supply = <®_gmac_3v3>; > > > > + phy-handle = <&ext_rgmii_phy>; > > > > + phy-mode = "rgmii"; > > > > + status = "okay"; > > > > +}; > > > > + > > > > +&mdio { > > > > + ext_rgmii_phy: ethernet-phy@7 { > > > > + compatible = "ethernet-phy-ieee802.3-c22"; > > > > + reg = <7>; > > > > + }; > > > > +}; > > > > > > This will not compile. > > > > I don't understand you, because, v5 file compiled for me. Here is output > > from running system, just the relevant part. using dtc -I fs > > /proc/device-tree > > > > ext_rgmii_phy = "/soc/ethernet@1c30000/mdio/ethernet-phy@7"; > > > > ethernet@1c30000 { > > mdio { > > .. > > ethernet-phy@7 { > > compatible = "ethernet-phy-ieee802.3-c22"; > > phandle = <0x1c>; > > reg = <0x7>; > > linux,phandle = <0x1c>; > > }; > > }; > > > > Is this what you expect? > > The bindings have been reverted recently, so if you based your work on > a version between 4.13-rc1 and 4.13-rc6 it will work, but anything > more recent will not compile anymore. I deleted emc and related node. I see. I hope stmmac: sun8i come back soon. It works well well on this board, running 4.13-rc6 > > > > + status = "okay"; > > > > + > > > > + /* > > > > + * AMPAK AP6212A WiFi module with BCM43430, rev=1 inside > > > > + * sdio vendor ID: 0x02d0, sdio device ID: 0xa9a6 > > > > + * There is no specific Documentation: dt-binding for BCM43430 > > > > + * brcm,bcm4329-fmac compatible can initialize this module > > > > + */ > > > > > > This is not really relevant. > > > > would you prefer no comment or a rewrite? How does this look? > > > > /* > > * AMPAK AP6212A WiFi module with BCM43430, rev=1 inside > > * sdio vendor ID: 0x02d0, sdio device ID: 0xa9a6 > > */ > > > > I am afraid a casual reader would think "brcm,bcm4329-fmac" is wrong, > > because that is not the actual chip inside the module. > > No comment is fine, and I'm not sure the casual reader will ever read > this :) Deleted. > > > > +&usb_otg { > > > > + dr_mode = "host"; > > > > + status = "okay"; > > > > +}; > > > > + > > > > +&usbphy { > > > > + /* USB Type-A ports' VBUS is always on */ > > > > + usb0_id_det-gpios = <&pio 6 12 GPIO_ACTIVE_HIGH>; /* PG12 */ > > > > > > If it has an ID-detect pin, then it's not a host-only USB OTG > > > controller. dr_mode should be set to otga > > > > good point. I don't see an ID-detect connected in the schematic. The > > previous generation had. > > > > I will leave > > &usb_otg { > > dr_mode = "host"; > > status = "okay"; > > }; > > > > &usbphy { > > /* USB Type-A ports' VBUS is always on */ > > status = "okay"; > > }; > > Looking at the schematics, it seems that the micro USB isn't even > wired to a bus but is only used to power the board. If so, you can > even remove the usb_otg node. Yes, the Micro USB data pins are not connected. However, it there is a second USB A port connected to the processor. If I remove &usb_otg node, in 4.13-rc6, the second port goes to disabled. BTW would this work s/brcm,bcm4329-fmac/brcm/ or should I revert it? I will send an updated version, v8, soon. thanks, -antony