From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.13]) (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 B9DB83A2559; Wed, 18 Mar 2026 09:10:57 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.13 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773825059; cv=none; b=pE6YuZuAMuVW14UPoiru4D2Uu5MJQFYV54wAQcgym987si3VMjQ03E+sZn8qSzG7y9luf0LBGSWhHzQa7AAbhwhwaI8TAly9NFuGoP6in1EWXEmzb7xtXu8vJw5VuxSn+w/UqcCBwVMwq/cbVqPdwBtSo7xxnWzYfjzCaJTG8yQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773825059; c=relaxed/simple; bh=ZYXIR0UL9LVrZM1kSMAGifMsq/4oudcUuiVR9bc1/do=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=Xg+bQErHHvb9Q4VL3jNnBEOHGE8QEsFcg48SQESDm5Lhr8GT9kZiAYAbD+03k7t2q3VMZfY41dAQp3INFCBG/UcF72MeauTheD6r2fupi0uY34ihReTcu0jYzTK1FEaMQPnVm0DWdunQMZh5CdCvaQLx355e3pmYY5nN0k4nGC4= 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=BQvzNcNR; arc=none smtp.client-ip=192.198.163.13 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="BQvzNcNR" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1773825058; x=1805361058; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=ZYXIR0UL9LVrZM1kSMAGifMsq/4oudcUuiVR9bc1/do=; b=BQvzNcNRrKc3Do8uVDyS4ilAc9WpncV7o77BHRSvPVNYGdyjHqFeXHsM YbodZLE0VLCBM2KViyABQ1Zmv0QsAub1sbGOcwTtHv8DyXSzyjLgfBPla WtOyprN94kC1thn8HueMARoAc0v8k3A2LrOARjtVqPI+oDaWVvZEzhOmy Q21ScaJ4Ns5lasm/7k1dS2Xi4JfDPufOjc2iX/VtRLlIdQJfxIGAmErnE JENMk+NRGT/QyaI9RJhKa/ZTEwmBduoqZhIWsRGGYdYvoGa/pX8WOyymI o3R9odnERtohdF2eIzvCWdtRk8VvibuAuoJSdnkBlqkeAZ3zmYtFALEkL A==; X-CSE-ConnectionGUID: NdoHGPb+SpaT/bNes3sR4Q== X-CSE-MsgGUID: glV6Cn4sSJq1eeLFYSFmgA== X-IronPort-AV: E=McAfee;i="6800,10657,11732"; a="77484394" X-IronPort-AV: E=Sophos;i="6.23,127,1770624000"; d="scan'208";a="77484394" Received: from orviesa003.jf.intel.com ([10.64.159.143]) by fmvoesa107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Mar 2026 02:10:57 -0700 X-CSE-ConnectionGUID: CTwCpFYTTLuTRlW5exKTlw== X-CSE-MsgGUID: fAFcL34SQiSXA9zG+LH7kg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.23,127,1770624000"; d="scan'208";a="226699929" Received: from gklab-003-001.igk.intel.com ([10.91.173.48]) by orviesa003.jf.intel.com with ESMTP; 18 Mar 2026 02:10:53 -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, Grzegorz Nitka , Aleksandr Loktionov Subject: [PATCH net-next 2/8] dpll: allow registering FW-identified pin with a different DPLL Date: Wed, 18 Mar 2026 10:06:48 +0100 Message-Id: <20260318090654.611349-3-grzegorz.nitka@intel.com> X-Mailer: git-send-email 2.39.3 In-Reply-To: <20260318090654.611349-1-grzegorz.nitka@intel.com> References: <20260318090654.611349-1-grzegorz.nitka@intel.com> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Relax the (module, clock_id) equality requirement when registering a pin identified by firmware (pin->fwnode). Some platforms associate a FW-described pin with a DPLL instance that differs from the pin's (module, clock_id) tuple. For such pins, permit registration without requiring the strict match. Non-FW pins still require equality. Reviewed-by: Arkadiusz Kubalewski Reviewed-by: Aleksandr Loktionov Signed-off-by: Grzegorz Nitka --- drivers/dpll/dpll_core.c | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) diff --git a/drivers/dpll/dpll_core.c b/drivers/dpll/dpll_core.c index 3f54754cdec4..0d25c23bd850 100644 --- a/drivers/dpll/dpll_core.c +++ b/drivers/dpll/dpll_core.c @@ -880,11 +880,21 @@ dpll_pin_register(struct dpll_device *dpll, struct dpll_pin *pin, return -EINVAL; mutex_lock(&dpll_lock); - if (WARN_ON(!(dpll->module == pin->module && - dpll->clock_id == pin->clock_id))) + + /* + * For pins identified via firmware (pin->fwnode), allow registration + * even if the pin's (module, clock_id) differs from the target DPLL. + * For non-fwnode pins, require a strict (module, clock_id) match. + */ + if (!pin->fwnode && + WARN_ON_ONCE(dpll->module != pin->module || + dpll->clock_id != pin->clock_id)) { ret = -EINVAL; - else - ret = __dpll_pin_register(dpll, pin, ops, priv, NULL); + goto out_unlock; + } + + ret = __dpll_pin_register(dpll, pin, ops, priv, NULL); +out_unlock: mutex_unlock(&dpll_lock); return ret; -- 2.39.3