Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp353589rwb; Wed, 21 Sep 2022 23:57:38 -0700 (PDT) X-Google-Smtp-Source: AMsMyM67osEyIb8zGzglMhzWRcvGs+l1YCTd8R8mVp258e+oDqibyTNDOdDFMqzKyM0cvX6moVPE X-Received: by 2002:a17:906:6a23:b0:782:e8:1b7d with SMTP id qw35-20020a1709066a2300b0078200e81b7dmr1532901ejc.127.1663829858648; Wed, 21 Sep 2022 23:57:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1663829858; cv=none; d=google.com; s=arc-20160816; b=NHKKQdRDmjIIhKVV8xQQBE/7YeodaF8ZJ50msR8z6VdgJXS2DfQdVdQw/3J1xkK94b 0/He6r9MXpIyhG2G+IvWHKS1zbfMF/QHZ0z96jbbqn8eoltKCkVgOdTeIf/HMJ4EpWfb QcLIiSfDDN5uqLEAYFe3I8hyCPZXoFcqZ61ze96pPzToiBZ+1OGVa1799DAXFk7L/y+e O4KwwDz3xb8veg3VsuutWyHaha18k3YGWjWY5gx27n+4tpY/fgajllTgfVDnRk+/RDoV 7Ji4i5DRuyTjmgTxTUgZgnduw14sANbu9plxsMReEep2ZynthEdhqCSffqp1GBOyFjO7 H7Nw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=5dBg3QwijXxmS8htwrStvKzirwE+EJnXtHqQ1fYKvUA=; b=A6KNOou4fK8iKqwMvlVJ5U6m0zNMkR90X5KsCJ0eYPSsG65sJ5zSRcsIQm8UbzepkG zp4zTDncjlBCUPR3F+hXMlCzVglt3kQjfM6p3EhKr2LQ6Wo71FRHjzVjRegBQ2+m2LZp ae4XZ7AxL8lvQjsBu8NZDznLHJllwPVIK1tlFKhbIc/dKQUboGShBVEGBz7AL/pU6+fi 7RgMH8BxPAHlEXeDxs57SM96j4ayaV2JG72g11GfCEdvvvNjkFTbAhyXgSj30WQoHxpD bE4Ltd2Rl1mJN8xdtmn5hutRSZewOVxcHML6FQ9JbqO+Bv/R6XOJkO3d27uJ92T7uegf rVmw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@marcan.st header.s=default header.b=AlnToHb5; 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=QUARANTINE sp=QUARANTINE dis=NONE) header.from=marcan.st Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id ia24-20020a170907a07800b00730ac298aa9si4046179ejc.783.2022.09.21.23.57.14; Wed, 21 Sep 2022 23:57:38 -0700 (PDT) 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=@marcan.st header.s=default header.b=AlnToHb5; 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=QUARANTINE sp=QUARANTINE dis=NONE) header.from=marcan.st Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230150AbiIVGki (ORCPT + 63 others); Thu, 22 Sep 2022 02:40:38 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50054 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230146AbiIVGkg (ORCPT ); Thu, 22 Sep 2022 02:40:36 -0400 Received: from mail.marcansoft.com (marcansoft.com [212.63.210.85]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8FD64ACA04; Wed, 21 Sep 2022 23:40:33 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: marcan@marcan.st) by mail.marcansoft.com (Postfix) with ESMTPSA id A8F6A421F5; Thu, 22 Sep 2022 06:40:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=marcan.st; s=default; t=1663828830; bh=RUtAZh/7J9hREx8V838cymaf7DD2ZOmGvoVfMJ8076s=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=AlnToHb5BLNHhdvff9SumZZMkfvnhvQesYbDKVSPPPRSSuip0hezSHHlfH3oeFiKm kCX6w3T1Kh7gj8lalEwr15IpCM9snownzy3zK2CPR8ltVzkAM5Hh7PdmexfbFZvQJM IjZZMQUQ9TQoBGQEN2UK4EFgMOctaofv68orYtnNtnhCGvtwvn3GVyOkRi9BE4PJJ1 Bk6+vThOD/gSV60KreK6ObkxXhnwgwEtbDvye3k0J5oh47GMYOQxaRUzT51kCjoZsr 5G2R7SuAVHmG3iJJPdX9KAJAh96mzmE1g9ComRCeqDxPx0o3q12PHLU6XhdaT3M5RR bCmwu2cnV2/og== Message-ID: <0e65a8b2-0827-af1e-602c-76d9450e3d11@marcan.st> Date: Thu, 22 Sep 2022 15:40:20 +0900 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Subject: Re: [PATCH v2] brcmfmac: Add support for BCM43596 PCIe Wi-Fi Content-Language: es-ES To: Konrad Dybcio , ~postmarketos/upstreaming@lists.sr.ht Cc: martin.botka@somainline.org, angelogioacchino.delregno@somainline.org, marijn.suijten@somainline.org, jamipkettunen@somainline.org, Arend van Spriel , Franky Lin , Hante Meuleman , Kalle Valo , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Linus Walleij , =?UTF-8?Q?Alvin_=c5=a0ipraga?= , Marek Vasut , "Zhao, Jiaqing" , "Russell King (Oracle)" , Soontak 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 References: <20220921001630.56765-1-konrad.dybcio@somainline.org> <83b90478-3974-28e6-cf13-35fc4f62e0db@marcan.st> <13b8c67c-399c-d1a6-4929-61aea27aa57d@somainline.org> From: Hector Martin In-Reply-To: <13b8c67c-399c-d1a6-4929-61aea27aa57d@somainline.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,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 On 22/09/2022 06.26, Konrad Dybcio wrote: > > > On 21.09.2022 06:37, Hector Martin wrote: >> On 21/09/2022 09.16, Konrad Dybcio wrote: >>> Add support for BCM43596 dual-band AC chip, found in >>> SONY Xperia X Performance, XZ and XZs smartphones (and >>> *possibly* other devices from other manufacturers). >>> The chip doesn't require any special handling and seems to work >>> just fine OOTB. >>> >>> PCIe IDs taken from: https://github.com/sonyxperiadev/kernel/commit/9e43fefbac8e43c3d7792e73ca52a052dd86d7e3.patch >>> >>> Signed-off-by: Konrad Dybcio >>> --- >>> Changes since v1: >>> - rebased the patch against -next >>> >>> drivers/net/wireless/broadcom/brcm80211/brcmfmac/chip.c | 2 ++ >>> drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c | 4 ++++ >>> drivers/net/wireless/broadcom/brcm80211/include/brcm_hw_ids.h | 4 ++++ >>> 3 files changed, 10 insertions(+) >>> >> [...] >>> diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c >>> index f98641bb1528..2e7fc66adf31 100644 >>> --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c >>> +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c >>> @@ -81,6 +81,7 @@ static const struct brcmf_firmware_mapping brcmf_pcie_fwnames[] = { >>> BRCMF_FW_ENTRY(BRCM_CC_43570_CHIP_ID, 0xFFFFFFFF, 43570), >>> BRCMF_FW_ENTRY(BRCM_CC_4358_CHIP_ID, 0xFFFFFFFF, 4358), >>> BRCMF_FW_ENTRY(BRCM_CC_4359_CHIP_ID, 0xFFFFFFFF, 4359), >>> + BRCMF_FW_ENTRY(BRCM_CC_43596_CHIP_ID, 0xFFFFFFFF, 4359), >> >> So this works with the same firmware as 4359? That sounds a bit off. Is >> that really the case? >> >> brcmfmac4359-pcie isn't in linux-firmware, but presumably there is >> *some* semi-canonical firmware you can find for that chip that other >> people are already using. If that works on 43596 *and* you plan on using >> that firmware or some other firmware marked 4359, then this is fine. If >> you are using separate firmware that shipped with a 43596 device and >> isn't itself marked 4359, please make it a separate firmware entry. We >> can always symlink the firmwares if it later turns out there is no >> reason to have different ones for each chip. > The firmware that SONY originally gave us for the devices that we know use > this chip seems to be marked 4359 [1]. That said, I have no other info > about the relation between the two models. > > [1] https://github.com/sonyxperiadev/device-sony-kagura/tree/q-mr1/rootdir/vendor/firmware That link seems to have the nvram file and Bluetooth firmware, but not WLAN firmware. I think if you run `strings` on the WLAN firmware you'll get a build ID with the chip name in it, that might be a good indication of what the firmware name should be. I would suggest trying to find some other 4359 firmware and testing your device with it. If it works, then it's definitely fine to use the same firmware name. If it doesn't, then you might need different firmware names, or it might just be a case for board-specific firmwares. - Hector