[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250717171100.2245998-1-ivecera@redhat.com>
Date: Thu, 17 Jul 2025 19:10:58 +0200
From: Ivan Vecera <ivecera@...hat.com>
To: netdev@...r.kernel.org
Cc: Vadim Fedorenko <vadim.fedorenko@...ux.dev>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>,
Jiri Pirko <jiri@...nulli.us>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Prathosh Satish <Prathosh.Satish@...rochip.com>,
devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
Michal Schmidt <mschmidt@...hat.com>,
Petr Oros <poros@...hat.com>
Subject: [PATCH net-next 0/2] dpll: zl3073x: Read clock ID from device property
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
Powered by blists - more mailing lists