From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 7776FCD5BC8 for ; Tue, 26 May 2026 13:27:34 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id 23A1760F80; Tue, 26 May 2026 13:27:34 +0000 (UTC) X-Virus-Scanned: amavis at osuosl.org Received: from smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavis, port 10024) with ESMTP id HNZXFx-Y5mcZ; Tue, 26 May 2026 13:27:32 +0000 (UTC) X-Comment: SPF check N/A for local connections - client-ip=140.211.166.142; helo=lists1.osuosl.org; envelope-from=intel-wired-lan-bounces@osuosl.org; receiver= DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 5779C60F47 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=osuosl.org; s=default; t=1779802052; bh=MOoP5D+3GayAYX2czvg1Rx3yDcS/IwtTCjoyb2Dq9dI=; h=Date:From:To:References:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Cc:From; b=fjNFUSfUq5BoVyChAqtQr/JLPtfgK52oTdUhhegipfcPpdXNlhLk/tKmZj61izQRm PYrPsDSxsfxufm0oJg7HpXAey7tVya/KLAzcd0T1rpfRMAEfoYS7FSp0LYsfBaIG4q 6z2uXE/IaZgHxsMt6NFw0WulX4jCKowV3tTpTsVYNxGFMza83o5tQbAUAr4ZnAKOeE hhwDd73rmBY9LWC6XCotyCNU+PJ6f2bmi4FYuAbuKUBzQLrT83wMdEp46ejPXfXg7t h6P5LeCWIlSUJ14c0+A6mYu2yvCaEpwNWsq+VLSO944wvLqqM3exZHofKwJHZNrQVi dxUZhcqNn5Fxw== Received: from lists1.osuosl.org (lists1.osuosl.org [140.211.166.142]) by smtp3.osuosl.org (Postfix) with ESMTP id 5779C60F47; Tue, 26 May 2026 13:27:32 +0000 (UTC) Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by lists1.osuosl.org (Postfix) with ESMTP id 7FAB3297 for ; Tue, 26 May 2026 13:27:31 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id 5D0B640FE3 for ; Tue, 26 May 2026 13:27:31 +0000 (UTC) X-Virus-Scanned: amavis at osuosl.org Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavis, port 10024) with ESMTP id k5kcb_l2bU6n for ; Tue, 26 May 2026 13:27:30 +0000 (UTC) Received-SPF: None (mailfrom) identity=mailfrom; client-ip=2a00:1450:4864:20::335; helo=mail-wm1-x335.google.com; envelope-from=jiri@resnulli.us; receiver= DMARC-Filter: OpenDMARC Filter v1.4.2 smtp4.osuosl.org 3FFF840FB5 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 3FFF840FB5 Received: from mail-wm1-x335.google.com (mail-wm1-x335.google.com [IPv6:2a00:1450:4864:20::335]) by smtp4.osuosl.org (Postfix) with ESMTPS id 3FFF840FB5 for ; Tue, 26 May 2026 13:27:26 +0000 (UTC) Received: by mail-wm1-x335.google.com with SMTP id 5b1f17b1804b1-48e8132c6d0so67062365e9.1 for ; Tue, 26 May 2026 06:27:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1779802044; x=1780406844; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=MOoP5D+3GayAYX2czvg1Rx3yDcS/IwtTCjoyb2Dq9dI=; b=VpybRN0y1KLIbr30+q8L5A0epdrQpkLwiCnJgRv/xthL6Wpg24IYWLggUJVv7Ud2Ms B5qWrqVjP2gXs/xNcKXUqTXA4i+R2/KSQIozPVRk5gW6TscduI/68JQwYA3OE5TXutY4 E5lDGMzyEASJ4AoXfVcW2RWcTnngKOt0aXDf+JRacm/2qrnMgl16IZRRk4dWI9yQgkaT SEBz/HLc2XK7vcDjvfPHqHW8ykjiW1XXHClUBBXVw5k3Hybwv3ef4+U0v0raap/3VmQ1 EikUPwMAFDumCcv9MfXT/Cwdwgw/22oFXqA79ti+2iXn56B7x+K0XGKe49EJ6jIwOucT zlwQ== X-Forwarded-Encrypted: i=1; AFNElJ+lvjkb68VcIs6dD8v53Wd+sTn9Gw2+wpYChjRdWR/amar43hFACaLlnyjtXisq2Yixe0Kbt6UdbjzoqxFgxH0=@lists.osuosl.org X-Gm-Message-State: AOJu0YzMhQfDf/8Qk2RGhnUMV4yXqxdnQDuISBdXKWj78c9pXdeUGe+y V7Qx7wvHpAJeksBw2KawvP6VYTOpGptURIXijkk0MYMIIRK3UJc/KhiMO1eLZpfIgT0= X-Gm-Gg: Acq92OG6U5jPedk3sUsparBzS0jiJl+gwS4lTiM7iYGZIE1lDoeUD6QbujW4ERtbfCY XSnKRKmc/WUBFlECP43dmow1OMIoJHEOIZwZSWYg2y91pHq4N9gR1YmKJZweF988+CV1YExKKHs GvhmAWxsq2lvptGr/T4yKLsMn602PrBJi1D6UrrErCA9TVMA5Sc+5MzpNbRnrLj073E6Cq2HFyW LOQta1RjZiC4ALwLO+a0KlnHLvatGUql5JzHd1RgXbs5lvE3oYzR9VFG39lWGhGOGKmEqc9+qlh U3UuiuD1ed70Bg9nt93EgUHoMEhcV6LLG3Yzy9Hv84DcEoABDSEPZpi7jLMECR1PFmyWONySA3x w0NMeEHRw5M8efWRvZeazTmj01UNk19n/0vq0eRdzYDTg+0bScmJQj0iDIeTWJnc+BTLwto4bqu eH848/Ce+MLxHcKFJRxtU3KI7ImsgcSOUk X-Received: by 2002:a05:600c:4f52:b0:490:4f91:5519 with SMTP id 5b1f17b1804b1-4904f91568dmr296207535e9.18.1779802043944; Tue, 26 May 2026 06:27:23 -0700 (PDT) Received: from localhost ([140.209.217.212]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-4904526c926sm578470375e9.1.2026.05.26.06.27.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 26 May 2026 06:27:23 -0700 (PDT) Date: Tue, 26 May 2026 15:27:19 +0200 From: Jiri Pirko To: Grzegorz Nitka Message-ID: References: <20260526093419.639220-1-grzegorz.nitka@intel.com> <20260526093419.639220-4-grzegorz.nitka@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260526093419.639220-4-grzegorz.nitka@intel.com> X-Mailman-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=resnulli-us.20251104.gappssmtp.com; s=20251104; t=1779802044; x=1780406844; darn=lists.osuosl.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=MOoP5D+3GayAYX2czvg1Rx3yDcS/IwtTCjoyb2Dq9dI=; b=E1IGe/CwR3wJSZvfWq4matOEbcPXG6NN7XqWTekKYeFiYJaKVdcL+uJUIDlBzrHKGO NUBT+9yx6jPn/1HC9V0sHhmbwlP9TlETNRXzI6VA/kKfL0RFZinE0YM99vEGY2II+eXc WZ0ku2gz0K7euWBowdv7XywT0Xtl+17/XUVSmTEYQuEMUILX0k6ZVUf3KQMaejaRIoKk hHHEtIoQocKg6QNxtwBtHdN4uhnXa5Pstvs+0RtHEHRAnz+aERrlVi0TciZGEaRuSbms LHmjQt09IKFT2tujH4DAVYbHyaBuXBLWh2xeHq8x/mV9L4I5KUujdADzsfCFrK01K8RM xo/g== X-Mailman-Original-Authentication-Results: smtp4.osuosl.org; dmarc=none (p=none dis=none) header.from=resnulli.us X-Mailman-Original-Authentication-Results: smtp4.osuosl.org; dkim=pass (2048-bit key, unprotected) header.d=resnulli-us.20251104.gappssmtp.com header.i=@resnulli-us.20251104.gappssmtp.com header.a=rsa-sha256 header.s=20251104 header.b=E1IGe/Cw Subject: Re: [Intel-wired-lan] [PATCH v11 net-next 3/8] dpll: extend pin notifier with notification source ID X-BeenThere: intel-wired-lan@osuosl.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Intel Wired Ethernet Linux Kernel Driver Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: ivecera@redhat.com, Aleksandr Loktionov , kuba@kernel.org, vadim.fedorenko@linux.dev, edumazet@google.com, netdev@vger.kernel.org, richardcochran@gmail.com, donald.hunter@gmail.com, linux-kernel@vger.kernel.org, arkadiusz.kubalewski@intel.com, Prathosh.Satish@microchip.com, andrew+netdev@lunn.ch, intel-wired-lan@lists.osuosl.org, horms@kernel.org, przemyslaw.kitszel@intel.com, anthony.l.nguyen@intel.com, pabeni@redhat.com, davem@davemloft.net Errors-To: intel-wired-lan-bounces@osuosl.org Sender: "Intel-wired-lan" Tue, May 26, 2026 at 11:34:14AM +0200, grzegorz.nitka@intel.com wrote: >Extend the DPLL pin notification API to include a source identifier >indicating where the notification originates. This allows notifier >consumers to distinguish between notifications coming from >an associated DPLL instance, a parent pin, or the pin itself. > >A new field, src_clock_id, is added to struct dpll_pin_notifier_info >and is passed through all pin-related notification paths. Callers of >dpll_pin_notify() are updated to provide a meaningful source identifier >based on their context: > - pin registration/unregistration uses the DPLL's clock_id, > - pin-on-pin operations use the parent pin's clock_id, > - pin changes use the pin's own clock_id. > >As introduced in the commit ("dpll: allow registering FW-identified pin >with a different DPLL"), it is possible to share the same physical pin >via firmware description (fwnode) with DPLL objects from different >kernel modules. This means that a given pin can be registered multiple >times. > >Driver such as ICE (E825 devices) rely on this mechanism when listening >for the event where a shared-fwnode pin appears, while avoiding reacting >to events triggered by their own registration logic. > >This change only extends the notification metadata and does not alter >existing semantics for drivers that do not use the new field. > >Reviewed-by: Arkadiusz Kubalewski >Reviewed-by: Aleksandr Loktionov >Signed-off-by: Grzegorz Nitka Reviewed-by: Jiri Pirko