From nobody Tue Feb 10 19:48:05 2026 Received: from mail63.out.titan.email (mail63.out.titan.email [34.202.218.147]) (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 B6204269CE1 for ; Thu, 25 Dec 2025 07:36:48 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=34.202.218.147 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766648211; cv=none; b=THmRywL+ruzBqg6/6UxWWYTqG8+oYqF8Jxe1lYhRoS++oJQ+guqfzgFTnG1BioNHfkCVtz8Ib3mrQJSu1kEPHt0g5go3vWuGqhxz4JjVL0dCsJxkBRrgIkRRHlEhnUr0g9QJ1grrst1QgUoyiy+HBmD3LSBmjiBRYLu9zMsN5+g= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766648211; c=relaxed/simple; bh=vJsXWI0fYsWoc0Z/xAAKyK+Q7tFUD345MbtJ/RwQvn4=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=BwcF/sjq9xxRjPBLO/kYk8bwfAH+hB6EsTjCwL89w0VNWasyrQG+2s6SXVORSML8VWWqtNgdA87PXbeHhcp+6W0A/7e0YJOLafi4AjZlz5kNmrWPQ6mUUrFnA7E5EU2e52AP7p/ZSgT9YTJU8zkwCNPB2yNTkLu5T8KJ+M7m49E= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=ziyao.cc; spf=pass smtp.mailfrom=ziyao.cc; dkim=pass (1024-bit key) header.d=ziyao.cc header.i=@ziyao.cc header.b=BIoRQVjO; arc=none smtp.client-ip=34.202.218.147 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=ziyao.cc Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=ziyao.cc Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=ziyao.cc header.i=@ziyao.cc header.b="BIoRQVjO" Received: from localhost (localhost [127.0.0.1]) by smtp-out.flockmail.com (Postfix) with ESMTP id 4dcKrW1Wycz7t9Q; Thu, 25 Dec 2025 07:19:55 +0000 (UTC) DKIM-Signature: a=rsa-sha256; bh=a7mwss2zUTWHrGu/W0jn+kAqkcl4B3JbKYGDTqhMoKE=; c=relaxed/relaxed; d=ziyao.cc; h=message-id:in-reply-to:references:mime-version:from:cc:to:subject:date:from:to:cc:subject:date:message-id:in-reply-to:references:reply-to; q=dns/txt; s=titan1; t=1766647195; v=1; b=BIoRQVjOukSUr8uDpgeXbHrgDwlpEDvHHmQN8Z+oqnDdEghudcujFBOphGF6arq3Ad+vUnjC THuWAfTjWtp3TnW/Ilh/Ye1Py9YW7AH2QoyiOa69HwbI0BORKIeclAWiy75dRAjDw/WnKu54LYI KtZg2uYw0nloa5dkO5ty+Kz4= Received: from ketchup (unknown [117.171.66.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp-out.flockmail.com (Postfix) with ESMTPSA id 4dcKrP5V87z7t9N; Thu, 25 Dec 2025 07:19:49 +0000 (UTC) Feedback-ID: :me@ziyao.cc:ziyao.cc:flockmailId From: Yao Zi To: Andrew Lunn , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Frank , Heiner Kallweit , Russell King , "Russell King (Oracle)" , Vladimir Oltean , Choong Yong Liang , Chen-Yu Tsai , Jisheng Zhang , Furong Xu <0x1207@gmail.com> Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, Mingcong Bai , Kexy Biscuit , Yao Zi Subject: [RFC PATCH net-next v5 1/3] net: phy: motorcomm: Support YT8531S PHY in YT6801 Ethernet controller Date: Thu, 25 Dec 2025 07:19:12 +0000 Message-ID: <20251225071914.1903-2-me@ziyao.cc> X-Mailer: git-send-email 2.51.2 In-Reply-To: <20251225071914.1903-1-me@ziyao.cc> References: <20251225071914.1903-1-me@ziyao.cc> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-F-Verdict: SPFVALID X-Titan-Src-Out: 1766647195062456277.30087.168411733287155282@prod-use1-smtp-out1002. X-CMAE-Score: 0 X-CMAE-Analysis: v=2.4 cv=WtDRMcfv c=1 sm=1 tr=0 ts=694ce59b a=rBp+3XZz9uO5KTvnfbZ58A==:117 a=rBp+3XZz9uO5KTvnfbZ58A==:17 a=MKtGQD3n3ToA:10 a=1oJP67jkp3AA:10 a=CEWIc4RMnpUA:10 a=VwQbUJbxAAAA:8 a=NfpvoiIcAAAA:8 a=0_qlMWoZVofwMTi4AHUA:9 a=HwjPHhrhEcEjrsLHunKI:22 a=3z85VNIBY5UIEeAh_hcH:22 a=NWVoK91CQySWRX1oVYDe:22 Content-Type: text/plain; charset="utf-8" YT6801's internal PHY is confirmed as a GMII-capable variant of YT8531S by a previous series[1] and reading PHY ID. Add support for PHY_INTERFACE_MODE_GMII for YT8531S to allow the Ethernet driver to reuse the PHY code for its internal PHY. Link: https://lore.kernel.org/all/a48d76ac-db08-46d5-9528-f046a7b541dc@moto= r-comm.com/ # [1] Co-developed-by: Frank Sae Signed-off-by: Frank Sae Signed-off-by: Yao Zi Reviewed-by: Andrew Lunn --- drivers/net/phy/motorcomm.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/drivers/net/phy/motorcomm.c b/drivers/net/phy/motorcomm.c index 89b5b19a9bd2..dc9569a39cb4 100644 --- a/drivers/net/phy/motorcomm.c +++ b/drivers/net/phy/motorcomm.c @@ -910,6 +910,10 @@ static int ytphy_rgmii_clk_delay_config(struct phy_dev= ice *phydev) val |=3D FIELD_PREP(YT8521_RC1R_RX_DELAY_MASK, rx_reg) | FIELD_PREP(YT8521_RC1R_GE_TX_DELAY_MASK, tx_reg); break; + case PHY_INTERFACE_MODE_GMII: + if (phydev->drv->phy_id !=3D PHY_ID_YT8531S) + return -EOPNOTSUPP; + return 0; default: /* do not support other modes */ return -EOPNOTSUPP; } --=20 2.51.2