From: Ivan Vecera <ivecera@redhat.com>
To: netdev@vger.kernel.org
Cc: Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Jiri Pirko <jiri@resnulli.us>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Prathosh Satish <Prathosh.Satish@microchip.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Michal Schmidt <mschmidt@redhat.com>,
Petr Oros <poros@redhat.com>
Subject: [PATCH net-next 0/2] dpll: zl3073x: Read clock ID from device property
Date: Thu, 17 Jul 2025 19:10:58 +0200 [thread overview]
Message-ID: <20250717171100.2245998-1-ivecera@redhat.com> (raw)
The current ZL3073x firmware revisions do not provide any information
unique for the particular chip that could be use to generate clock ID
necessary for a DPLL device registration.
Currently the driver generates random clock ID during probe and a user
have and option to change this value using devlink interface.
The situation is very similar to network controllers that do not have
assigned a fixed MAC address.
The purpose of this series is to allow to specify the clock ID property
through DT. If the property is not provided then the driver will use
randomly generated value as fallback.
Patch breakdown:
Patch 1 - adds clock-id property to dpll-device DT schema
Patch 2 - adds support for this DT property in zl3073x driver
Ivan Vecera (2):
dt-bindings: dpll: Add clock ID property
dpll: zl3073x: Initialize clock ID from device property
.../devicetree/bindings/dpll/dpll-device.yaml | 5 +++
drivers/dpll/zl3073x/core.c | 32 ++++++++++++++++---
2 files changed, 32 insertions(+), 5 deletions(-)
--
2.49.1
next reply other threads:[~2025-07-17 17:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 17:10 Ivan Vecera [this message]
2025-07-17 17:10 ` [PATCH net-next 1/2] dt-bindings: dpll: Add clock ID property Ivan Vecera
2025-07-18 6:55 ` Krzysztof Kozlowski
2025-07-18 12:16 ` Ivan Vecera
2025-07-21 9:23 ` Krzysztof Kozlowski
2025-07-21 12:54 ` Ivan Vecera
2025-07-23 6:25 ` Krzysztof Kozlowski
2025-07-23 7:23 ` Ivan Vecera
2025-08-03 11:12 ` Krzysztof Kozlowski
2025-08-04 18:26 ` Ivan Vecera
2025-08-04 18:45 ` Andrew Lunn
2025-08-05 15:26 ` Ivan Vecera
2025-08-05 15:31 ` Andrew Lunn
2025-07-17 17:11 ` [PATCH net-next 2/2] dpll: zl3073x: Initialize clock ID from device property 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=20250717171100.2245998-1-ivecera@redhat.com \
--to=ivecera@redhat.com \
--cc=Prathosh.Satish@microchip.com \
--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®