From: Ivan Vecera <ivecera@redhat.com>
To: netdev@vger.kernel.org
Cc: Aleksandr Loktionov <aleksandr.loktionov@intel.com>,
Alexander Lobakin <aleksander.lobakin@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Jiri Pirko <jiri@resnulli.us>,
Jonathan Lemon <jonathan.lemon@gmail.com>,
Leon Romanovsky <leon@kernel.org>, Mark Bloch <mbloch@nvidia.com>,
Paolo Abeni <pabeni@redhat.com>,
Prathosh Satish <Prathosh.Satish@microchip.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Richard Cochran <richardcochran@gmail.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
intel-wired-lan@lists.osuosl.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: [PATCH net-next v3 2/9] dpll: zl3073x: Associate pin with fwnode handle
Date: Fri, 30 Jan 2026 17:53:31 +0100 [thread overview]
Message-ID: <20260130165338.101860-3-ivecera@redhat.com> (raw)
In-Reply-To: <20260130165338.101860-1-ivecera@redhat.com>
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@intel.com>
Signed-off-by: Ivan Vecera <ivecera@redhat.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
next prev parent reply other threads:[~2026-01-30 16:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 16:53 [PATCH net-next v3 0/9] dpll: Core improvements and ice E825-C SyncE support Ivan Vecera
2026-01-30 16:53 ` [PATCH net-next v3 1/9] dpll: Allow associating dpll pin with a firmware node Ivan Vecera
2026-01-30 17:50 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-01-30 16:53 ` Ivan Vecera [this message]
2026-01-30 16:53 ` [PATCH net-next v3 3/9] dpll: Add notifier chain for dpll events Ivan Vecera
2026-01-30 16:53 ` [PATCH net-next v3 4/9] dpll: Support dynamic pin index allocation Ivan Vecera
2026-01-30 17:50 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-01-30 16:53 ` [PATCH net-next v3 5/9] dpll: zl3073x: Add support for mux pin type Ivan Vecera
2026-01-30 16:53 ` [PATCH net-next v3 6/9] dpll: Enhance and consolidate reference counting logic Ivan Vecera
2026-01-30 17:51 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-01-30 16:53 ` [PATCH net-next v3 7/9] dpll: Add reference count tracking support Ivan Vecera
2026-01-30 17:52 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-01-30 16:53 ` [PATCH net-next v3 8/9] drivers: Add support for DPLL reference count tracking Ivan Vecera
2026-01-30 17:52 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-01-30 16:53 ` [PATCH net-next v3 9/9] ice: dpll: Support E825-C SyncE and dynamic pin discovery Ivan Vecera
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260130165338.101860-3-ivecera@redhat.com \
--to=ivecera@redhat.com \
--cc=Prathosh.Satish@microchip.com \
--cc=aleksander.lobakin@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jiri@resnulli.us \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=richardcochran@gmail.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=vadim.fedorenko@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox