From:   Sean Anderson <sean.anderson@seco.com>
To:     Shawn Guo <shawnguo@kernel.org>, Li Yang <leoyang.li@nxp.com>,
        linux-arm-kernel@lists.infradead.org
Cc:     netdev@vger.kernel.org, Madalin Bucur <madalin.bucur@nxp.com>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
        linux-kernel@vger.kernel.org,
        Sean Anderson <sean.anderson@seco.com>
Subject: [PATCH] arm64: ls1046ardb: Use in-band-status for SFP module
Date:   Tue, 24 Jan 2023 12:47:57 -0500
Message-Id: <20230124174757.2956299-1-sean.anderson@seco.com>
Content-Transfer-Encoding: 8bit
Content-Type: text/plain
MIME-Version: 1.0
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?us-ascii?Q?csgkcjTKKGfvgjPQXXojUnr8ROwxXOfo4altFWZSgXxnNZr1EakJqCPfYnXh?=
 =?us-ascii?Q?tOH9qdKPAl9iV0Z3C6+qbTf+URmIDzbSYPqHT8eVHC6iUGyGbWfRuDrlRps1?=
 =?us-ascii?Q?2I5Nqg8gKpU2bnkubIYy+vIpVr4CXGGtRktpTI7dW2M33nrfp+qRk/3/X+C1?=
 =?us-ascii?Q?6AsaVSzqbEP1crWsOLLTsnDQbTOF0RKPJsCAPqz4Yl0VZNO7/vsGfp4rO85I?=
 =?us-ascii?Q?twi7z1aw9KHkHTfR9M6VXTCS6CJOV/gXlYLywjgfG/4QHrNtJLqnCEx//24N?=
 =?us-ascii?Q?ADv+L4dOjLpWrq0TPP9YpYbV3TXJfmfZYgqhbBCnGNBxPBo1ZpFjOqe7XNpj?=
 =?us-ascii?Q?BObMDZwOHkeV12GBKBm91HMpATQv2YVpaWzexH1psrmv4d5sKcPTCwGrnGHg?=
 =?us-ascii?Q?vgNMXrKlkok/mAlbeQltR6PRkmcotsvPho36aD7Bps2e1NsQKMgAVqGZbwrC?=
 =?us-ascii?Q?zcpDgFXATTMh85ouFdSGevxd//xkKXXYmeCwUR0biyRqT3I76Ec0ChO+2h24?=
 =?us-ascii?Q?oavzpJQXcrX7PQzEOYUK4OkvstKObnkSFG9eMS1Ve5MdFuYIpiozz9y9ZVp4?=
 =?us-ascii?Q?8TNyKJiMFGIDnrOE6YiivpyGjWRQCn29CZcCU4ii4JbfKeBM02B8Ys0B3Wz2?=
 =?us-ascii?Q?G6KmZIKwJ+umNxbq+qubCjvWnEJ1Vn1PVRQUHipaIEhXUIVfU1SufKsS5sV9?=
 =?us-ascii?Q?QaMekWAUQHEzRQngn4QedkNBElUewRXJ6a2th03+PaJiCqzFJt+0G+fuDR4Y?=
 =?us-ascii?Q?ijpVrq4dLZJBQ0jBJZN+K0zqWL8pdJOrev1h6dSmv2SSmFVr6Iznm+kciSLQ?=
 =?us-ascii?Q?iJyZIUkbNs8cKxXIHcXCdzSVbzwvRdYMWE437PogS0H5TGguVTQlXb3qjRBX?=
 =?us-ascii?Q?zJE1OqXdSB8WOkAgmKYrd7Vrh45628wcWl58L7InhRUsKFQIVuOmtjYz8tcr?=
 =?us-ascii?Q?vqnWgBHGZ/XOTscFibeBBZThvaowJjrMZ7ciwHkvk02qE5xoJ5M9TXM6rYZi?=
 =?us-ascii?Q?ITqzsEJQsViI1tCZCWbAPAB6D5b67lhjL/MVi5AwHCNAiZ1e8yGc0nq86ZaK?=
 =?us-ascii?Q?SLG0bE+KSwMzzQoVLSGwKworvy/PGMtZ7F1h6XhlFUvcmjvJw9ALJF+Rnnzf?=
 =?us-ascii?Q?pcTrMAoZrufJoC0xtv8w2/ZhM0bqBEDknpQocu1qMtsLu3pYUMbr7ZvNw7+C?=
 =?us-ascii?Q?Yz+kGcWZO0sMrpYokLbKVvH7i80Q+Yn92M/8Sd5Ee7XT1J/8XV7tacwXdyoS?=
 =?us-ascii?Q?fy0849t71E/80uV5ySjw6v2d/EW7Cj1Nl9J24BLgxazO4Vi0gBazS0WvJBHD?=
 =?us-ascii?Q?vs9YSZTUegfl2kUjNpqLwb+/9FfTmdyEl0Eg4dPejOwLZlEl9/eYMVmzRZmx?=
 =?us-ascii?Q?gl7Duh8mMnLAi8Ltauq1fno1GsIYTr1Z7vuYtI2/PkdMBryBVT62NYQRV4ik?=
 =?us-ascii?Q?R7CZWJWTMHUF0fIN97fO5zTBRf91TBv4pfqIeKFAZ89HF/tLJt/hkXCZXtWM?=
 =?us-ascii?Q?oxTJXiiQyJZ1mSp79FpltifygHar+/yxJ678+IbAqpSaNSdOwGivJt8i7PoU?=
 =?us-ascii?Q?qZzV/7AN6dLtSmDET1n8mEcS+86Ol+z3opknNaaRJET25gS34lc3EJptbHXW?=
 =?us-ascii?Q?jA=3D=3D?=
X-OriginatorOrg: seco.com
X-MS-Exchange-CrossTenant-Network-Message-Id: a30cb61d-d746-473a-e893-08dafe333123
X-MS-Exchange-CrossTenant-AuthSource: DB9PR03MB8847.eurprd03.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Jan 2023 17:48:24.9445
 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: bebe97c3-6438-442e-ade3-ff17aa50e733
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: 4u4sxc+TblJeQ66rajMi5Kf3qxzccsfjnh9DtfiEfTX2yzy4qGlB1SBp4h+Xm3cCTEOb/7LCMj4CvqOpF/MWxQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DU0PR03MB8785
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

net10 is connected to an SFP module. Unfortunately, the I2C lines are
not connected due to an address conflict. Now that DPAA uses phylink, we
can use in-band-status. This lets us determine whether the link is up or
down instead of assuming it is up all the time. Also fix the phy mode
while we're here.

Signed-off-by: Sean Anderson <sean.anderson@seco.com>
---
This should likely go through Shawn Guo's tree, although it could also
go through net-next. It will conflict with [1] which modifies the
adjoining lines and is likely to go through the phy tree.

[1] https://lore.kernel.org/linux-phy/Y8pLjLWjv0nJa+ww@matsya/T/#m54a5ed1450322df1499836edbb561bc4d6daf4d8

 arch/arm64/boot/dts/freescale/fsl-ls1046a-rdb.dts | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1046a-rdb.dts b/arch/arm64/boot/dts/freescale/fsl-ls1046a-rdb.dts
index 7025aad8ae89..07f6cc6e354a 100644
--- a/arch/arm64/boot/dts/freescale/fsl-ls1046a-rdb.dts
+++ b/arch/arm64/boot/dts/freescale/fsl-ls1046a-rdb.dts
@@ -153,8 +153,8 @@ ethernet@f0000 { /* 10GEC1 */
 	};
 
 	ethernet@f2000 { /* 10GEC2 */
-		fixed-link = <0 1 1000 0 0>;
-		phy-connection-type = "xgmii";
+		phy-connection-type = "10gbase-r";
+		managed = "in-band-status";
 	};
 
 	mdio@fc000 {
-- 
2.35.1.1320.gc452695387.dirty