From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pj1-f42.google.com (mail-pj1-f42.google.com [209.85.216.42]) (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 2791C2222C5 for ; Wed, 4 Feb 2026 13:17:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.216.42 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770211038; cv=none; b=qd7tQz7V8u8JqtYqP0nL1DH9aDbqAXP7VAv8N4+sVDi0gt9xJvJrDB1E8y40SNf6a6qA1cMFqEWy9+bYEv361aEc+1j9ZZN07X4szS4ZJxVdb5q9sqSDTmyX1f/QU1RW796QiKtzaL5/is2XbtHfUKhbAVmt2JjsJjHSnmi8M/Y= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770211038; c=relaxed/simple; bh=4fhGAl1etiRKhkugayByjRtTz7JIa5wVXw0UDNoMW38=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=efTL8KYOXmqigOHaXYVpe3QeHAZ4SO3WjfnQIizMumf89lWZNG1teegx10kBIOKveADm/vVFnQOerSev9rgiWdXNg0DZQD0BAM5aodChk5niAaCGUYJ2yK+ij1wnxEKn93OjvIHzCFDb8MmXYe6Air/rHri9GemPQED99lZ1zBo= 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=MU23SF5T; arc=none smtp.client-ip=209.85.216.42 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="MU23SF5T" Received: by mail-pj1-f42.google.com with SMTP id 98e67ed59e1d1-34c93e0269cso559216a91.1 for ; Wed, 04 Feb 2026 05:17:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1770211037; x=1770815837; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=4fhGAl1etiRKhkugayByjRtTz7JIa5wVXw0UDNoMW38=; b=MU23SF5TXAVvaeG0jPS9AomjuYYbtcmSN+NkLQh5ymkdlbzj0tuh48NxLjYPSIg7Nr K8r2fVWkAgNQVF1IXo6rfdhv6Tg+T9tnG5H/8Wyb8CjMz8ERlj6fhTmeIpGPWjFuP2ZE O/dthkvz07b1Xbvejnpq3iRCP9ntLYNeNqQRSzbrZJ8SzmqctoRTQJXfjPlzc3ifERN5 uBtZdx7Jn5xEMBizvdBFrnaN2eir362UdM32l6mPxtiWXLJwahG7AuHCtm8uHsMK1pWD D6O0rUA2xyh3zRPNNckeiRKm0FqXS+XDECOyZdgqeCLjo54H79DwD3CCUwUZX1ru2GiY NYFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1770211037; x=1770815837; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=4fhGAl1etiRKhkugayByjRtTz7JIa5wVXw0UDNoMW38=; b=ZKXEY1ZI+I88DtOVqiwJM2vEEhoHbUxHEoWURtjWtUNwDQtx+nBjHGfQdpyR0YTBHq Hhnn7igALV0TVOJC6OekYOac7e7L1gOqhZR/NWqmE6JLBjBlUPJicNGTq+NZfH8tk2ag 79PRCFo3z0j7ifajMBmnAj2esYKkqBNYw7o0U6mLBXEdavkAEiQInYARKAwNbPSu9cX1 baz5lkOQv9RPOzhnlNdH2bQdGrDceTBSp+ftgPsHY4xrDQGa7IDvknB/1Snbux4U6ldr ozHlUKo0QAO+JZZNJa5FlKHbQC0Pj9R6tmRj4QG6AUH2pDRFKVPhuCjMRFXU9/iKZLXb kQ4w== X-Forwarded-Encrypted: i=1; AJvYcCXhdcHmvr9/CY/l47ksE9jplB+LsrKu9Mq71JbN3i2SNnAAvdml6bE1VR/xoT7m7nEOE23GVInoh15l@vger.kernel.org X-Gm-Message-State: AOJu0YxZzjrCyJcXvba0PVZ7ngtwrGWRlm/yICf+bIVJKeyVOdn7THuv BWcQdpPoY7UtBSvpHxO63pDf3WbiZYdYL58UYO6jjb0AyaVNy7DWGMto X-Gm-Gg: AZuq6aL81ID8WvvemG7sHRoIrp1qZkIabM4LrtxEfhAu0x/kLrKS/Wm10+oGNlX1BHr soMiLcEXI2jSh7zDVyI7UC+m/evs1zd0hR0RyN/XH/y+0pu2tSNqOMQmAPwsfy7tf1S+ZTo/ueo MRJx9Q2AYS2HVQ0N1CQQsZ6/0p+OMEqgO7nFfoazm/AszsbDvQ2zA09/zdVvmEd9LgkfNrAtpsT RA/SrVb/4LN4/tiUCjjNnqKeLoq7P9/B3AuArVy+gEK6PcHj7A2/gd0sDwZsK1+1U65xBxukYrG Tjsk7OillS0CcuO6OwlmhfNNnkLECiKLDnfU3wGtgswmI0tQ8Qhd2LZguGXitEMoC0J2pYYqD4y yQNf6ABJ8qA9ywa9Wq6+pWLCB9w51ffxMuTi/gir7/Opo6OwxIiJ1gYiUBRXDZjiq3B9u32egDa 2c8aR04BVFCghwUZANuM6gbVaZ0UIhCB8y24/o2hwgvKexIRmGALO1V+aWH9nbCLZgj6QJwhSdW gW0RVj1wgapr5xvnSjp8P7HGAncrQ== X-Received: by 2002:a17:90b:254c:b0:34e:6e7d:7e73 with SMTP id 98e67ed59e1d1-354777ef744mr5226490a91.11.1770211037312; Wed, 04 Feb 2026 05:17:17 -0800 (PST) Received: from d.home.mmyangfl.win (tunnel997320-pt.tunnel.tserv3.fmt2.ipv6.he.net. [2001:470:1f04:2c7::2]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-35485dcb7f4sm2568072a91.8.2026.02.04.05.17.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 04 Feb 2026 05:17:16 -0800 (PST) From: yangfl X-Google-Original-From: yangfl To: michio.haiyaku@gmail.com Cc: 20251017060859.326450-4-mmyangfl@gmail.com, andrew@lunn.ch, conor+dt@kernel.org, davem@davemloft.net, devicetree@vger.kernel.org, edumazet@google.com, horms@kernel.org, krzk+dt@kernel.org, kuba@kernel.org, linux-kernel@vger.kernel.org, linux@armlinux.org.uk, mmyangfl@gmail.com, netdev@vger.kernel.org, olteanv@gmail.com, pabeni@redhat.com, robh@kernel.org Subject: Re: [PATCH net-next v14 3/4] net: dsa: yt921x: Add support for Motorcomm YT921x Date: Wed, 4 Feb 2026 21:16:51 +0800 Message-ID: <20260204131707.224142-1-yangfl@users.noreply.github.com> X-Mailer: git-send-email 2.51.0 In-Reply-To: <60f98b3a-79de-494a-895f-4d1eb21a405a@gmail.com> References: <60f98b3a-79de-494a-895f-4d1eb21a405a@gmail.com> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit On Wed, Feb 4, 2026 at 3:12 PM michio da neko wrote: > > Hi David Yang, > > I am testing your YT9215 driver on a CIG device (ODM for a carrier) > which uses the Qualcomm IPQ5018 SoC paired with the Motorcomm YT9215S > switch. > > The switch itself is detected correctly via MDIO bitbang, but I am > facing issues with the internal PHYs. They are detected with a specific > ID |0x01e04281| which falls back to the "Generic PHY" driver, and the > ports remain in |NO-CARRIER| state even when cables are plugged in. I > tried the existing Motorcomm PHY driver but it does not seem to cover > this specific ID. > > Here is my setup details: > > DTS Configuration: I am using phy-mode = "internal" for the ports. (Full > DTS available here: > https://github.com/michioxd/openwrt-wf810df/blob/1b37e3adee7ab6651430511af259687a5a57edc5/target/linux/qualcommax/files/arch/arm64/boot/dts/qcom/ipq5018-ax3000cv2.dts) > > > &mdio_bitbang { >      /* ... */ >      yt9215: switch@1d { >          compatible = "motorcomm,yt9215"; >          reg = <29>; >          /* ... */ >          ethernet-ports { >              ethernet-port@0 { >                  reg = <0>; >                  phy-mode = "internal"; >                  phy-handle = <&sw_phy0>; >              }; >              /* ... */ >          }; >      }; > }; > > > dmesg Output: The chip ID is detected as 0x90020002, but PHYs are generic: > > > [   13.405614] yt921x gpio-1:1d: Motorcomm YT9215S ethernet switch, > chipid: 0x90020002, chipmode: 0x2 0x0 > [   14.004664] yt921x gpio-1:1d: configuring for fixed/2500base-x link mode > [   14.018058] yt921x gpio-1:1d: Link is Up - 2.5Gbps/Full - flow > control off > [   14.097426] yt921x gpio-1:1d lan1 (uninitialized): PHY [gpio-1:1d:00] > driver [Generic PHY] (irq=POLL) > [   14.160182] yt921x gpio-1:1d lan2 (uninitialized): PHY [gpio-1:1d:01] > driver [Generic PHY] (irq=POLL) > [   14.226811] yt921x gpio-1:1d lan3 (uninitialized): PHY [gpio-1:1d:02] > driver [Generic PHY] (irq=POLL) > > > ip link Output: > > > 3: lan: mtu 1508 qdisc fq_codel state > UP qlen 1000 >      link/ether ... brd ff:ff:ff:ff:ff:ff > 4: lan1@lan: mtu 1500 qdisc noqueue > master br-lan state LOWERLAYERDOWN qlen 1000 >      link/ether ... brd ff:ff:ff:ff:ff:ff > 5: lan2@lan: mtu 1500 qdisc noqueue > master br-lan state LOWERLAYERDOWN qlen 1000 >      link/ether ... brd ff:ff:ff:ff:ff:ff > 6: lan3@lan: mtu 1500 qdisc noqueue > master br-lan state LOWERLAYERDOWN qlen 1000 >      link/ether ... brd ff:ff:ff:ff:ff:ff > > Have you encountered this PHY ID (0x01e04281) before? If this ID > requires a driver patch, do you know if it shares the same register > layout or behavior with any existing supported YT8xxx PHYs (like YT8511 > or YT8521)? Knowing its closest relative would help me attempt to add > support for it in drivers/net/phy/motorcomm.c. > > Any advice on how to bring up these ports would be appreciated. > > Best regards, Michio > > -- > michio da neko > https://michioxd.ch > Hi, Please do not use PATCH thread for technical support, as it CCs to tons of unrelated people. If you are looking closer you might find the thread about the chip on the OpenWRT forum. As for your question, the internal PHYs are standard and do not need a separate driver for basic support.