linux-kernel - RE: [Intel-wired-lan] [PATCH net-next v5 2/9] dpll: zl3073x: Associate pin with fwnode handle

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <LV4PR11MB94913C3EABBD02E6DFFD0B679B99A@LV4PR11MB9491.namprd11.prod.outlook.com>
Date: Thu, 5 Feb 2026 09:19:27 +0000
From: "Kubalewski, Arkadiusz" <arkadiusz.kubalewski@...el.com>
To: "Vecera, Ivan" <ivecera@...hat.com>, "netdev@...r.kernel.org"
	<netdev@...r.kernel.org>
CC: "Loktionov, Aleksandr" <aleksandr.loktionov@...el.com>, "Lobakin,
 Aleksander" <aleksander.lobakin@...el.com>, Andrew Lunn
	<andrew+netdev@...n.ch>, "David S. Miller" <davem@...emloft.net>, "Eric
 Dumazet" <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Jiri Pirko
	<jiri@...nulli.us>, Jonathan Lemon <jonathan.lemon@...il.com>, "Leon
 Romanovsky" <leon@...nel.org>, Mark Bloch <mbloch@...dia.com>, Paolo Abeni
	<pabeni@...hat.com>, Prathosh Satish <Prathosh.Satish@...rochip.com>,
	"Kitszel, Przemyslaw" <przemyslaw.kitszel@...el.com>, Richard Cochran
	<richardcochran@...il.com>, Saeed Mahameed <saeedm@...dia.com>, Tariq Toukan
	<tariqt@...dia.com>, "Nguyen, Anthony L" <anthony.l.nguyen@...el.com>, "Vadim
 Fedorenko" <vadim.fedorenko@...ux.dev>, "intel-wired-lan@...ts.osuosl.org"
	<intel-wired-lan@...ts.osuosl.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "linux-rdma@...r.kernel.org"
	<linux-rdma@...r.kernel.org>
Subject: RE: [Intel-wired-lan] [PATCH net-next v5 2/9] dpll: zl3073x:
 Associate pin with fwnode handle

>From: Intel-wired-lan <intel-wired-lan-bounces@...osl.org> On Behalf Of
>Ivan Vecera
>Sent: Tuesday, February 3, 2026 6:40 PM
>
>Associate the registered DPLL pin with its firmware node by calling
>dpll_pin_fwnode_set().
>
>This links the created pin object to its corresponding DT/ACPI node
>in the DPLL core. Consequently, this enables consumer drivers (such as
>network drivers) to locate and request this specific pin using the
>fwnode_dpll_pin_find() helper.
>
>Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@...el.com>

LGTM,
Reviewed-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>

>Signed-off-by: Ivan Vecera <ivecera@...hat.com>
>---
> drivers/dpll/zl3073x/dpll.c | 1 +
> 1 file changed, 1 insertion(+)
>
>diff --git a/drivers/dpll/zl3073x/dpll.c b/drivers/dpll/zl3073x/dpll.c
>index 7d8ed948b9706..9eed21088adac 100644
>--- a/drivers/dpll/zl3073x/dpll.c
>+++ b/drivers/dpll/zl3073x/dpll.c
>@@ -1485,6 +1485,7 @@ zl3073x_dpll_pin_register(struct zl3073x_dpll_pin
>*pin, u32 index)
> 		rc = PTR_ERR(pin->dpll_pin);
> 		goto err_pin_get;
> 	}
>+	dpll_pin_fwnode_set(pin->dpll_pin, props->fwnode);
>
> 	if (zl3073x_dpll_is_input_pin(pin))
> 		ops = &zl3073x_dpll_input_pin_ops;
>--
>2.52.0