From nobody Thu Sep 11 01:38:50 2025 Received: from smtpout-03.galae.net (smtpout-03.galae.net [185.246.85.4]) (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 DAC2832A81F; Wed, 10 Sep 2025 14:55:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.246.85.4 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1757516156; cv=none; b=gulENoGaiyvseQbabPmO361PsQRHb2MPnnQUzinqnmhFYAnbT7LBhmIru7koOOrUZavGqZI7/Mxp4Hf0VX9uZ1N+mbcN3zwhErXR6o8VCxTSWNu3uKaBPBgmNbcPwomD+p8QojAufkRwpjUym6ReOfeXKIeKT2AuzqXrztXI+pk= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1757516156; c=relaxed/simple; bh=Bc3e3/0ahFi9v5qz8AZyosX6PMtW/7OQTL8jvV0sdXs=; h=From:Date:Subject:MIME-Version:Content-Type:Message-Id:References: In-Reply-To:To:Cc; b=AcdiLF7j6DQ+tcrxAjuZxAFmRVE5Dn/pf7xee80LgwqJQivRMu0lIzM4+pO1D22mCWSBma/Bejhe4FufXJ5/mERQ/qm6fttkl5GewnYWiwuyy0TpBUn7JbAnTF8CMU6CNx/puuHVw0QXwyPy5oPhd05e57491R87E7DCrk9tvUo= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=bootlin.com; spf=pass smtp.mailfrom=bootlin.com; dkim=pass (2048-bit key) header.d=bootlin.com header.i=@bootlin.com header.b=0jjTLQlu; arc=none smtp.client-ip=185.246.85.4 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=bootlin.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=bootlin.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=bootlin.com header.i=@bootlin.com header.b="0jjTLQlu" Received: from smtpout-01.galae.net (smtpout-01.galae.net [212.83.139.233]) by smtpout-03.galae.net (Postfix) with ESMTPS id 0DC264E40BDD; Wed, 10 Sep 2025 14:55:53 +0000 (UTC) Received: from mail.galae.net (mail.galae.net [212.83.136.155]) by smtpout-01.galae.net (Postfix) with ESMTPS id F24D2606D4; Wed, 10 Sep 2025 14:55:52 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id D261C102F1CED; Wed, 10 Sep 2025 16:55:44 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bootlin.com; s=dkim; t=1757516151; h=from:subject:date:message-id:to:cc:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=Z56JzDWKmQD/kK3e7696NE0uPkdwabDSZWVgzG00JDo=; b=0jjTLQluKeDkY5SA+dZQ5tGXUCW+EiG/eIerCtRfUrNfbAeHDjmqczQJIkBU5Cc2JqRC07 YNknpkI+S+gFWIceaOkZuz8bbGMRCFoGpuPeJvF2ZemDL7RvsZAUTQOAHpBPrcnsMFZfmw JtIQac1SpjbVgInMug7DYhkoI4FiwY5/d2/CffCkGh7OSUCsVM9oSTImHbnFguAj4q5Liw kxpOCygeVJX8k/QCJH4AQtdCpaMdXD3x79rKtz0RnSGMRZOfqGMaydbZrskndXS1B4brNQ zDeKmWZ/G/KY/YYinjoUR/YqIJE3/hgqq/SDTYCxYX46AoelBhu46scKGUvr2g== From: Bastien Curutchet Date: Wed, 10 Sep 2025 16:55:24 +0200 Subject: [PATCH net-next 1/2] dt-bindings: net: dsa: microchip: Add strap description 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="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <20250910-ksz-strap-pins-v1-1-6308bb2e139e@bootlin.com> References: <20250910-ksz-strap-pins-v1-0-6308bb2e139e@bootlin.com> In-Reply-To: <20250910-ksz-strap-pins-v1-0-6308bb2e139e@bootlin.com> To: Woojung Huh , UNGLinuxDriver@microchip.com, Andrew Lunn , Vladimir Oltean , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Marek Vasut Cc: Thomas Petazzoni , =?utf-8?q?Miqu=C3=A8l_Raynal?= , Pascal Eberhard , Woojung Huh , netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, "Bastien Curutchet (Schneider Electric)" X-Mailer: b4 0.14.2 X-Last-TLS-Session-Version: TLSv1.3 At reset, some KSZ switches use strap-based configuration. If the required pull-ups/pull-downs are missing (by mistake or by design to save power) the pins may float and the configuration can go wrong. Add a strap description that can be used by the driver to drive the strap pins during reset. It consists of a 'reset' pinmux configuration and a set of strap GPIOs. Since the pins used and the nature of the configuration differ from one KSZ switch to another, GPIO names aren't used. Signed-off-by: Bastien Curutchet (Schneider Electric) --- Documentation/devicetree/bindings/net/dsa/microchip,ksz.yaml | 12 ++++++++= ++++ 1 file changed, 12 insertions(+) diff --git a/Documentation/devicetree/bindings/net/dsa/microchip,ksz.yaml b= /Documentation/devicetree/bindings/net/dsa/microchip,ksz.yaml index eb4607460db7f32a4dffd416e44b61c2674f731e..f40a5e3cd0e4d39c809a1fb6697= bc3bc64f35fec 100644 --- a/Documentation/devicetree/bindings/net/dsa/microchip,ksz.yaml +++ b/Documentation/devicetree/bindings/net/dsa/microchip,ksz.yaml @@ -37,6 +37,13 @@ properties: - microchip,ksz8567 - microchip,lan9646 =20 + pinctrl-names: + items: + - const: default + - const: reset + description: + Used during reset for strap configuration. + reset-gpios: description: Should be a gpio specifier for a reset line. @@ -80,6 +87,11 @@ properties: enum: [2000, 4000, 8000, 12000, 16000, 20000, 24000, 28000] default: 8000 =20 + strap-gpios: + description: + Strap pins to drive during reset. For KSZ8463, the first GPIO drives= the + RXDO line, the second one drives the RXD1 line. + interrupts: maxItems: 1 =20 --=20 2.51.0