public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Ivan Vecera <ivecera@redhat.com>
To: netdev@vger.kernel.org
Cc: Prathosh Satish <Prathosh.Satish@microchip.com>,
	Vadim Fedorenko <vadim.fedorenko@linux.dev>,
	Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
	Jiri Pirko <jiri@resnulli.us>,
	linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/2] dpll: zl3073x: Include current frequency in supported frequencies list
Date: Thu,  5 Feb 2026 16:43:48 +0100	[thread overview]
Message-ID: <20260205154350.3180465-1-ivecera@redhat.com> (raw)

This series ensures that the current operating frequency of a DPLL pin                                                                                      
is always reported in its supported frequencies list.                                                                                                       
                                                                                                                                                              
Problem:                                                                                                                                                    
When a ZL3073x DPLL pin is registered, its supported frequencies are                                                                                        
read from the firmware node's "supported-frequencies-hz" property.                                                                                          
However, if the firmware node is missing, or doesn't include the                                                                                            
current operating frequency, the pin reports a frequency that isn't                                                                                         
in its supported list. This inconsistency can confuse userspace tools                                                                                       
that expect the current frequency to be among the supported values.

Solution:
Always include the current pin frequency as the first entry in the
supported frequencies list, followed by any additional frequencies
from the firmware node (with duplicates filtered out).

Patch 1 refactors the output pin frequency calculation into a reusable
helper function zl3073x_dev_output_pin_freq_get(), which mirrors the
existing zl3073x_dev_ref_freq_get() for input pins.

Patch 2 modifies zl3073x_pin_props_get() to obtain the current
frequency early and place it at index 0 of the supported frequencies
array, ensuring it is always present regardless of firmware node
contents.

Ivan Vecera (2):
  dpll: zl3073x: Add output pin frequency helper
  dpll: zl3073x: Include current frequency in supported frequencies list

 drivers/dpll/zl3073x/core.h | 30 ++++++++++++++++++++++++++++
 drivers/dpll/zl3073x/dpll.c | 39 +------------------------------------
 drivers/dpll/zl3073x/out.h  | 17 ++++++++++++++++
 drivers/dpll/zl3073x/prop.c | 32 +++++++++++++++++++-----------
 4 files changed, 69 insertions(+), 49 deletions(-)

-- 
2.52.0


             reply	other threads:[~2026-02-05 15:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 15:43 Ivan Vecera [this message]
2026-02-05 15:43 ` [PATCH net-next 1/2] dpll: zl3073x: Add output pin frequency helper Ivan Vecera
2026-02-05 15:43 ` [PATCH net-next 2/2] dpll: zl3073x: Include current frequency in supported frequencies list Ivan Vecera
2026-02-07  4:50 ` [PATCH net-next 0/2] " patchwork-bot+netdevbpf

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=20260205154350.3180465-1-ivecera@redhat.com \
    --to=ivecera@redhat.com \
    --cc=Prathosh.Satish@microchip.com \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=jiri@resnulli.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.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