From: Christian Hewitt <christianshewitt@gmail.com>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
brcm80211-dev-list@cypress.com, Wright.Feng@cypress.com,
Neil Armstrong <narmstrong@baylibre.com>,
Christoph Muellner <christoph.muellner@theobroma-systems.com>
Subject: Re: [RESEND] brcmfmac support for BCM4359 sdio on arm64 ??
Date: Mon, 24 Jun 2019 19:45:41 +0400 [thread overview]
Message-ID: <30516339-BAD7-40F4-980B-D30CDF504A08@gmail.com> (raw)
In-Reply-To: <37d2964d-1c2b-51bd-ac98-2cc171aa0c9c@broadcom.com>
On 11 Jun 2019, at 1:45 pm, Arend Van Spriel <arend.vanspriel@broadcom.com> wrote:
>
> The splat could be relevant. Maybe try the patch below to get actual values that are checked in the WARN_ON.
>
>> BCMDHD is also reported working with commits here: https://gitlab.com/baylibre/amlogic/atv/linux/commits/narmstrong/v5.1/aml/integ-5.1-bcmdhd but LibreELEC needs to support many different boards (with many different SDIO modules) from a single OS image, so BCMDHD is not the solution we need.
>> One additional patch I spotted mentioning BCM4359 (also from Wright Feng) was https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/65f17112e1c883d3c9f3fa68837e5f9b5eb7cfad/patches/cypress/v4.14.52-2018_0928/cypress-patch/0073-non-upstream-reset-two-D11-cores-if-chip-has-two-D11.patch but it makes no difference (the dmesg log above is with this patch applied).
>> I don’t write code but am happy to build test kernels with suggested patches or explicit instructions. I’ve also CC’d LibreELEC colleague and linux-amlogic maintainer Neil Armstrong who can assist. NB: If direct access to hardware would help progress things I can easily organise remote access or get board samples shipped.
>> How can we resume the investigation?
>
> Let's try one step at a time ;-)
>
> Regards,
> Arend
> ---
> diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c b/driver
> index fc12598..e9b0986 100644
> --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c
> +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c
> @@ -772,7 +772,8 @@ void brcmf_sdiod_sgtable_alloc(struct brcmf_sdio_dev *sdiod
> sdiodev->settings->bus.sdio.txglomsz);
> nents += (nents >> 4) + 1;
>
> - WARN_ON(nents > sdiodev->max_segment_count);
> + WARN(nents > sdiodev->max_segment_count, "max_seg_cnt=%u, host_max_seg=
> + sdiodev->max_segment_count, host->max_segs, nents);
>
> brcmf_dbg(TRACE, "nents=%d\n", nents);
> err = sg_alloc_table(&sdiodev->sgtable, nents, GFP_KERNEL);
> q
^ this patch is mangled - please send me the correct one so I can reply with information to move things forwards. Thanks.
Christian
next prev parent reply other threads:[~2019-06-24 15:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 3:39 [RESEND] brcmfmac support for BCM4359 sdio on arm64 ?? Christian Hewitt
2019-06-11 9:45 ` Arend Van Spriel
2019-06-12 8:22 ` Christian Hewitt
2019-06-24 15:45 ` Christian Hewitt [this message]
2019-06-24 19:04 ` Arend Van Spriel
2019-06-30 17:06 ` Christian Hewitt
2019-11-21 3:52 ` Christian Hewitt
2019-11-21 9:00 ` Arend Van Spriel
2019-11-21 12:01 ` Christian Hewitt
[not found] ` <096CB8E8-5D24-4EEF-B283-746D6AA7C105@gmail.com>
2019-12-12 9:07 ` Arend Van Spriel
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=30516339-BAD7-40F4-980B-D30CDF504A08@gmail.com \
--to=christianshewitt@gmail.com \
--cc=Wright.Feng@cypress.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=christoph.muellner@theobroma-systems.com \
--cc=linux-wireless@vger.kernel.org \
--cc=narmstrong@baylibre.com \
/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