Received: by 2002:a05:7412:b130:b0:e2:908c:2ebd with SMTP id az48csp2306322rdb; Mon, 20 Nov 2023 07:37:26 -0800 (PST) X-Google-Smtp-Source: AGHT+IFKBUC0DH12H4MKYAdcPxMZD/8xUwcdZC6sz6WLsrNxBHZNRtezJ0ZLJzk1JUYBLPhUJ6XU X-Received: by 2002:a05:6a20:e104:b0:187:f97d:771b with SMTP id kr4-20020a056a20e10400b00187f97d771bmr11017500pzb.40.1700494645651; Mon, 20 Nov 2023 07:37:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1700494645; cv=none; d=google.com; s=arc-20160816; b=aqG75twrUOMDr5Z+bn5gVyLOPBmYonoiAoBbdeemmZ2nJ3Se3TQYoa7Qz3lV3warfO NHYZI9+36j8uJlbKOPcg9ouQ9jOTY+9zFh4rcHeu1xLOwYT507GlG/sfObBSi2vwIYkp NZRCJuE5W/3rX6F47fepnb8s9+0AFMBw09D5v0rNarayPzEH8dU+mWBL4aax7FC/R5Il tSyqJiH+90ikPlXSjZCYXkSixVqL1A2NSRZNEID2PWhCy8CBy9zOatyG+at6zprbJCNm qVu259Yhjl//jlmdOsJxevSeffxA6YLdDnZMRzp1PGLTCaY4KE+SFoztnRfQ2oNSBuoJ x1Hg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=o0mw2JgobxwE3CByukMe4G5waOUJCs1Oqg/+hT2lg0M=; fh=+swbtmywOpgkaVFTL1dSn7K5I/0/vHckNGNEoZn1AoY=; b=QsoQAdbdSoCzH136vUH1ls5soPh6IB1BVIHCgpUz2o+zYUcDEeeG34VUhwEleNk5i2 HiDvmITAGrVtMbNkcfLMgGY+CPLeSmX9HPxqu6k8v0ildij2uK2XQIOAGBEfuV1jxqC3 aEtnmPBE7+2+zzmdaIfghjDIUznJ8XK1ZKCQ+vwc0S7TbuRmJH+a1LeAsWUS0JDm+L5F YQB7TcQKKih4xeN3gghmJO31Lxev2YJVcN/mMGUg14yURc7KzmI9FF1tDeLpRRaA8/x3 iElSMfElylqc3YSQ8eo8HlQhfbmkypYWJfAXWFpmyzSyoFLJBL0V0M3W5trJ9Jlm6CEJ /3qg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=MZhPMwca; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.32 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=lunn.ch Return-Path: Received: from agentk.vger.email (agentk.vger.email. [23.128.96.32]) by mx.google.com with ESMTPS id u2-20020a631402000000b005b92b048254si8506164pgl.201.2023.11.20.07.37.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 20 Nov 2023 07:37:25 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.32 as permitted sender) client-ip=23.128.96.32; Authentication-Results: mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=MZhPMwca; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.32 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=lunn.ch Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by agentk.vger.email (Postfix) with ESMTP id 9DD918082DC3; Mon, 20 Nov 2023 07:35:32 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at agentk.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234387AbjKTPfT (ORCPT + 99 others); Mon, 20 Nov 2023 10:35:19 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49768 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234366AbjKTPfR (ORCPT ); Mon, 20 Nov 2023 10:35:17 -0500 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 89A4F9F; Mon, 20 Nov 2023 07:35:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=o0mw2JgobxwE3CByukMe4G5waOUJCs1Oqg/+hT2lg0M=; b=MZhPMwcajRhLZ9BHsVAMYvESlP unjmzfPzaUvwIeYdhuX++Sh2goFYq41AnneW4mEzZduSkQu0TCF5uFbT7UXMFxo0xAiQYrzZhZehi HCwTGcu1aMnsiFKPW9OgnQBF7yiwyWyw28BTWjA4EUg0mVDZdAB5AevPSZjr8XkxnLus=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1r56IZ-000ewk-Vn; Mon, 20 Nov 2023 16:34:55 +0100 Date: Mon, 20 Nov 2023 16:34:55 +0100 From: Andrew Lunn To: Jie Luo Cc: "Russell King (Oracle)" , davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org, hkallweit1@gmail.com, corbet@lwn.net, netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [PATCH v5 3/6] net: phy: at803x: add QCA8084 ethernet phy support Message-ID: <1d4d7761-6b42-48ec-af40-747cb4b84ca5@lunn.ch> References: <20231118062754.2453-1-quic_luoj@quicinc.com> <20231118062754.2453-4-quic_luoj@quicinc.com> <1eb60a08-f095-421a-bec6-96f39db31c09@lunn.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on agentk.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (agentk.vger.email [0.0.0.0]); Mon, 20 Nov 2023 07:35:32 -0800 (PST) > Hi Andrew, > The interface mode 10G_QXGMII is a type of USXGMII-M, the other modes > such as 20G-QXGMII, 20G-OXGMII... > > As for the interface mode 10G-QXGMII, there is a multiplexer for 4 PHYs, > then do 66bit/68bit encode in xpcs and pass to PMA, the link topology: > quad PHY --- multiplexer ---XPCS --- PMA. > the 10G-QXGMII interface block includes multiplexer, XPCS and PMA. > > when the PHY works on SGMII mode, then there is no xpcs, the only fourth > PHY of qca8084 can work on SGMII mode, the link topology: > the fourth PHY --- PCS --- PMA, the SGMII block includes PCS and PMA. What i missed is that you have two different PMA blocks. PHY4 can be muxed to either the QXGMII PMA or the 2500BaseX PMA. This is not clear in the commit message, and i think why you are getting questions about how 2500BaseX can work over QXGMII. Please expand you commit message to explain the architecture in more detail. So, next question. How do you control what PMA PHY4 is connected to? Is this going to be based on interface mode? QXGMII it is configured to use the QXGMII PMA? SGMII, 1000BaseX, and 2500BaseX it is configured to the other PMA? > Here is a problem as Russell mentioned earlier, we need to know which PHY > device is changing the link status when the 10G-QXGMII mode is used, > since there are 4 PHYs, when one of them has the link change, there is no > PHY device information passed to the PHYLINK, so the PCS driver don't > which PHY is changing link status and 10G-QXGMII mode don't know which > channel(mapped to PHY) should be configured. This is the first time QXGMII has been seen in mainline, so its good to explain the background. Are you saying there is a USXGMII-M level link change status? The link between the SoC and the PHY package is up/down? If it is down, all four MAC-PHY links are down. If it is up, it is possible to carry frames between the SoC and the PHY package, but maybe the PHYs themselves are down? Withing the four multiplex streams, is there a per stream link change indication? Andrew