From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1EDF23E958A for ; Thu, 5 Feb 2026 15:44:02 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.129.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770306243; cv=none; b=cau5MCKn+jxa5XG89mAsswZYAL5glYK53K4a4e5duyVTRinKJnTYXYNo9L35NjPtPrlBb8qzHzVgU230DFOK/D9zr39C9haX/ix2w7lcR1Npu+dHxRUMNKPKAzkcF8rtFHG8lX8TnLyA0r2YhKcSeTtX8nMdyGWKLX2R4JARC7A= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770306243; c=relaxed/simple; bh=H7q2J1/J1WOIM3h8FTGC79FzhhbRtPNHrzphmIMW3dI=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=lV1rG6xEA0gd2xewgOxZdsJtlYgJSfB1I2/ULQWksnu6k8suCajRKDzrGuHaHlkTa+65lfetm4ssoOJTJo6/hncniC8GpQQDhIAKjnKjQyK0sH7KdEEXHgecXF9uORgTjObLWTYOHt4rJxMMY9tOjcumTvlr9jjfMY8t0K4AgnI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=EB3gtSuX; arc=none smtp.client-ip=170.10.129.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="EB3gtSuX" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1770306242; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=namUa4LSW2job2tTxSo2yNiR2IiIciWnpuvpbUA8DNg=; b=EB3gtSuXZ7WSoj5N2ZX38usm5WPIPygJ2mA4FG3xobd1XeW5rAxxyu8wJN7MDsqFW1KOwn jFPg7u92Nh6Sl390qY6MRTU5GMp5ENHLRYZEh9tQp8Q9AAcAgd89Z3eVYWRTZEJWFb79gU olYDnmvh7oUoTJng2t+H9v5C8DAGKaA= Received: from mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-195-ZVubfYLYMA-1wpPNkab0Fw-1; Thu, 05 Feb 2026 10:43:57 -0500 X-MC-Unique: ZVubfYLYMA-1wpPNkab0Fw-1 X-Mimecast-MFC-AGG-ID: ZVubfYLYMA-1wpPNkab0Fw_1770306236 Received: from mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.111]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id A1885195605F; Thu, 5 Feb 2026 15:43:55 +0000 (UTC) Received: from cnb-01.lab.eng.brq2.redhat.com (cnb-01.lab.eng.brq2.redhat.com [10.37.129.36]) by mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 7E81B1800465; Thu, 5 Feb 2026 15:43:53 +0000 (UTC) From: Ivan Vecera To: netdev@vger.kernel.org Cc: Prathosh Satish , Vadim Fedorenko , Arkadiusz Kubalewski , Jiri Pirko , 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 Message-ID: <20260205154350.3180465-1-ivecera@redhat.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.111 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