From nobody Thu Apr 2 22:08:50 2026 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.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 432A62DA755; Thu, 26 Mar 2026 16:32:55 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.19 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774542776; cv=none; b=RhiCfRf43uuDR6bflcmtHKBEEFoCaYi6OVW1q7W3xcZoKjwBVEGeRTHSMeEnFuYjIq3PtAdd5OS59nDxM4ADDY4lfP1rhkWBKENGHhDYGLC6LKN+zqs3B8SiC4TOe6Zr5BeQqTEc3RuyBnURKJuDD2UuB+QZtCJryNOXd+NXxUI= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774542776; c=relaxed/simple; bh=Izbqb6M5jnyKGkCx6C0FAG3R4OV2Dm01nNdm0f5hBzY=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=Fw6f1eX/9zCM6UcoIvnYp0JnMfTNeqgcSGa/6X/VuAP9J6jnuP940Dreid7M/hzb6GgB0CIyOYq6be5XovlTspow9g+aeuJDX+qPFsPSFjZD0V3xtvf0i2zSPpIBE0I/iZn0YCBb4/ofrahLfSxWec761A1cdyQAcvBDcu6l7xc= 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=eP3og8sk; arc=none smtp.client-ip=192.198.163.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="eP3og8sk" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1774542775; x=1806078775; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=Izbqb6M5jnyKGkCx6C0FAG3R4OV2Dm01nNdm0f5hBzY=; b=eP3og8skrtshbDP1KtRnKd9kLPX1E7LQhMJQZXLugXC/W65+mMTAr2EX 95KNeHlOYawtl7xwo9YpKSfOGbNJj5uWdesmSS3cKgFouw8HsrBtxjrVv UgYuJ/H+13Rf9P04M1M1h6ZXzZHmBpVrjsSBttN3ONhHDxDlF4pNsJfvt gcOqxv2mrk2MDXpQ0t8CKVTf7w1giV7EsgRusTs/uXv1bUF70K4rOSYx5 ODyYnDJ1d2fDGMnU2Jb72NDlLzY3UQAbTbtEPjo/z3ExCVLkMJpiDVDSZ aDPakwjZP7avXXJi2iVT6lXghXRIIauGm3pojRo345wUu2EYPtRTTGVp0 A==; X-CSE-ConnectionGUID: 8MbKZN6OTG+C5qaim8dL1g== X-CSE-MsgGUID: 4MINUEK0Soi448MFsePclQ== X-IronPort-AV: E=McAfee;i="6800,10657,11741"; a="74636657" X-IronPort-AV: E=Sophos;i="6.23,142,1770624000"; d="scan'208";a="74636657" Received: from orviesa007.jf.intel.com ([10.64.159.147]) by fmvoesa113.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Mar 2026 09:32:55 -0700 X-CSE-ConnectionGUID: 4ypneq9KQxuydLG5tMkNjw== X-CSE-MsgGUID: B7XIhe7VT9u1M3sKGU9d+Q== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.23,142,1770624000"; d="scan'208";a="225311062" Received: from gklab-003-001.igk.intel.com ([10.91.173.48]) by orviesa007.jf.intel.com with ESMTP; 26 Mar 2026 09:32:51 -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 v4 net-next 4/8] dpll: zl3073x: allow SyncE_Ref pin state change Date: Thu, 26 Mar 2026 17:28:28 +0100 Message-Id: <20260326162832.3135857-5-grzegorz.nitka@intel.com> X-Mailer: git-send-email 2.39.3 In-Reply-To: <20260326162832.3135857-1-grzegorz.nitka@intel.com> References: <20260326162832.3135857-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