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;
Message-ID: <638afa8e-a393-410c-3182-0d8e9b6da17d@warmcat.com>
Date:   Thu, 17 Nov 2022 12:01:26 +0000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.4.1
Subject: Re: AP6275 / bcm43752 pcie on mainline brcmf
Content-Language: en-US
To:     Arend van Spriel <arend.vanspriel@broadcom.com>,
        Shengyu Qu <wiagn233@outlook.com>
Cc:     franky.lin@broadcom.com, linux-wireless@vger.kernel.org
References: <TY3P286MB26114DD461F50814980453E598029@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM>
 <08416710-655a-c87c-a599-3fe2563f7de4@warmcat.com>
 <18470a1e910.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com>
 <TY3P286MB26115A58795F264893CCB40198029@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM>
 <184720fc920.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com>
 <TY3P286MB26118BD94839F752CADCCF5298079@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM>
 <625f1d5d-e137-7ad7-96b9-92035e87df8b@broadcom.com>
From:   Andy Green <andy@warmcat.com>
In-Reply-To: <625f1d5d-e137-7ad7-96b9-92035e87df8b@broadcom.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk


On 11/17/22 09:23, Arend van Spriel wrote:
> On 11/16/2022 1:25 PM, Shengyu Qu wrote:
>> Got a new version of downstream driver and firmware here: 
>> https://gitlab.com/rk3588_linux/linux/external/rkwifibt/-/tree/linux-5.10-gen-rkr3.4
> 
> Thanks for that. The firmware indeed seems to originate from Synaptics 
> and this module can be found on wifi-alliance product finder:
> 
> https://www.wi-fi.org/product-finder-results?sort_by=certified&sort_order=desc&keywords=ap6275
> 
> We have no known contacts there and they do not seem to have much 
> interest in open-source. In that gitlab repo I see they are providing 
> bcmdhd driver and I assume they consider that sufficient.
> 
> Will see what I can do. First have to think on how to approach this 
> failure to get most out of a debug effort. I do not have the module over 
> here so we would need to go back and forth. The fact that the issue is 
> seen on both SDIO and PCIe is somewhat encouraging.

Yes it seems that at some point with some firmware, SDIO has worked for, 
eg, Angus.  And, it should work well with bchdhd (but that does not seem 
to work for scan for me on v6.1-rc5 uplevel with the firmware load 
changed to use kernel apis; but the firmware has no timeout on bcmdhd). 
So it doesn't feel a million miles away.

I have the hw, and (paid) time to help with debugging this "pair of 
hands" style. I'm also a little familiar with the kernel code and can 
try jiggle things autonomously if you can prompt what is interesting.

-Andy

> Regards,
> Arend