Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp666528ybl; Thu, 12 Dec 2019 03:00:26 -0800 (PST) X-Google-Smtp-Source: APXvYqxoH6YR6flngEItmObQMkQIxOGFEBDWiG7QmV9T0MFxfste6cBMfxfCPuVyzot1lIFTJTP2 X-Received: by 2002:a9d:7:: with SMTP id 7mr6976393ota.26.1576148426301; Thu, 12 Dec 2019 03:00:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576148426; cv=none; d=google.com; s=arc-20160816; b=bKZqpu6gRu12WglRpW2/8ZfbbkE9i4oz0oGdGaNZ4b4jNvQlHk35Bnwp/E/Q93E82y SkMJJ0WkmC0kX+Ck9wQU2x+4ge9YdZi8x3yYwOdIrpgqZaBJOOMq3tb3x52pRGndwIu7 U28GwgyuR64pB8M51BJkbhHfIXCaliIjAuVh1PQvihnN4hQk5Uz+OSAy/OBvT5MaR6YF H+HCJk9qmptMYpsEu+JsiI8r1ikp2XJ/+OBydEyKvj+o219HYNxl+HLtR3P7ztBnsuaA bJciEFz159gYK0DZ4WIN6XSOU8qTjYsSH4lb2xELUyc7aahc/o0H5Bryte0mHSdrdDmR 2Nlw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=H6VJj7h6Vg1/JX7xb9gep9oR4+dQ7Pdj1Ol1gyoq+gE=; b=svH/A+MJtDq4hX3a7QI29hwC1C17G15NgExkYdhotxWBisXnnwLwlWmcmkexBMdBWF NXUX90bv6znTnJEx2NDUOc7izgjERhp0mpCOEFJ6Xl363UPOl6TQBQJJX5ftXb64fihB gLADidacGFLIO7vw03h62pmgSZLRx44ahSSHj3ttvke3qjDUUqaB/8fjsX4kUHzS21bI i3g3Bz7wqZBSaR7oAEQsLFLjaE+gLH+BWWmkALQBVmvkVYrqwqHCWIsRF5WwBFkxHuXa 0S7bKS2mU85+UwNJR2PP252KpF7FzCYrU1mXdHkkfGsZRIlKAktuC6iQuDbz3Q7ZzR10 2ihg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@web.de header.s=dbaedf251592 header.b=aA2fwg0b; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w26si2669825otl.213.2019.12.12.03.00.12; Thu, 12 Dec 2019 03:00:26 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@web.de header.s=dbaedf251592 header.b=aA2fwg0b; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728937AbfLLK7c (ORCPT + 99 others); Thu, 12 Dec 2019 05:59:32 -0500 Received: from mout.web.de ([217.72.192.78]:42053 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728777AbfLLK7b (ORCPT ); Thu, 12 Dec 2019 05:59:31 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=dbaedf251592; t=1576148357; bh=keZMm0sbIdLHuKg2ERn1DL+jHDL/cWURqxHw0Hu/p0A=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=aA2fwg0bcpAURby5zURwZamBbgaMsktdVD6saMWtZuaoSVSoxO+4Pyc/8/4jwG2BV 1ejH7AznNmia67ny1h1ssx6Z01fXY6xjLka1D3VvwWmLBWQBKtVZPYE+UNnwhMb01M aznF098xbi3gBtnkhRv3JV/5OHkbvFg4yxJQnTPM= X-UI-Sender-Class: c548c8c5-30a9-4db5-a2e7-cb6cb037b8f9 Received: from [192.168.43.108] ([89.204.139.166]) by smtp.web.de (mrweb101 [213.165.67.124]) with ESMTPSA (Nemesis) id 0M3Bhz-1hpaVu0SM3-00szdL; Thu, 12 Dec 2019 11:59:17 +0100 Subject: Re: [PATCH v2 0/9] brcmfmac: add support for BCM4359 SDIO chipset To: Kalle Valo Cc: brcm80211-dev-list.pdl@broadcom.com, Heiko Stuebner , netdev@vger.kernel.org, linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org, brcm80211-dev-list@cypress.com, linux-arm-kernel@lists.infradead.org References: <20191211235253.2539-1-smoch@web.de> <0101016ef97cf6b5-2552a5e4-12de-4616-94d6-b63d9c795ed6-000000@us-west-2.amazonses.com> From: Soeren Moch Message-ID: <1daadfe0-5964-db9b-818c-6e4c75ac6a69@web.de> Date: Thu, 12 Dec 2019 11:59:13 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1 MIME-Version: 1.0 In-Reply-To: <0101016ef97cf6b5-2552a5e4-12de-4616-94d6-b63d9c795ed6-000000@us-west-2.amazonses.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-GB X-Provags-ID: V03:K1:X1VXSbz0SVvWmuA9nSQSUNDgrZCFbxASzXxbWmYUVAixHdeM2ap 5jmIj84J8M/PXs/xv2KPflfJqUt1QNjJv5GJgJoLMLXyLiCjk0/Q3dLXeNg9mRE5SgJDMrp lMtjGHcpWNZZDPCuLLeuS1tRI3rHa+cB30xT2NU+YYo77xPbDHOD+6iyqP03+Hh+I890Zym DY/WgF90Ef1JOL5NUpYVA== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:nlKbbsRR7i0=:E+Q+EdeHtqjknVu7hYEK3S euzrTVn88dNTLxE8S8Bmf9etZpvuQ+ug2P/QlYtYWAvl6n5LeLFWYDUeZP8pMmhaW7kqTgs3V lT4dRgdn+ljCmrzCfjae5wbBHgUiv94nXEYCLSyRbUNi0w9+hMrjcobzp0HP8SZ3BaHb/Y/bS p1M8vXBKf3J17rBwRBwldk++//LFDOwBMSH1NJ1dl8wVua+01mQftvDogUSvv9JjSS7f/3URL Q6NNd7m+Umlw4wjz3wBbUDrFis01Cx6GzsDc/CVo0oNcUctbNrkFtmrbrNhcP32+zgg0SJsDR KjRIASeSNRRQKvnUhdNpwDvGaxz0d67FjGG9tg9L6T0wri4W+osqi7/S7CVq6P6ilteV9EY5j Joh3ig7b0psa4p8iR0vdKRjujfAtljo2MvB9JySRM6g6Jzy6p/4mBL2TswUxHssyzVdJhadEr VOnFagxMXcJD6/Bt6qkqk1sc4VBXHLE+y7mUvlcq8X1yxEE+GP1IWTOEHyFpJQVlgcxHf/bH4 ezYtSPRp/55TUrUQsEULFDJIBHwKtLN0n2nWB2rc0xL1vDkVWCUGIiqtWUJlCQbvmxradRvzf 3IhC9nMdlUiwiq1J4IrSYRrI05627W4XAqLE9sCyQjbXTxaXvuiif5sQJYARAM46Qw8Pu8hQR q3ota1qXM6Vim/0XSoZGFcX0puCW+hfgx3ih4lat3dZhzbycUMyG/ZUg6AcEs9BAQAlAjB4/r qPYF5YDnohZEXMHPsLhIS14+NFQSPr9K5JzQZdix4QrggGcD1nU+RBXrKvzPuJuSz/Ybf8Bng OUCNE3nwUMqKDKMqwPPyONgbRFxmnsXYxBXSNlEZhQNzyQmpBWTzuMJyxgdxpcRGgWLhErbf3 E17Z5TA64ZVTUX7PByWYChmwPpkDvVvJGdLGIw76hrdxs18tLy/57MY4TWunoefJS2TMplt15 DGNeV1Bdaee9swC9w1PWtu03rqkXFIz2g1T0XDwqpxW6BnzbGdG3/xjCKiutsAEmKPfFvr71g egloZRpK3i3UQ1CEJn39vavZWYF/sxNfCwvz1OHafER/+PYgKcGXhZxgvj0xMTTiw/u+GQWuo sQvb15A1OdGWKK+cwMPCVOdWDSZc/XjeKojhCrY2891siO4IVsFQA24CScAYCM1YLSG+CVO47 IPuicuo1OFqGIe23wysjRGfQsXbfw1Tm9KiqGCTFrymq0rv6+ZAnb+WDhf96GNsGKctmuxT7C lsN0L8y2/vEhLWXhXuLVXJE2s7y783NfGiXTdYQ== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12.12.19 10:42, Kalle Valo wrote: > Soeren Moch writes: > >> Add support for the BCM4359 chipset with SDIO interface and RSDB support >> to the brcmfmac wireless network driver in patches 1-7. >> >> Enhance devicetree of the RockPro64 arm64/rockchip board to use an >> AP6359SA based wifi/bt combo module with this chipset in patches 8-9. >> >> >> Chung-Hsien Hsu (1): >> brcmfmac: set F2 blocksize and watermark for 4359 >> >> Soeren Moch (5): >> brcmfmac: fix rambase for 4359/9 >> brcmfmac: make errors when setting roaming parameters non-fatal >> brcmfmac: add support for BCM4359 SDIO chipset >> arm64: dts: rockchip: RockPro64: enable wifi module at sdio0 >> arm64: dts: rockchip: RockPro64: hook up bluetooth at uart0 >> >> Wright Feng (3): >> brcmfmac: reset two D11 cores if chip has two D11 cores >> brcmfmac: add RSDB condition when setting interface combinations >> brcmfmac: not set mbss in vif if firmware does not support MBSS >> >> .../boot/dts/rockchip/rk3399-rockpro64.dts | 50 +++++++++++--- >> .../broadcom/brcm80211/brcmfmac/bcmsdh.c | 8 ++- >> .../broadcom/brcm80211/brcmfmac/cfg80211.c | 68 +++++++++++++++---- >> .../broadcom/brcm80211/brcmfmac/chip.c | 54 ++++++++++++++- >> .../broadcom/brcm80211/brcmfmac/chip.h | 1 + >> .../broadcom/brcm80211/brcmfmac/pcie.c | 2 +- >> .../broadcom/brcm80211/brcmfmac/sdio.c | 17 +++++ >> include/linux/mmc/sdio_ids.h | 2 + >> 8 files changed, 176 insertions(+), 26 deletions(-) > Just to make sure we are on the same page, I will apply patches 1-7 to > wireless-drivers-next and patches 8-9 go to some other tree? And there > are no dependencies between the brcmfmac patches and dts patches? > Yes, this also is my understanding. I'm glad if you are fine with patches 1-7. Heiko will pick up patches 8-9 later for linux-rockchip independently. And if we need another round of review for patches 8-9, I think we don't need to bother linux-wireless with this. Thanks, Soeren