From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 93D0A386422; Mon, 3 Aug 2026 13:01:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=156.67.10.101 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785762112; cv=none; b=Rvy+RVrREqJjGLwRpeWQTC05Uk5CY9m0PV4mPQjusB239tswrG2ks+co4FK2J0GyOsD0nrqcwKrXwaNYBPcKL8zm58MvFkFtK+2+lxZ+RdZ16Itf7t3MsEB+8S1SDmhvTVWHAEcAHlf8Fp1C4bW07QUk0XvVXPiu3Z9PgcTpoqI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785762112; c=relaxed/simple; bh=ulfl3/X5f/LYXJvwrI7YEnXUirLbSE8K+L7KYNiv+rQ=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=jEHjNM0nZsaMPIdJ4RewiMRwhjFiRyOXn1C1RSlId4Ux4LNXHeRLyNrXWB4htgZBdfsRunvVNc7uwzJau8/PrKmmqdi+0JvWFLrRU2R72yCtqPwE/MQviVwqXlLJQ7bnnjLYqa5RkddkIcrXBFBi2Yo7rbiGU0WQHGTvKB0YNxM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch; spf=pass smtp.mailfrom=lunn.ch; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b=44VXgAvS; arc=none smtp.client-ip=156.67.10.101 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lunn.ch Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b="44VXgAvS" 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=hRXn5kzc97BQTjib/Wj0YW5AbHYZrqSl7Di4vozL+yk=; b=44VXgAvShSfyUZOOhHGJmb8U/1 knBdqbXRkyUJrsKE6mh5V36V9fJJDComtnWDbSenQ4KQWk+FQw8sQnu+MFJaIVdN3vAkOphjPptWN 7SVc+xjX5VaRedewLqN/xtp6VqFOVwiPgkFYuXrUmBQwoFPonWcRio1yCqS4ybSaQxHk=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1wqsIN-00Fixe-Bi; Mon, 03 Aug 2026 15:01:31 +0200 Date: Mon, 3 Aug 2026 15:01:31 +0200 From: Andrew Lunn To: James Hilliard Cc: Andrew Lunn , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Chen-Yu Tsai , Jernej Skrabec , Samuel Holland , Andre Przywara , Richard Genoud , Maxime Ripard , Alexandre Torgue , Giuseppe Cavallaro , Jose Abreu , Maxime Chevallier , Maxime Coquelin , Heiner Kallweit , Russell King , Saravana Kannan , Lee Jones , Heiko Stuebner , netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, mfd@lists.linux.dev, linux-rockchip@lists.infradead.org Subject: Re: [PATCH 00/21] net: phy: add X-Powers AC200/AC300 EPHY support Message-ID: <8088f2b1-1fd9-4acc-b9f4-8bfbaa2bd28a@lunn.ch> References: <20260802-submit-acx00-of-dynamic-v1-v1-0-0a53cd9e21cc@gmail.com> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260802-submit-acx00-of-dynamic-v1-v1-0-0a53cd9e21cc@gmail.com> On Sun, Aug 02, 2026 at 11:14:10PM -0600, James Hilliard wrote: > The Allwinner H616/H618 secondary EMAC is commonly connected to a Fast > Ethernet PHY in an X-Powers AC200 or AC300 companion package. The two > packages expose the same link PHY ID and largely compatible link-side > registers, but require different control paths before those registers can > be accessed: AC200 is initialized through its I2C MFD, while AC300 uses a > non-PHY Clause 22 control endpoint. > > Some H616-family products were shipped with either package under the same > board identity. For those systems, this series uses a SID NVMEM field to > select the control provider at run time. With CONFIG_OF_DYNAMIC, the link > PHY enables only the selected fail-needs-probe provider, so an AC300 board > does not probe the unused AC200 I2C controller or claim its pins. The same > drivers also support fixed descriptions without CONFIG_OF_DYNAMIC: a board > can reference one enabled provider, or enable both candidates when runtime > selection is still required. > > The series adds: > > - the H616 EMAC1 binding, stmmac variant and controller node; > - generic MDIO OF reconfiguration support for PHYs, packages, scanned > addresses and generic MDIO devices; > - the AC200 MFD and AC200/AC300 EPHY control providers; > - the shared AC200/AC300 link-PHY driver, including calibration, power and > reset sequencing, MDI/MDI-X, statistics, EDPD, PHY-managed EEE, package > LEDs, interrupts and Wake-on-LAN; and > - H6 and H616-family device-tree descriptions and arm64 defconfig support. > > The AC200 and AC300 control and link paths were exercised on H616-family > hardware during development, including link traffic, address handling, > ethtool EDPD/EEE controls, statistics and LEDs. The H6 interrupt and > Wake-on-LAN description still needs validation by an H6 hardware user. > > This series depends on Richard Genoud's v7 H616 PWM controller series, > which provides the bypass clock used by the companion EPHY: > > https://lore.kernel.org/all/20260703152215.192859-1-richard.genoud@bootlin.com/ > > The PWM patches are an external prerequisite and are intentionally not > included in this 21-patch series. 21 patches is on the big side. Now you have shown the big picture, can you break this up into a couple of series? Andrew