From: Sergey Matyukevich <geomatsi@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 4/4] configs/stm32mp157c-dk2: add support for wifi
Date: Sun, 1 Nov 2020 14:08:56 +0300 [thread overview]
Message-ID: <20201101110856.GA1177156@curiosity> (raw)
In-Reply-To: <20201007144945.1697081-4-shlomi.39sd@gmail.com>
Hello,
> Adding support for wifi for stm32mp157c-dk2 is achieved by using
> another dts which includes the bindings for the wifi module.
> In addition, a txt file for the wifi firmware was added.
> This was copied from the yocto bsp layer of st.
>
> Signed-off-by: Shlomi Vaknin <shlomi.39sd@gmail.com>
> ---
> .../stm32mp157c-dk2/linux.config | 4 +-
> .../overlay/boot/extlinux/extlinux.conf | 2 +-
> .../brcmfmac43430-sdio.st,stm32mp157c-dk2.txt | 59 +++++++++++++++++++
> .../stm32mp157c-dk2/stm32mp157c-dk2-wifi.dts | 32 ++++++++++
> configs/stm32mp157c_dk2_defconfig | 7 ++-
> 5 files changed, 100 insertions(+), 4 deletions(-)
> create mode 100644 board/stmicroelectronics/stm32mp157c-dk2/overlay/lib/firmware/brcm/brcmfmac43430-sdio.st,stm32mp157c-dk2.txt
> create mode 100644 board/stmicroelectronics/stm32mp157c-dk2/stm32mp157c-dk2-wifi.dts
I would suggest to add a kernel patch for stm32mp157c-dk2 dts file
instead of adding custom dts directly. This way no need to modify
extlinux.conf. Besides, patch will be easy to drop as soon as wifi
support is mainlined.
As for WiFi on stm32mp157c-dk2, I have the same problems as mentioned
earlier in this email thread. Firmware is loaded, but times out later on
[8.083508] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000):
clkctl 0x50
[9.130954] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000):
clkctl 0x50
I tried both linux-firmware and murata firmware package. None of them
makes wifi work on my board.
Regards,
Sergey
next prev parent reply other threads:[~2020-11-01 11:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 14:49 [Buildroot] [PATCH v3 1/4] boot/uboot: add stm32 binary format Shlomi Vaknin
2020-10-07 14:49 ` [Buildroot] [PATCH v3 2/4] configs/stm32mp157*: use trusted configuration Shlomi Vaknin
2020-10-12 18:08 ` Bartosz Bilas
2020-10-12 20:11 ` Shlomi Vaknin
2020-10-13 17:29 ` Bartosz Bilas
2020-10-14 17:02 ` Thomas Petazzoni
2020-10-07 14:49 ` [Buildroot] [PATCH v3 3/4] configs/stm32mp157*: bump kernel version Shlomi Vaknin
2020-10-14 17:02 ` Thomas Petazzoni
2020-10-07 14:49 ` [Buildroot] [PATCH v3 4/4] configs/stm32mp157c-dk2: add support for wifi Shlomi Vaknin
[not found] ` <15798cdd-e335-a291-53d4-1ac03d1bbd6c@grinn-global.com>
2020-10-07 19:27 ` Bartosz Bilas
2020-10-07 20:16 ` Shlomi Vaknin
2020-10-08 17:31 ` Bartosz Bilas
2020-10-08 20:45 ` Shlomi Vaknin
2020-10-09 16:49 ` Bartosz Bilas
2020-10-09 19:13 ` Shlomi Vaknin
2020-10-10 15:41 ` Bartosz Bilas
2020-10-10 18:08 ` Shlomi Vaknin
2020-10-10 18:59 ` Shlomi Vaknin
2020-10-10 19:01 ` Bartosz Bilas
2020-10-10 20:48 ` Shlomi Vaknin
2020-10-12 14:49 ` Bartosz Bilas
2020-10-12 17:35 ` Shlomi Vaknin
2020-10-12 18:15 ` Bartosz Bilas
2020-10-14 17:02 ` Thomas Petazzoni
2020-11-01 11:08 ` Sergey Matyukevich [this message]
2020-10-14 17:00 ` [Buildroot] [PATCH v3 1/4] boot/uboot: add stm32 binary format Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201101110856.GA1177156@curiosity \
--to=geomatsi@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox