From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from esa.microchip.iphmx.com (esa.microchip.iphmx.com [68.232.153.233]) (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 CEFD131690A; Thu, 2 Apr 2026 13:13:40 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=68.232.153.233 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775135622; cv=none; b=itEM9HX0K9jl/tkS2aJ3+aj5ogp7cG+MYtCrwE4L1t9ARpf2fE7+6ON7njn6dCgMQCOytm6RGObFH/qRqjsPkrStVbgpwtNAMMv6aAxALSrPKQ7oCvhpj7AelhYkARj5hBzHvkOl0SHiquL8w2DxDm4tCdAWh8nsdt3L7pY7BFY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775135622; c=relaxed/simple; bh=C2KY7sy/BojAlYbuWIeT4FOySSmwKdjjEEo4+Jx0PSQ=; h=From:To:CC:Subject:Date:Message-ID:MIME-Version:Content-Type; b=OFEx6hiYeRzHtIyT+ZEd59nXe09bfIy+SbqOz0JpwMhci+pGQ+wPwzc9cz0pUXkxcXiRYE6hvuIUTjn4c3GQFQfKu3KGM8dH0LM6bMrr6Ana7yHVTzkdJ19t2PYThYB+boaI8JhRsBIQWxpHh8Y0kM06dQKSjcxbaQAFyopysS0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=microchip.com; spf=pass smtp.mailfrom=microchip.com; dkim=pass (2048-bit key) header.d=microchip.com header.i=@microchip.com header.b=T//vQhcj; arc=none smtp.client-ip=68.232.153.233 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=microchip.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=microchip.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=microchip.com header.i=@microchip.com header.b="T//vQhcj" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=microchip.com; i=@microchip.com; q=dns/txt; s=mchp; t=1775135621; x=1806671621; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=C2KY7sy/BojAlYbuWIeT4FOySSmwKdjjEEo4+Jx0PSQ=; b=T//vQhcjM13s7ybSevf+Rhvc3YNHwVU2+gkW1DlWpgTRDPd8CZqa99G3 MStvLTZhlqNBDFVCTUXSsIJY0LsV38swUuqbeVRu/QdAOGjqNO5VeOL3s QgKPjKespfi7IWRpfDJL/qIuXKOqsygNGOoMtSgVHkj5rBkMHWBloLPvQ qIy7r85FOzaLo3dRxiZIiQIYuoAEieQLtvIKwrSmvOvSM0Vs/hbX0jUqp KTAGt4F2IBBZx/Bs3XRjv3wlvSIochlBz5yI4/ydcav5/XuuvY8sjAsfE iyR2tOlfP4vwGrqkVDRw9cA+fdJINyD5/1ZNBJSWDKfye1dJWXUCq6+Ii Q==; X-CSE-ConnectionGUID: DSzgFxBLReScRspQAdm+CQ== X-CSE-MsgGUID: qccmT4tXQ0WnJLRmxcHZIw== X-IronPort-AV: E=Sophos;i="6.23,155,1770620400"; d="scan'208";a="55583661" X-Amp-Result: SKIPPED(no attachment in message) Received: from unknown (HELO email.microchip.com) ([170.129.1.10]) by esa3.microchip.iphmx.com with ESMTP/TLS/ECDHE-RSA-AES128-GCM-SHA256; 02 Apr 2026 06:13:34 -0700 Received: from chn-vm-ex03.mchp-main.com (10.10.85.151) by chn-vm-ex04.mchp-main.com (10.10.85.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.58; Thu, 2 Apr 2026 06:13:02 -0700 Received: from bby-cbu-swbuild03.eng.microchip.com (10.10.85.11) by chn-vm-ex03.mchp-main.com (10.10.85.151) with Microsoft SMTP Server id 15.1.2507.58 via Frontend Transport; Thu, 2 Apr 2026 06:13:01 -0700 From: Charles Perry To: CC: Charles Perry , Andrew Lunn , "David S. Miller" , "Eric Dumazet" , Jakub Kicinski , Paolo Abeni , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Heiner Kallweit , Russell King , Subject: [PATCH net-next v4 0/3] Add support for PIC64-HPSC/HX MDIO controller Date: Thu, 2 Apr 2026 06:12:21 -0700 Message-ID: <20260402131229.319599-1-charles.perry@microchip.com> X-Mailer: git-send-email 2.47.3 Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain Hello, This series adds a driver for the two MDIO controllers of PIC64-HPSC/HX. The hardware supports C22 and C45 but only C22 is implemented for now. This MDIO hardware is based on a Microsemi design supported in Linux by mdio-mscc-miim.c. However, The register interface is completely different with pic64hpsc, hence the need for a separate driver. The documentation recommends an input clock of 156.25MHz and a prescaler of 39, which yields an MDIO clock of 1.95MHz. This was tested on Microchip HB1301 evalkit which has a VSC8574 and a VSC8541 with clock frequencies of 0.6, 1.95 and 2.5 MHz. This series also adds a PHY write barrier when disabling PHY interrupts as discussed in [1]. Thanks, Charles [1]: https://lore.kernel.org/all/acvUqDgepCIScs8M@shell.armlinux.org.uk/ Changes in v4: - 3/3: Add the PHY barrier patch (Russell, Andrew) - 2/3: return FIELD_GET() directly instead of using "ret" (Russell) Changes in v3: - 2/2: Add a MAINTAINERS entry (Jakub) Changes in v2: - 1/2: Make "clocks" and "interrupts" required (Andrew) - 1/2: Add a default value to "clock-frequency" (Andrew) - 2/2: Remove #define for unused registers (Maxime) - 2/2: Add "c22" to clause 22 read/write ops (Maxime) - 2/2: Remove the call to platform_set_drvdata() (Andrew) - 2/2: Make the clock mandatory (Andrew) - 2/2: Use 2.5MHz if no clock-frequency was specified (Andrew) - 2/2: Change the error message for bad clock-frequency (Andrew) - 2/2: Fix a use without initialization on bus_freq (Andrew) CC: Andrew Lunn CC: "David S. Miller" CC: Eric Dumazet CC: Jakub Kicinski CC: Paolo Abeni CC: Rob Herring CC: Krzysztof Kozlowski CC: Conor Dooley CC: Heiner Kallweit CC: Russell King CC: netdev@vger.kernel.org CC: devicetree@vger.kernel.org Charles Perry (3): dt-bindings: net: document Microchip PIC64-HPSC/HX MDIO controller net: mdio: add a driver for PIC64-HPSC/HX MDIO controller net: phy: add a PHY write barrier when disabling interrupts .../net/microchip,pic64hpsc-mdio.yaml | 68 +++++++ MAINTAINERS | 6 + drivers/net/mdio/Kconfig | 7 + drivers/net/mdio/Makefile | 1 + drivers/net/mdio/mdio-pic64hpsc.c | 190 ++++++++++++++++++ drivers/net/phy/phy.c | 27 ++- 6 files changed, 298 insertions(+), 1 deletion(-) create mode 100644 Documentation/devicetree/bindings/net/microchip,pic64hpsc-mdio.yaml create mode 100644 drivers/net/mdio/mdio-pic64hpsc.c -- 2.47.3