From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) (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 6DF611A585; Wed, 3 Jan 2024 14:22:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lunn.ch Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b="YqTRV7Vl" 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=eCxJHVjVhX9miBj2Rlu9rCBVdhCCoWX7LYP4sTNG5GY=; b=YqTRV7Vl5smuubd7bGIR3inNfQ +94q6QgmxA3IeXXoHZL+vCBQ/BkV9Iv9O7S873V1kRCxtnKj1mgFPeKU2DRCovyRKXr5ZvpqkSUI0 cM5B0yuI3FKDC9mTnibQt5HTnPIkqpafopbBDGOATHcWNSKZl87HzRNbZWUYlm0Y/Nvw=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1rL28V-004GKS-5P; Wed, 03 Jan 2024 15:22:23 +0100 Date: Wed, 3 Jan 2024 15:22:23 +0100 From: Andrew Lunn To: Jie Luo Cc: Christian Marangi , "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, p.zabel@pengutronix.de, f.fainelli@gmail.com, netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [PATCH v8 14/14] dt-bindings: net: ar803x: add qca8084 PHY properties Message-ID: <85590a5b-9d5a-40cb-8a0e-a3a3a1c3720a@lunn.ch> References: <7c05b08a-bb6d-4fa1-8cee-c1051badc9d9@lunn.ch> <6abe5d6f-9d00-445f-8c81-9c89b9da3e0a@quicinc.com> <1bddd434-024c-45ff-9866-92951a3f555f@quicinc.com> <6593e0a3.050a0220.5c543.8e12@mx.google.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: > Yes, APQ8084 is the application SoC. > QCA8084 is the pure PHY chip which has quad-phy. I think everybody agrees these are terrible names, being so close together but being very different devices. You have the issues of not giving clear explanations of your hardware. This is resulting in a lot of wasted tome for everybody. So please make your explanations very clear. I personally would avoid using APQ8084 or QCA8084 on there own. Always say the application SoC APQ8084, or the PHY chip QCA8084, or the switch embedded within the application processor APQ8084, or the PHYs embedded within the Application processor etc. This is particularly important when talking about clocks and resets, since the PHYs embedded within the application processor are likely to have different clocks and reset controllers to the PHY chip QCA8084. Andrew