From nobody Thu Mar 5 06:32:15 2026 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 DD33A2D1F7B; Mon, 16 Feb 2026 17:13:20 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771262000; cv=none; b=Fq3xSS0I9LL/GsW5Lsv/bckSVVnz2zbgikFgnKnGl/QpUm515yViKutVFyXkJSGZ0UKNrujUOhtIAFdbUV73Yse+8ICM2SMq1MIkOZuL2IEDgIHfBWGnKPfevIHBlIFAMDH+iVE4dswL/bR+C8wLCb2X1PKe0t3cHdobUnCQHP4= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771262000; c=relaxed/simple; bh=wwNjpAxLnbWXj2x/gojmm+AaV5qKGG7+RSBh/gjAdOA=; h=From:Date:Subject:MIME-Version:Content-Type:Message-Id:To:Cc; b=vEdPYrmRR89Fwubfpy6B1LgbcRgJl28LNp+e6RQo4z71wUbJ1KDrW+q2Jxe9JE+esd01m4PJmQorCcen/7DiQADZQMTBdiWNi6YzDv2J2MuFUK3GBCj4tVenXzJOwltpkzUnMepi+gCHwY2emJs/NmFfjH49YgWJs6E+tcw+4eg= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=QHQ3DFdq; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="QHQ3DFdq" Received: by smtp.kernel.org (Postfix) with ESMTPS id 7E48EC116C6; Mon, 16 Feb 2026 17:13:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1771262000; bh=wwNjpAxLnbWXj2x/gojmm+AaV5qKGG7+RSBh/gjAdOA=; h=From:Date:Subject:To:Cc:Reply-To:From; b=QHQ3DFdqL2DPGRDBjFNQmai8V4mCdE3oBhf1i3UDoiA5EYpbWvu/OcB37Zakonxub emKz8mKQpJoMPTImApm48tvr6hN8OPsGYzNwLSMR7A4jch6Y7u3C3eKkc7NXDE1PHp uefi+KTqZcM9cFWiPVUWXrKr3YQWZGBchDKjuwBsKLZhciRw8xpaanwJg1tGEUi0m6 SPbHxvbvPoERdAQjZvY2HPgYx3NWKMu8lknc9S7Mz5mvOHt270Xzi7Avi1yA42ouWY NnESqfa4o0+0Yyl8jrfsTNZE+L+bR6xERivymPmHSLIlykUgIk59U5P5oa0g6ZsEis JMjvTsi0tYFEQ== Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6FA38E81A5A; Mon, 16 Feb 2026 17:13:20 +0000 (UTC) From: =?utf-8?q?Kry=C5=A1tof_=C4=8Cern=C3=BD_via_B4_Relay?= Date: Mon, 16 Feb 2026 18:11:09 +0100 Subject: [PATCH] net: phy: realtek: Add support for PHY LEDs on RTL8211F-VD Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <20260216-rtl8211fvd-add-leds-v1-1-a2b8617bbf80@gmail.com> X-B4-Tracking: v=1; b=H4sIAKxPk2kC/x3MzQpAUBBA4VfRrE2ZKePnVWQhM5gSuldS8u5ul t/inAeiBbcIbfZAsMuj71sC5RmMy7DNhq7JwAVLwSQYzrVmoulSHFRxNY1YsZUqItYwQSqPYJP f/7Xr3/cDklKhhGUAAAA= X-Change-ID: 20260216-rtl8211fvd-add-leds-72e5d666e921 To: Andrew Lunn , Heiner Kallweit , Russell King , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni Cc: Miroslav Ondra , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, =?utf-8?q?Kry=C5=A1tof_=C4=8Cern=C3=BD?= X-Mailer: b4 0.14.3 X-Developer-Signature: v=1; a=ed25519-sha256; t=1771261999; l=1456; i=cleverline1mc@gmail.com; s=20241112; h=from:subject:message-id; bh=UcDBB6aqn6VGJO+wrWmfuuDhMbNI+KYuwnnokfwejMY=; b=q1iiWNCuapGkYpnUzMCoonZHxYfGwV7ZC8l5ct9AzwknkjTQeTtkfca2avgxpzrlskW2I1AJX nCj+z1JNK7pDiX4V65P3N8Mj6sOv/RxpPodcdDwYM/UoPRdy5n6coGV X-Developer-Key: i=cleverline1mc@gmail.com; a=ed25519; pk=EJoEbw03UiRORQuCiEyNA8gH1Q6fIpEWnn/MyaWOWX0= X-Endpoint-Received: by B4 Relay for cleverline1mc@gmail.com/20241112 with auth_id=275 X-Original-From: =?utf-8?q?Kry=C5=A1tof_=C4=8Cern=C3=BD?= Reply-To: cleverline1mc@gmail.com From: Kry=C5=A1tof =C4=8Cern=C3=BD Realtek RTL8211F-VD has the same LED configuration and registers as RTL8211F. Use the existing LED related functions for this chip, so it is possible to also use the netdev trigger. Tested on ROCK Pi E. Signed-off-by: Kry=C5=A1tof =C4=8Cern=C3=BD Reviewed-by: Andrew Lunn --- I have been trying to match LED behavior of RTL8211F-VD with RTL8211E and found out the RTL8211F is supported already, which by the look in datasheet matched the RTL8211F-VD. So I have reused the functions and tested on ROCK Pi E. --- drivers/net/phy/realtek/realtek_main.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/net/phy/realtek/realtek_main.c b/drivers/net/phy/realt= ek/realtek_main.c index 75565fbdbf6d..530b4e26d16e 100644 --- a/drivers/net/phy/realtek/realtek_main.c +++ b/drivers/net/phy/realtek/realtek_main.c @@ -2243,6 +2243,9 @@ static struct phy_driver realtek_drvs[] =3D { .read_page =3D rtl821x_read_page, .write_page =3D rtl821x_write_page, .flags =3D PHY_ALWAYS_CALL_SUSPEND, + .led_hw_is_supported =3D rtl8211x_led_hw_is_supported, + .led_hw_control_get =3D rtl8211f_led_hw_control_get, + .led_hw_control_set =3D rtl8211f_led_hw_control_set, }, { .name =3D "Generic FE-GE Realtek PHY", .match_phy_device =3D rtlgen_match_phy_device, --- base-commit: 350adaf7fde9fdbd9aeed6d442a9ae90c6a3ab97 change-id: 20260216-rtl8211fvd-add-leds-72e5d666e921 Best regards, --=20 Kry=C5=A1tof =C4=8Cern=C3=BD