From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from relay1-d.mail.gandi.net (relay1-d.mail.gandi.net [217.70.183.193]) (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 06AD6125BA; Tue, 30 Apr 2024 04:58:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=217.70.183.193 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1714453100; cv=none; b=o4x05HsiZTx0XEVq654DZUi6CMVfkmhO6DTHT/FbZF07zrkVPoFHpl73tCGOTnRfbznhBz9AZ1vwr/yX687UBedI5Rp060SElw4+MtAFFjfUR5ekzFjZlugQ5fuiuH7MNykmk/JdEPym57mwUpnUwvywWLGZIml8pP2iFvnOmpY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1714453100; c=relaxed/simple; bh=FxARK+Ac1zGzaPGYkJ1m/SwB3s0XeVwOgtFDsG9w8NQ=; h=Message-ID:Date:MIME-Version:Subject:To:References:From: In-Reply-To:Content-Type; b=JdBkZslRQVF8E2k1NQJ9Xrl/tLpaub5jNBgHkNfogsOQChMfxxJnLgM7nzP5t7HEoKqjsrAFSfyg5Qom4y86+cE3lIkgZ2WP/Lhqbf8yChlJwYHfEYmQtHYwfo8TzhZvgy7RHNx1ohGISJuOdmcR18HRHIACa9Ywp7CkrDUzC5k= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arinc9.com; spf=pass smtp.mailfrom=arinc9.com; dkim=pass (2048-bit key) header.d=arinc9.com header.i=@arinc9.com header.b=GvqvmYBT; arc=none smtp.client-ip=217.70.183.193 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arinc9.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=arinc9.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=arinc9.com header.i=@arinc9.com header.b="GvqvmYBT" Received: by mail.gandi.net (Postfix) with ESMTPSA id 0C189240002; Tue, 30 Apr 2024 04:58:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arinc9.com; s=gm1; t=1714453095; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=FxARK+Ac1zGzaPGYkJ1m/SwB3s0XeVwOgtFDsG9w8NQ=; b=GvqvmYBTMir6yilmStEchowgXWLuj9LMkK0Iegexk6xEuqA/fTZrDaF9sc6ox/iy88ofS1 VeiY3TWT7VwSe0yIpNZrAryXpqBSGu4LpGjYjKjWi5e92jReF5OWMflTn0GMF0I2yVJ0pV hWyxbhqP7Qte/5DmFp3NPvMwBe24f4Vx4JrMEKPxO2n3vPgwHn63UnmaY511Q3OV7T/990 K6VXaKbbpeOMUNnGjfuuooSaLfFfV68W62qT+7An4iCTrkL1vDAPMfl3NgUgzH8xj7dC+5 ARtBmgiKmlgl229n0IU8wHbfyBSxqTvH9A27v7E861JDg+wNAzkw5viozmMN/Q== Message-ID: Date: Tue, 30 Apr 2024 07:58:08 +0300 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH net] net: dsa: mt7530: fix impossible MDIO address and issue warning To: Daniel Golle , Felix Fietkau , Rob Herring , Krzysztof Kozlowski , Conor Dooley , DENG Qingfang , Sean Wang , Andrew Lunn , Florian Fainelli , Vladimir Oltean , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Matthias Brugger , AngeloGioacchino Del Regno , Landen Chao , devicetree@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org References: Content-Language: en-US From: =?UTF-8?B?QXLEsW7DpyDDnE5BTA==?= In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-GND-Sasl: arinc.unal@arinc9.com On 4/30/24 02:45, Daniel Golle wrote: > The MDIO address of the MT7530 and MT7531 switch ICs can be configured > using bootstrap pins. However, there are only 4 possible options for the > switch itself: 7, 15, 23 and 31 (ie. only 3 and 4 can be configured, bit > 0~2 are always 111). Practically all boards known as of today use the > default setting which is to have the switch respond to address 31, while > the built-in switch PHYs respond to address 0~4 in this case. I'm not aware of the MT7531 switch having bootstrap pins to configure the PHY address. Are you sure this is the case? Arınç