From: Ivan Vecera <ivecera@redhat.com>
To: Andrew Lunn <andrew@lunn.ch>, Jiri Pirko <jiri@resnulli.us>
Cc: Rob Herring <robh@kernel.org>,
netdev@vger.kernel.org, mschmidt@redhat.com, poros@redhat.com,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Jiri Pirko <jiri@resnulli.us>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Prathosh Satish <Prathosh.Satish@microchip.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH net-next] dt-bindings: dpll: Add per-channel Ethernet reference property
Date: Wed, 10 Sep 2025 14:51:33 +0200 [thread overview]
Message-ID: <dcca9d10-b2b7-4534-abe6-999a9013a8e9@redhat.com> (raw)
In-Reply-To: <350cecaf-9e41-4c34-8bc0-4b1c93b0ddfe@lunn.ch>
On 09. 09. 25 3:50 odp., Andrew Lunn wrote:
>>>> Yesterday I was considering the implementation from the DPLL driver's
>>>> perspective and encountered a problem when the relation is defined from
>>>> the Ethernet controller's perspective. In that case, it would be
>>>> necessary to enumerate all devices that contain a “dpll” property whose
>>>> value references this DPLL device.
>>>
>>> Why is that?
>>
>> Because the DPLL driver has to find a mac-address of the ethernet
>> controller to generate clock identity that is used for DPLL device
>> registration.
>
> Maybe this API is the wrong way around? Maybe what you want is that
> the MAC driver says to the DPLL driver: hey, you are my clock
> provider, here is an ID to use, please start providing me a clock?
Yes, this could be fine but there is a problem because clock id is part
of DPLL device and pins registration and it is not possible to change
the clock id without full de-re-registration. I have provided in zl3073x
a user to change the clock id via devlink but it means that the driver
has to unregister all dpll devices and pins and register them under
different clock id.
> So it is the MAC driver which will follow the phandle, and then make a
> call to bind the dpll to the MAC, and then provide it with the ID?
In fact that would be enough to expose from the DPLL core a function
to change clock id of the existing DPLL devices.
E.g.
int dpll_clock_id_change(struct module *module, u64 clock_id,
u64 new_clock_id)
{
struct dpll_device *dpll_pos;
struct dpll_pin *pin_pos;
unsigned long i;
mutex_lock(&dpll_lock);
/* Change clock_id of all devices registered by given module
* with given clock_id.
*/
xa_for_each(&dpll_device_xa, i, dpll_pos) {
if (dpll->clock_id == clock_id &&
dpll->module == module)
dpll_pos->clock_id = new_clock_id;
}
}
/* Change clock_id of all pins registered by given module
* with given clock_id.
*/
xa_for_each(&dpll_pin_xa, i, pos) {
if (pin_pos->clock_id == clock_id &&
pin_pos->module == module) {
pos->clock_id = new_clock_id;
}
}
mutex_unlock(&dpll_lock);
}
With this, the standalone DPLL driver can register devices and pins with
arbitrary clock_id and then the MAC driver can change it.
Thoughts?
Thanks,
Ivan
next prev parent reply other threads:[~2025-09-10 12:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 14:47 Ivan Vecera
2025-08-15 23:21 ` Andrew Lunn
2025-08-20 21:13 ` Rob Herring
2025-08-29 13:29 ` Ivan Vecera
2025-09-04 14:43 ` Ivan Vecera
2025-09-04 22:06 ` Rob Herring
2025-09-05 6:50 ` Ivan Vecera
2025-09-08 22:49 ` Rob Herring
2025-09-09 12:50 ` Ivan Vecera
2025-09-09 13:50 ` Andrew Lunn
2025-09-10 12:51 ` Ivan Vecera [this message]
2025-09-16 9:31 ` Jiri Pirko
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=dcca9d10-b2b7-4534-abe6-999a9013a8e9@redhat.com \
--to=ivecera@redhat.com \
--cc=Prathosh.Satish@microchip.com \
--cc=andrew@lunn.ch \
--cc=arkadiusz.kubalewski@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jiri@resnulli.us \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=poros@redhat.com \
--cc=robh@kernel.org \
--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
all inboxes | Powered by JetHome®