From nobody Sat Apr 4 01:35:09 2026 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.17]) (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 E1C4A1B3925; Sat, 21 Mar 2026 22:30:18 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.17 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774132220; cv=none; b=hR9qLawfajT3Oy1g62TG1P0Y7XkIDXAKuCLHhjCg5xhJl7ah1WwgGxGotG25pgSrVZamOBWJZOFFqZc6oV4eepk6FC1oyAHc2H9dxdXU47qYd9C7FUlcUfIfbZZwtbboz6wHEQ5AHDgRdC3ZSLSwOnc2l+VZlpXxoBpdXi9YLp4= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774132220; c=relaxed/simple; bh=hYTA8iUKl0X+UOSv4rV5POwDjvdL2+lTdynEuwcEsbk=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=bREkTYTZeuc57Vz4cnzKXskRuONqmcGhRX5vMvMcckMQrqfoH32vK/eGBVaW63vSR7rzeWMJlEo4qyxG90hQRQ8Uj5rNikuwGTXHM5PwuvtaC8ZOcAu++/eFYmb0jByz+BDKLIBmXRNX87kw3lacj0nMxSMMHAuaycys5n+tC+o= 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=UPKCB8fI; arc=none smtp.client-ip=198.175.65.17 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="UPKCB8fI" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1774132219; x=1805668219; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=hYTA8iUKl0X+UOSv4rV5POwDjvdL2+lTdynEuwcEsbk=; b=UPKCB8fI9ev1QAG3kKWP0JhYp0gBsj/34dBqsryIEvMb88MRkydJngc7 bt4UXTnhKXgBBUbU0mHqoAqQb22T9RWl7YiMcaF11mU3nQB/l6uft+8DI vaOCXChnitSaRmObkmmoK3xFDaQTX3CjtNCNBqr1owVtfZ1/beHG5KDqJ jrxK5wmsnRMQNBZFKDeJ2xrEw/iWMGjixeOonNlJO0PceCzihAIOkRx94 PkZYbakFVAFFl/Pgny4OMSrY4uMin9D9wzs5Oq51rW9vwUSq0wjDwQU0L aDhL0EAi+tUXG11NChOUSExtOOCJVXr3ymtHJbeGjDx3RaEPrS6D/saFT g==; X-CSE-ConnectionGUID: NHnIEe7gSdCCbKcjbbZRwg== X-CSE-MsgGUID: B3oU7SNTSGGOHatTrbAE7A== X-IronPort-AV: E=McAfee;i="6800,10657,11736"; a="75150395" X-IronPort-AV: E=Sophos;i="6.23,134,1770624000"; d="scan'208";a="75150395" Received: from orviesa001.jf.intel.com ([10.64.159.141]) by orvoesa109.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Mar 2026 15:30:18 -0700 X-CSE-ConnectionGUID: iHMrUULUS/ChliilFda4lw== X-CSE-MsgGUID: 1DggN3p/RTKee2n8lJT6dg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.23,134,1770624000"; d="scan'208";a="261543945" Received: from gklab-003-001.igk.intel.com ([10.91.173.48]) by orviesa001.jf.intel.com with ESMTP; 21 Mar 2026 15:30:14 -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 v2 net-next 2/8] dpll: allow registering FW-identified pin with a different DPLL Date: Sat, 21 Mar 2026 23:26:21 +0100 Message-Id: <20260321222627.1193603-3-grzegorz.nitka@intel.com> X-Mailer: git-send-email 2.39.3 In-Reply-To: <20260321222627.1193603-1-grzegorz.nitka@intel.com> References: <20260321222627.1193603-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" 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 Reviewed-by: Jiri Pirko --- 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..55ad03977d6d 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 dp= ll_pin *pin, return -EINVAL; =20 mutex_lock(&dpll_lock); - if (WARN_ON(!(dpll->module =3D=3D pin->module && - dpll->clock_id =3D=3D 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 !=3D pin->module || + dpll->clock_id !=3D pin->clock_id)) { ret =3D -EINVAL; - else - ret =3D __dpll_pin_register(dpll, pin, ops, priv, NULL); + goto out_unlock; + } + + ret =3D __dpll_pin_register(dpll, pin, ops, priv, NULL); +out_unlock: mutex_unlock(&dpll_lock); =20 return ret; --=20 2.39.3