Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp14627766rwb; Mon, 28 Nov 2022 03:22:22 -0800 (PST) X-Google-Smtp-Source: AA0mqf79wsK75mApggRfU/ZRWRGTpathqXtVP8F65n7udI2VcsE70Te7T04IUd7kSZArqeTLE1hW X-Received: by 2002:a17:902:8217:b0:189:5859:adfd with SMTP id x23-20020a170902821700b001895859adfdmr21261260pln.6.1669634541864; Mon, 28 Nov 2022 03:22:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669634541; cv=none; d=google.com; s=arc-20160816; b=AFwlC5yYY0/8ub6xRDfYecdU4l21ayY1Hb/RrpW8r/l+CMTiss+AJG9JMKowu0Z0z8 WGPYeRco7Sh/log0GLdu0QpTR0pgX7oPHIt6z33p6zTSvXOnm8EFz7nZzU9saUsFiaYN A3sZ4IRaqO1koA7Z00WPQ8xYBFKuZC5wiNCIrjrczJ/wHAbQrKwLlGQgCBMc9gkkWMD9 AF9uzjKnaKYbpq7eAHAiQ1zDPxLJ4t/LH1zE/xSpKpxWLiJzEfA8jV5SOJuzHtXU5NBU 4o7YNk3h+/Lv5iXmSP7jE4uW595E/8ZzWM1xL9uCCAeaIUBUOpB751WjLuQFq9V73Y+K Gphg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:message-id:in-reply-to :date:references:subject:cc:to:from:dkim-signature; bh=xorotRfwzrdTFEeljDF1exBFoZnl7/79ZTQprEftyNs=; b=ycdw7c98BAS7g0o3Lnn1e93hJdbyhmAmc6LYu2/ur+pdIo8VlAEPbrgcYHRBM/br1i pDV4F2bXmqnvrYw+DcIZT9F80gUrRAV1YYI7t4c6kdt/njssGNd8laSIDd2GYOViygCm ntpDHRhcqCW3dB+NJlEy83hUepD4UzF8nf0vaDhRsWSHZCE0cW+94p7XoEnhGvoYGS3a reaL88iWb4qo84Q4C9O/sl3sY6pvp4lflXjWV4DuHJrnGU/DkyxgBDF+ms/GJ4n7rat7 wNbIf40iFAkkdnzJDRV2YEz/TJvlf5gjVd8oZa5SSlKhxrecwZkGoykvhj7HixkflcvU xtQQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=Zc3z3ZpS; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id d188-20020a6336c5000000b00477cead7cd1si12115406pga.644.2022.11.28.03.22.13; Mon, 28 Nov 2022 03:22:21 -0800 (PST) Received-SPF: pass (google.com: domain of linux-wireless-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=@kernel.org header.s=k20201202 header.b=Zc3z3ZpS; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230179AbiK1LRR (ORCPT + 67 others); Mon, 28 Nov 2022 06:17:17 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36146 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229890AbiK1LRQ (ORCPT ); Mon, 28 Nov 2022 06:17:16 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3754E6172; Mon, 28 Nov 2022 03:17:15 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id CD4316106C; Mon, 28 Nov 2022 11:17:14 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 24DD3C433D7; Mon, 28 Nov 2022 11:17:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1669634234; bh=xJRkcM/s19gYAXNwC6geD/5BTDYu4MnGAhHKzNufA+0=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=Zc3z3ZpSWt3HdcyaFQb77lXWXGjgErqrJLoSYdVZXy55Aku3lOHxFJeoyY+mqiho9 FpATB+axPKq/E+U+UnKlRr+Z6LW3qFLAwE3sQgQO5PEL+DJmn9VpqYxW7ujWqypOgv SRFrEK4IkYwYcrQSVYVpdZyynw163vlOh2qv4cHcMmxWkojKIeSrpsrxc13CndztAO EDWWNA7nvxDsYGAxW0IOKWxq7S3E+8/cV0OLh5Ehj5/XskASIiV1w4RNcqqNWs/31u WY8q5uxsB6ch/bCuMWP6ZDQnuifHYj6zXndMSfeu38QkSPTW71cgLsdtk43eW+2p+i d7fB78QwN1GfA== From: Kalle Valo To: Linus Walleij Cc: Konrad Dybcio , Alvin =?utf-8?Q?=C5=A0iprag?= =?utf-8?Q?a?= , Hector Martin , "~postmarketos\/upstreaming\@lists.sr.ht" <~postmarketos/upstreaming@lists.sr.ht>, "martin.botka\@somainline.org" , "angelogioacchino.delregno\@somainline.org" , "marijn.suijten\@somainline.org" , "jamipkettunen\@somainline.org" , Arend van Spriel , Franky Lin , Hante Meuleman , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Marek Vasut , "Zhao\, Jiaqing" , "Russell King \(Oracle\)" , Soon Tak Lee , "linux-wireless\@vger.kernel.org" , "brcm80211-dev-list.pdl\@broadcom.com" , "SHA-cyfmac-dev-list\@infineon.com" , "netdev\@vger.kernel.org" , "linux-kernel\@vger.kernel.org" Subject: Re: [PATCH v2] brcmfmac: Add support for BCM43596 PCIe Wi-Fi References: <20220921001630.56765-1-konrad.dybcio@somainline.org> <83b90478-3974-28e6-cf13-35fc4f62e0db@marcan.st> <13b8c67c-399c-d1a6-4929-61aea27aa57d@somainline.org> <0e65a8b2-0827-af1e-602c-76d9450e3d11@marcan.st> <7fd077c5-83f8-02e2-03c1-900a47f05dc1@somainline.org> <20220922133056.eo26da4npkg6bpf2@bang-olufsen.dk> <87sfke32pc.fsf@kernel.org> <4592f87a-bb61-1c28-13f0-d041a6e7d3bf@linaro.org> <87fse76yig.fsf@kernel.org> <87bkov6x1q.fsf@kernel.org> Date: Mon, 28 Nov 2022 13:17:06 +0200 In-Reply-To: (Linus Walleij's message of "Sat, 26 Nov 2022 22:45:33 +0100") Message-ID: <87wn7f5nwt.fsf@kernel.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS 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-wireless@vger.kernel.org Linus Walleij writes: >> >> Instead of a directory path ("brcm/brcmfmac43596-pcie") why not provide >> >> just the chipset name ("brcmfmac43596-pcie")? IMHO it's unnecessary to >> >> have directory names in Device Tree. >> > >> > I think it's common practice to include a full $FIRMWARE_DIR-relative >> > path when specifying firmware in DT, though here I left out the board >> > name bit as that's assigned dynamically anyway. That said, if you don't >> > like it, I can change it. >> >> It's just that I have understood that Device Tree is supposed to >> describe hardware and to me a firmware directory "brcm/" is a software >> property, not a hardware property. But this is really for the Device >> Tree maintainers to decide, they know this best :) > > I would personally just minimize the amount of information > put into the device tree to be exactly what is needed to find > the right firmware. > > brcm,firmware-compatible = "43596"; > > since the code already knows how to conjure the rest of the string. FWIW I like this. > But check with Rob/Krzysztof. Indeed, they are the experts here. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches