From nobody Sat Apr 4 01:33:46 2026 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.19]) (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 047003F65F6; Thu, 2 Apr 2026 23:10:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.19 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775171438; cv=none; b=Hld8YO+yn6XSAjG2SJdq13uKoWWD2Rhi/h+KK2SFQ/Wcp7gFLm5l7SQSolkmHCKx5Z0TK6+5vDKQ13Gj6MW6PywWfHxMxzZrADHjLYvRHZU1vXr9p/8hcXrS66X9ZDMGppKrGsTyXuzS7qr4fzLppDhx5kayMJXCPuLMNiY39hA= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775171438; c=relaxed/simple; bh=Izbqb6M5jnyKGkCx6C0FAG3R4OV2Dm01nNdm0f5hBzY=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=XD+4M/yMA/49OvDphRdc1TojVaoIuXZxB6x8Nyvrk12ogZHkJiwyk8aZDf3UmNwnNaGp9QJ01VyDCqg53SI1Y/xtW5MDYacgswHPopQEbqZo3+WfWjawcFN6KiTBZWzPPyiOjuDuTucUIvv46WBlCF7UdDSkabCJ8HrIdx1RbLg= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com; spf=pass smtp.mailfrom=intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=ZpbKuyum; arc=none smtp.client-ip=198.175.65.19 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="ZpbKuyum" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1775171437; x=1806707437; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=Izbqb6M5jnyKGkCx6C0FAG3R4OV2Dm01nNdm0f5hBzY=; b=ZpbKuyumb/TKQUgNqoZ5ATmeq/0SzabKU3gHna8aV253xRIwP7sjp6we AKRMACBFzDsBgbX+vBP8zDjacWlMwRZvy/6Plj+xYuKnaZ8UKmn1yXFsc D0VrLP9MsgHKfxL3eyK7hscMx6f2sPDkXB72XGGedteySw1qlzSXbMZW+ 0KtPgLSDvnJAam6Pe3xPr+U+Fx587SiCSmZaLPRGpcYzcwWLtZizcPHcI IzFL1o1cDcC9RDw/nz0PybbON4ZGwnjTLE+mkwpANsh/WhJMVynjYw5mD vSdjU5MtC+1G042O4JMeqUkoE6Gd7GKXspiZaMtM5xGccAVBRrBmL2tGe A==; X-CSE-ConnectionGUID: RY9kP+wLTvOPz3tQiPdvTA== X-CSE-MsgGUID: iyNugGViTEmLS68pMFwwWw== X-IronPort-AV: E=McAfee;i="6800,10657,11747"; a="76123098" X-IronPort-AV: E=Sophos;i="6.23,156,1770624000"; d="scan'208";a="76123098" Received: from orviesa008.jf.intel.com ([10.64.159.148]) by orvoesa111.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Apr 2026 16:10:37 -0700 X-CSE-ConnectionGUID: zn4o8IXFSYeGhwfXaibKyg== X-CSE-MsgGUID: 6rWA4cGyQMGl/Fmfwh3p9w== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.23,156,1770624000"; d="scan'208";a="227044442" Received: from gklab-003-001.igk.intel.com ([10.91.173.48]) by orviesa008.jf.intel.com with ESMTP; 02 Apr 2026 16:10:33 -0700 From: Grzegorz Nitka To: netdev@vger.kernel.org Cc: linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org, poros@redhat.com, richardcochran@gmail.com, andrew+netdev@lunn.ch, przemyslaw.kitszel@intel.com, anthony.l.nguyen@intel.com, Prathosh.Satish@microchip.com, ivecera@redhat.com, jiri@resnulli.us, arkadiusz.kubalewski@intel.com, vadim.fedorenko@linux.dev, donald.hunter@gmail.com, horms@kernel.org, pabeni@redhat.com, kuba@kernel.org, davem@davemloft.net, edumazet@google.com, Grzegorz Nitka , Aleksandr Loktionov Subject: [PATCH v5 net-next 4/8] dpll: zl3073x: allow SyncE_Ref pin state change Date: Fri, 3 Apr 2026 01:06:22 +0200 Message-Id: <20260402230626.3826719-5-grzegorz.nitka@intel.com> X-Mailer: git-send-email 2.39.3 In-Reply-To: <20260402230626.3826719-1-grzegorz.nitka@intel.com> References: <20260402230626.3826719-1-grzegorz.nitka@intel.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" The SyncE_Ref pin may operate as either an active or inactive reference depending on board design and system configuration. Some platforms need to disable the SyncE reference dynamically (e.g., when selecting a different recovered clock input). The hardware supports toggling this pin, therefore advertise the STATE_CAN_CHANGE capability. Reviewed-by: Arkadiusz Kubalewski Reviewed-by: Aleksandr Loktionov Signed-off-by: Grzegorz Nitka --- drivers/dpll/zl3073x/prop.c | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/drivers/dpll/zl3073x/prop.c b/drivers/dpll/zl3073x/prop.c index ac9d41d0f978..acd7061a741a 100644 --- a/drivers/dpll/zl3073x/prop.c +++ b/drivers/dpll/zl3073x/prop.c @@ -215,6 +215,15 @@ struct zl3073x_pin_props *zl3073x_pin_props_get(struct= zl3073x_dev *zldev, =20 props->dpll_props.type =3D DPLL_PIN_TYPE_GNSS; =20 + /* + * The SyncE_Ref pin supports enabling/disabling dynamically. + * Some platforms may choose to expose this through firmware + * configuration later. For now, advertise this capability + * universally since the hardware allows state toggling. + */ + props->dpll_props.capabilities |=3D + DPLL_PIN_CAPABILITIES_STATE_CAN_CHANGE; + /* The output pin phase adjustment granularity equals half of * the synth frequency count. */ --=20 2.39.3