On 04-08-2021 11:35, Linus Walleij wrote:
On Wed, Aug 4, 2021 at 10:48 AM Arend van Spriel
<arend.vanspriel@xxxxxxxxxxxx> wrote:
Right. I didn't get to looking at this earlier, but indeed the check
whether the requested firmware exists is done in another thread context
so the return value here only indicates whether the firmware request
could be scheduled or not.
I think my recent patch fixes is, please have a look.
Right. I want to explore another option for myself, but I will first
look at your patch so we can fix the current issue in timely manner.
My first reaction to the patch was to reject it, but leaning towards
supporting this now. OEMs tend to get tailor-made firmware in terms of
features. Depending on their requirements they get their mix of firmware
features. That such difference lead to a crash in 3d engine is somewhat
surprising. I am curious if we can debug this more and learn how a
firmware variant could cause such a crash. Maybe some DMA issue?
I am not certain what happens, but I think the 3D engine misses its
interrupts. This may in turn be because GPIO IRQs are held
low or fireing repeatedly for an extensive period of time, stressing
the system to the point that other important IRQs are missed.
This in turn can be caused by the wrong (non-custom) firmware
managing these GPIO IRQs fireing left and right.
I have noticed that the config files for brcmfmac contain words
about GPIOs and so on and that is what makes me think this way.
Not sure what config files you refer to. I am only aware of the device
tree bindings mentioning GPIO for out-of-band SDIO interrupt.
I can tell for sure that brcmfmac has definately had special
firmware tailored by/for Samsung for these phones. We can just
look at the files extracted from the platforms (the original
files are named bcmdhd_sta.bin_b2 or similar):
BRCMFMAC 4330
-rw-r--r--. 1 linus linus 213390 Mar 22 23:32
brcmfmac4330-sdio.samsung,janice.bin
-rw-r--r--. 1 linus linus 203593 Jul 11 01:53
brcmfmac4330-sdio.samsung,codina.bin
-rw-r--r--. 1 linus linus 212956 Mar 22 23:31
brcmfmac4330-sdio.samsung,gavini.bin
BRCMFMAC 4334
-rw-r--r--. 1 linus linus 346151 Mar 16 22:53
brcmfmac4334-sdio.samsung,golden.bin
-rw-r--r--. 1 linus linus 434236 Jul 7 00:43 brcmfmac4334-sdio.samsung,kyle.bin
-rw-r--r--. 1 linus linus 434236 Mar 16 22:54
brcmfmac4334-sdio.samsung,skomer.bin
All different file sizes, except Kyle and Skomer, who actually share
the same firmware. (Those were the two last phones produced
in this series BTW.) Doing strings * on each file reveals that they
were compiled at different dates around the time these phones
were produced.
As said earlier customers get their mix of firmware features. Apart from
the compile date using strings will also give you the firmware compile
target, ie. 4330*-roml/... Could you share that?
These are all for standard WiFi functionality. There is two more
firmwares for each phone, one for the access point usecase and
one more which I don't know what it is for, the actual set of firmware
for each phone is for example (Skomer):
bcmdhd_apsta.bin_b2
bcmdhd_mfg.bin_b2
bcmdhd_p2p.bin_b2
bcmdhd_sta.bin_b2
So I am half-guessing that bcmdhd_sta.bin_b2 is obviously for the
ordinary use case, *mfg* is probably for manufacturing, *apsta*
for mobile hotspot (access point) and *p2p* for some other cool
Half-guessing seems sufficient ;-) If I recall correctly on Android the
driver loads different firmware based on what a user selects in the gui.
Not something we do in upstream linux. p2p is a WFA specification and
supported in upstream linux cfg80211. Many TV sets support it to show
content from your portable device.
Regards,
Arend
