From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wr1-f48.google.com (mail-wr1-f48.google.com [209.85.221.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E5C5C5476F4 for ; Tue, 8 Sep 2026 14:40:53 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.221.48 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788878460; cv=none; b=jpgGotjP2ChyRy348rY1XnYHnY7b3yvJ1lFLlcstyLJo46O1t1EjTlMRv2feuapl24ZrcTmhHm9tW2MQvbAqFFcT1WfNni/1UlLG6kRxbJku38g9ya2ZX04ZZ2Y/OgtFmg2sTOGTmF3CvhazOpLPqRxEws7tymmv1a35ZzEu5Is= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788878460; c=relaxed/simple; bh=5cup85Qb2q3dpZ9j4NJ+riAqKzhV1ATVnwyRINFCU4Y=; h=Message-ID:Date:From:To:Subject:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=CSsB0Ic4v8cFWZec0AjGH/LK5n7nefm8OXlK2E5oarl/TXB2r+NYcojmM0+UVeG3TYT0u0jdE23dIoGSep/qyg/84Wegp1v7oMGUH+npmORVFwngfElqHHrOzJv+JWHxLL1AGS7RkqHxGexzUSAn//zwDL+p4PrnqwgENsabX5s= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=PjN306iC; arc=none smtp.client-ip=209.85.221.48 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="PjN306iC" Received: by mail-wr1-f48.google.com with SMTP id ffacd0b85a97d-485850cbac3so3055859f8f.3 for ; Tue, 08 Sep 2026 07:40:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1788878449; x=1789483249; darn=lists.linux.dev; h=in-reply-to:content-disposition:content-type:mime-version :references:subject:to:from:date:message-id:from:to:cc:subject:date :message-id:reply-to:content-type; bh=Miv8sjNJdTG6Gu0+wUlQ27sQKF6CmSEymk2ANPK2DPg=; b=PjN306iCBitMHGLpsnHpk9mFU5q4754hQUu8NFfR9i7qWMAdPyIRHLNaU8kGnrscIW SnicIqRvwTabmqR5sLjzAXg+C/2aqOsUWQHeef6s1uhgonGD61H1p2I1WyEHQeKc9U95 hEvSMzKIZEe4pD9aFOPu8UZa5kAviiUFf/T0m0f4R6QkhGrp91v4AVk0FGTbGjjCuOjs YQWFYqnpVLm8okuRzzLzniCWrLKwMSl5xyzxFviccnpQG9/NuUKRSMSvVVUaau5R+k7U BjpKQsj8iCiFw6mK4gbYbu6V0BSP3iTM1IK8fhTmjYX9KkSsEfhS48/uhiVY0MrqiQgh r7aA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1788878449; x=1789483249; h=in-reply-to:content-disposition:content-type:mime-version :references:subject:to:from:date:message-id:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=Miv8sjNJdTG6Gu0+wUlQ27sQKF6CmSEymk2ANPK2DPg=; b=X09nE3DiWrI5WtVWi+M92o/eAbXqjykZK/YByPM/kSok92AfZVsYjNQeL6QmXmw+so s6DDIT1HQCP9lmOEXEzWeHiAn1Kl3ANYU2WNIK1/1u5OGzjzl0viCF7zOJNruMiTZynb ttawI2ney7rlUwQdDRgBa+vFsXb998yQt4WOR407BKx19xV3J2QLn5a4+PFf0yHLCZ2b 8pqYdRH1GczAz3Sc2o5Yc4RjoSfOKxGz33mPjKUEpOuxfUos0i+VGICduNNmjO5F9Qsz AoNg73iMMlzAFIMMxQQ4PsX7k3UzhJIqqxDQaXV0clYZpQV2lgeJEZHX5xYaIn03j/+u Y+dA== X-Forwarded-Encrypted: i=1; AKwUvBwJM+CpH/GxbfUq79jyIhov9aMN9r4lwZKy3Dn+sDxjWoSw0MeJry4z5LuQQI9CBxvfUtA8@lists.linux.dev X-Gm-Message-State: AFuF++mYAHaLM1dmeRK2973yL3Zw8OIplCB+avuBE8jm1crT9UbdpKPK ew2fjCsV+Ri5kuk9ZJNDjT6jjrcMSXDJvLESc1l+d0a20q1o+2lR7GUG X-Gm-Gg: AYBFou1co5U9l8nM6UKTWLq8RxgJcqgv+9A/4/cYnV1Hje6P31pX1A9k2FqGJ6t+16K ac5+PfYpr8oUtaIDl6nPQn3k97B9EwuQ6Cl6fQUz0EO1CgfdLc8d0b7kq/CWQCVeuGQIsfnPFWR hv5tycIEIAlPZNZkNkRsxboFwvEjnj7E+rgJJEb1o9Rc0QN0Z2OErxHwpCEsIFBlRZ9VuQUZK5/ sJnIxrNwEKDsjv3i3MrHyIBoVq4HP0vLPW8XalpL35DcmuBUSwNZgtGj1AM6+DjuWRyPghaDLA1 vvnfRAQQRzYC4+qjH1ZqcXCXKR4X0PMTeB+53wzugS1ak3W/3e7sSpIwZgRR0CrS5LkYGwwt1Pp OGkvGHAW8IC9BA5879jssUptvEZ9zI79d3ra6iHbKib53VMwuwnTNhSTj9sSeT9icWlOEBsxHtv 4/Pys4jC7UZQnoQwrGbKwlHYcHigoteQVziLYPM1Mo+5fyBaLXdqOSbmGobx8LEiSwa4gWruOq4 90BHmvHV9FXtQ9rFZhT2Gdw7HWpPx8E4vWo X-Received: by 2002:a05:6000:46c2:b0:484:4769:18a4 with SMTP id ffacd0b85a97d-485872cd677mr23543135f8f.14.1788878449028; Tue, 08 Sep 2026 07:40:49 -0700 (PDT) Received: from Ansuel-XPS. (host-79-26-252-140.retail.telecomitalia.it. [79.26.252.140]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-485883959f0sm39338196f8f.10.2026.09.08.07.40.46 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 08 Sep 2026 07:40:48 -0700 (PDT) Message-ID: <6aa01e70.ebbd881c.32bd35.196e@mx.google.com> X-Google-Original-Message-ID: Date: Tue, 8 Sep 2026 16:40:44 +0200 From: Christian Marangi To: Maxime Chevallier , Andrew Lunn , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Simon Horman , Jonathan Corbet , Shuah Khan , Randy Dunlap , Lorenzo Bianconi , Heiner Kallweit , Russell King , Philipp Zabel , Nathan Chancellor , Nick Desaulniers , Bill Wendling , Justin Stitt , netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, llvm@lists.linux.dev Subject: Re: [PATCH net-next v15 00/12] net: pcs: Introduce support for fwnode PCS References: <20260901083001.8044-1-ansuelsmth@gmail.com> Precedence: bulk X-Mailing-List: llvm@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260901083001.8044-1-ansuelsmth@gmail.com> On Tue, Sep 01, 2026 at 10:29:15AM +0200, Christian Marangi wrote: > This series introduce a most awaited feature that is correctly > provide PCS with fwnode without having to use specific export symbol > and additional handling of PCS in phylink. > > At times there were 2 different implementation (this and the one > from Sean) but Sean agreed that this can be picked and used in favor > of his implementation as long as his case with race condition is > correctly handled. > > --- > First the PCS fwnode: > > The concept is to implement a producer-consumer API similar to other > subsystem like clock or PHY. > > That seems to be the best solution to the problem as PCS driver needs > to be detached from phylink and implement a simple way to provide a > PCS while maintaining support for probe defer or driver removal. > > To keep the implementation simple, the PCS driver devs needs some > collaboration to correctly implement this. This is O.K. as helper > to correctly implement this are provided hence it's really a matter > of following a pattern to correct follow removal of a PCS driver. > > A PCS provider have to implement and call fwnode_pcs_add_provider() in > probe function and define an xlate function to define how the PCS > should be provided based on the requested interface and phandle spec > defined in fwnode (based on the #pcs-cells) > > fwnode_pcs_get() is provided to provide a specific PCS declared in > fwnode at index. > > A simple xlate function is provided for simple single PCS > implementation, fwnode_pcs_simple_xlate. > > A PCS provider on driver removal must call fwnode_pcs_del_provider() > to delete itself as a provider. > > --- > Second PCS handling in phylink: > > We have the PCS problem for the only reason that in initial > implementation, we permitted way too much flexibility to MAC driver > and things started to deviate. At times we couldn't think SoC > would start to put PCS outside the MAC hence it was OK to assume > they would live in the same driver. With the introduction of > 10g in more consumer devices, we are observing a rapid growth > of this pattern with multiple PCS external to MAC. > > To put a stop on this, the only solution is to give back to phylink > control on PCS handling and enforce more robust supported interface > definition from both MAC and PCS side. > > It's suggested to read patch 0003 of this series for more info, here > a brief explaination of the idea: > > This series introduce handling of PCS in phylink and try to deprecate > .mac_select_pcs. > > Phylink now might contain a linked list of available PCS and > those will be used for PCS selection on phylink_major_config. > > MAC driver needs to define pcs_interfaces mask in phylink_config > for every interface that needs a dedicated PCS. > > These PCS needs to be provided to phylink at phylink_create time > by setting the .fill_available_pcs and .num_possible_pcs in phylink_config. > Helpers to parse PCS from fwnode are provided > fwnode_phylink_pcs_count() that will return the count of PCS entries > described in the firmware node and fwnode_phylink_pcs_parse() that will > fill a preallocated array of PCS pointer with the actual available PCS > (ignoring the one that still needs to be probed). > > phylink_create() will fill the internal PCS list with the passed > array of PCS. phylink_major_config and other user of .mac_select_pcs > are adapted to make use of this new PCS list. > > The supported interface value is also moved internally to phylink > struct. This is to handle late removal and addition of PCS. > (the bonus effect to this is giving phylink a clear idea of what > is actually supported by the MAC and his constraint with PCS) > > The supported interface mask in phylink is done by OR the > supported_interfaces in phylink_config with every PCS in PCS list. > > PCS removal is supported by forcing a mac_config, refresh the > supported interfaces and run a phy_resolve(). > > PCS late addition is supported by introducing a global notifier > for PCS provider. If a phylink have the pcs_interfaces mask not > zero, it's registered to this notifier. > > PCS provider will emit a global PCS add event to signal any > interface that a new PCS might be available. > > The function will then check if the PCS is related to the MAC > fwnode and add it accordingly. > > A user for this new implementation is provided as an Airoha PCS > driver. This was also tested downstream with the IPQ95xx QCOM SoC > and with the help of Daniel also on the various Mediatek MT7988 > SoC with both SFP cage implementation and DSA attached. > > Lots of tests were done with driver unbind/bind and with interface > up/down also by adding print to make sure major_config_fail gets > correctly triggered and reset once the PCS comes back. > > The dedicated commits have longer description on the implementation > so it's suggested to also check there for additional info. > > It's worth to mention that OpenWrt is currently using this on > Mediatek SoC and QCOM ipq807x/ipq60xx/ipq50xx and Airoha are > already ported in staging tree for testing. > Any news of this? I feel this version is now very mature and wonder if an human review is possible or any feedback of any needed change to make any progress? -- Ansuel