Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp980173iog; Thu, 30 Jun 2022 14:19:17 -0700 (PDT) X-Google-Smtp-Source: AGRyM1s3zn+wG7VoRp8lHMkQ5GmiUEZluXW90dbk7o8m4UfXbO/UbCiaw6YTIFqISPZj+ZMcZ1Eb X-Received: by 2002:aa7:df19:0:b0:435:5eb7:5e31 with SMTP id c25-20020aa7df19000000b004355eb75e31mr14121429edy.418.1656623957015; Thu, 30 Jun 2022 14:19:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656623957; cv=none; d=google.com; s=arc-20160816; b=MIZwRRTBbAZCLlG/MgpjKmXaODWBRK9mVEBnguoKtzRtd6wptFMWHIPob14vk4aqbu IrIHcYhF3/IpG18VOsQCm3+DgmQouqYXFlckpaYcq6tiTrvO7InTRyIjom10XoUdVE1B CUyubAsC6hn8QtYrwYXx/0bDPRCDPDRcaSf/FtlUvY7iN7MJ8H7c5L4TCj1XI92H59rg +VsAQjY0HIDh39dvcWcpY/kBYiTGDwfgBX3GpEoZ+T9WtkySNaCtELga9d2MKDAhFzf6 zIe6+RM7NA1zXlY6G1AxX2ZUn5igBEkWGxQP3EdPug8tEhbArsACgjFehQPDSGQEuEKW laVw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:user-agent:references:in-reply-to :subject:cc:to:from:date:content-transfer-encoding:mime-version :dkim-signature; bh=82UJBr6ACNE0EKd6nPjOsmQDwDWzYJeTBz8Z22qFb7s=; b=URXIzk6KeWwV7A1ClwpZjA9x7NZBHZveZegPkOitwYAZK+LAi5MbdNE+Juv4+/W8GT 7TeB0FxVF3GoINZBO/4eQnmHX7EZP7F121j3LvYXPFxposv6MI1UFaBpMg+Bl445LRkM 6DLXtKSRqkHZWYXGO0RkU9QyqGqjYwuVl3EIhE6fzMc8FbRDJt4DskVk7Cd+p4yYyEdj ePfJZDzFYBReLis+tk7s74ER9xiivgLHlZVnRE1tTjGVGV+uWA6lt6m9DEB//k/ZyYNX eJAVhV+XyALm4gOZm2CAvShY5fHeeWh9jw6QUI12Tt1T+zh1Sp29mnTX1rJznzOArpjX DWww== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@walle.cc header.s=mail2016061301 header.b=LPfRjyOg; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id gb5-20020a170907960500b0072a7561b2c4si1977877ejc.964.2022.06.30.14.18.50; Thu, 30 Jun 2022 14:19:17 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@walle.cc header.s=mail2016061301 header.b=LPfRjyOg; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233794AbiF3U4h (ORCPT + 99 others); Thu, 30 Jun 2022 16:56:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48276 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230503AbiF3U4f (ORCPT ); Thu, 30 Jun 2022 16:56:35 -0400 Received: from ssl.serverraum.org (ssl.serverraum.org [IPv6:2a01:4f8:151:8464::1:2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A3933403E0; Thu, 30 Jun 2022 13:56:33 -0700 (PDT) Received: from ssl.serverraum.org (web.serverraum.org [172.16.0.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ssl.serverraum.org (Postfix) with ESMTPSA id 1CBF922236; Thu, 30 Jun 2022 22:56:31 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walle.cc; s=mail2016061301; t=1656622591; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=82UJBr6ACNE0EKd6nPjOsmQDwDWzYJeTBz8Z22qFb7s=; b=LPfRjyOguub3ig8hubkevjW8TfHe97qALfLiNNisD02rx0fodn12ZsD0BNjuTz4wo+xO0S 5hKfTk6XJjruMs1FmHjsG5z7val4CMh8HJoQrwKB9SxMCGR7nV6TM6C/3B6glXcPcbvycX 5bDt1VQUwHuAgTtOTl6h3P7X3twR/R8= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 30 Jun 2022 22:56:30 +0200 From: Michael Walle To: Horatiu Vultur Cc: "David S . Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Rob Herring , Krzysztof Kozlowski , UNGLinuxDriver@microchip.com, netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH net-next 0/4] net: lan966x: hardcode port count In-Reply-To: <20220630204433.hg2a2ws2zk5p73ld@soft-dev3-1.localhost> References: <20220630140237.692986-1-michael@walle.cc> <20220630204433.hg2a2ws2zk5p73ld@soft-dev3-1.localhost> User-Agent: Roundcube Webmail/1.4.13 Message-ID: <0169b5865944d6522a752b02321a7f4b@walle.cc> X-Sender: michael@walle.cc X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 2022-06-30 22:44, schrieb Horatiu Vultur: > The 06/30/2022 16:02, Michael Walle wrote: >> EXTERNAL EMAIL: Do not click links or open attachments unless you know >> the content is safe >> >> Don't rely on the device tree to count the number of physical port. >> Instead >> introduce a new compatible string which the driver can use to select >> the >> correct port count. >> >> This also hardcodes the generic compatible string to 8. The rationale >> is >> that this compatible string was just used for the LAN9668 for now and >> I'm >> not even sure the current driver would support the LAN9662. > > It works also on LAN9662, but I didn't have time to send patches for > DTs. Then when I send patches for LAN9662, do I need to go in all dts > files to change the compatible string for the 'switch' node? I'd assume there is one lan9662.dtsi and yes, there should then be compatible = "microchip,lan9662-switch"; or compatible = "microchip,lan9662-switch", "microchip,lan966x-switch"; depending on the outcome of the question Krzysztof raised. And of course adding the compatible string to the driver with a port count of 4 (?). I can't find anything about the lan9662, and you've mentioned it has 4 ports. Are there four external ports? I was under the impression the last digit of the SoC name stands for the number of ports. -michael