linux-kernel - Re: RTL8723BS driver doesn't work for,me but I can help testing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAFBinCCpVCLHQ6TPegKjy+32nKGbJKKeQyjCSgnCNBMDgs2kpg@mail.gmail.com>
Date:   Tue, 26 May 2020 22:13:46 +0200
From:   Martin Blumenstingl <martin.blumenstingl@...glemail.com>
To:     Tobias Baumann <017623705678@...nline.de>
Cc:     hdegoede@...hat.com, Larry.Finger@...inger.net,
        gregkh@...uxfoundation.org, devel@...verdev.osuosl.org,
        linux-kernel@...r.kernel.org
Subject: Re: RTL8723BS driver doesn't work for,me but I can help testing

Hi Tobias,


On Thu, May 21, 2020 at 1:17 PM Tobias Baumann <017623705678@...nline.de> wrote:
[...]
>>> with my patch and oleg RC5 hotstart(shutdown now)  do not work with my
>>> box ( wlan goes back to sleep mode always)
>>
>> I'm not sure what you mean here.
>> if you run "shutdown now" then the system does not shut down and only
>> wifi goes to sleep mode?
>
> i meant  that after a reboot with "shutdown now" my box restart but the wifi chip is back in sleep mode ,  while the wifi chip was online befor the restart .
I don't know how sleep mode is controlled (some GPIO or through SDIO
communication) so I can't comment on that

[...]
>  i read also the AP6330 and BCM4330 Datasheet  for both of them is a start order inside the datashet ( i think that RTL8723BS should have same timming) . the time between 32k clock and WLAN_dis should be more than minimum 2 clock cycle (1/32kHZ * 2cycle = 0.06ms )
>
> also that AP6330 has most identical  pinout as RTL8723BS ( i did not get the pinout of BCM4330 because datasheet only has information to the chip and not the small extra pcb where the chip is mount)
I don't have any additional comments on this one

> on Android 4.4 my box told me that GPIOAO_6 ist chip enable and GPIOX_11 ist wlan enable
>
> mybe a clue is that in the HArdkernel S805 Datasheet the GPIOAO_6 is also a 32k clock  output (site 42 table 10 Func1 maybe  (but i also found some Dts file from old S805 RTL8723bs box they use only GPIOX_11 and powerPin2 was comment out )
do you have an oscilloscope or does your multimeter support frequency
measurements (based on what I understand it would only have to be
capable of measuring 32kHz)?
then you can prove or refute this :-)

> i have another question , do we use the same wifi.c file for the meson8m2 boxes as for endless mini ? i have taken a closer look at the file and the two delay information you are mention are not  in the wifi. c is neither a function nor an instance, it just takes two fixed values "mdelay(200)" line 156 , furthermore we ignore the output level of wifi_power_gpio2 and automatically set it to "1" line 378 , so it is important which of the two pins is passed to the header file first (translate with DEEPL)
Endless Mini has the CHIP_EN signal hard-wired to 3.3V
This is the .dts from the Endless Mini:
https://github.com/endlessm/linux-meson/blob/d628bf1242928927a41f7482ba5ef7295e01a9ff/arch/arm/boot/dts/meson8b-ec100.dts

[...]
> You are right the chip has only wifi wake host and that should be GPIOX_21 as input ; maybe on your box the pin is alway high  on the board  ( direkt an 3.3V verdrahtet)
on the Endless Mini GPIOX_21 is also WIFI_WAKE_HOST
I haven't tested any reboot / shutdown / etc. cycles with RTL8723BS
there yet because I typically use the sdio controller to access the
internal SD card (and at the time of writing the MMC subsystem in
Linux doesn't support two different cards with one MMC controller). So
only because of your email I did a quick test on the Endless Mini.


Best regards,
Martin