From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: Chen-Yu Tsai <wens@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Scott Branden <sbranden@broadcom.com>,
Eric Anholt <eric@anholt.net>, Stephen Boyd <sboyd@kernel.org>,
Ray Jui <rjui@broadcom.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-mmc@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Christoph Hellwig <hch@lst.de>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
"open list:BROADCOM BCM281XX..."
<bcm-kernel-feedback-list@broadcom.com>,
Matthias Brugger <mbrugger@suse.com>,
"moderated list:BROADCOM BCM2835..."
<linux-rpi-kernel@lists.infradead.org>,
Michael Turquette <mturquette@baylibre.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Stefan Wahren <wahrenst@gmx.net>
Subject: Re: [PATCH 00/18] ARM: Add minimal Raspberry Pi 4 support
Date: Wed, 24 Jul 2019 10:37:45 +0200 [thread overview]
Message-ID: <ab7af8537ebcbc7a7bdf04d2c06152ba6821b333.camel@suse.de> (raw)
In-Reply-To: <CAGb2v66-o23CW5iH9Bn1aELymPSiKrA43eJd2q6EZ7iubcogaw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 909 bytes --]
> > > Does it fix the wifi issue too?
> >
> > Well it works as long as I revert this: 901bb98918 ("nl80211: require and
> > validate vendor command policy"). Which has nothing to do with DMA anyways.
> >
> > Was this the issue you where seeing?
> >
> > [ 4.969679] WARNING: CPU: 2 PID: 21 at net/wireless/core.c:868
> > wiphy_register+0x8e8/0xbdc [cfg80211]
> > [...]
> > [ 4.969974] ieee80211 phy0: brcmf_cfg80211_attach: Could not register
> > wiphy device (-22)
>
> We're seeing this on different platforms (allwinner / rockchip / amlogic)
> with Broadcom WiFi chips. So it's unlikely to be related with anything in
> this series.
>
> I believe a fix for this has already been queued up:
>
>
https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git/commit/?id=91046d6364afde646734c7ead1f649d253c386e9
Thanks for pointing it out, it fixes the issue alright.
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-07-24 8:37 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 5:54 [PATCH 00/18] ARM: Add minimal Raspberry Pi 4 support Stefan Wahren
2019-07-22 5:54 ` [PATCH 01/18] ARM: bcm283x: Reduce register ranges for UART, SPI and I2C Stefan Wahren
2019-07-24 20:01 ` Stefan Wahren
2019-07-22 5:54 ` [PATCH 02/18] ARM: bcm2835: DMA can only address 1GB Stefan Wahren
2019-07-22 5:54 ` [PATCH 03/18] ARM: dts: bcm283x: Move BCM2835/6/7 specific to bcm2835-common.dtsi Stefan Wahren
2019-07-22 17:54 ` Eric Anholt
2019-07-22 5:54 ` [PATCH 04/18] ARM: dts: bcm283x: Define MMC interfaces at board level Stefan Wahren
2019-08-12 21:03 ` Stefan Wahren
2019-07-22 5:54 ` [PATCH 05/18] ARM: dts: bcm283x: Define memory " Stefan Wahren
2019-08-12 21:02 ` Stefan Wahren
2019-07-22 5:54 ` [PATCH 06/18] dt-bindings: bcm2835-cprman: Add bcm2711 support Stefan Wahren
2019-07-22 5:54 ` [PATCH 07/18] clk: bcm2835: Introduce SoC specific clock registration Stefan Wahren
2019-07-22 10:30 ` Matthias Brugger
2019-08-11 20:43 ` Stefan Wahren
2019-07-22 5:54 ` [PATCH 08/18] clk: bcm2835: Add BCM2711_CLOCK_EMMC2 support Stefan Wahren
2019-07-22 10:30 ` Matthias Brugger
2019-07-22 5:54 ` [PATCH 09/18] dt-bindings: sdhci-iproc: Add brcm,bcm2711-emmc2 Stefan Wahren
2019-07-22 10:31 ` Matthias Brugger
2019-07-24 14:08 ` Ulf Hansson
2019-07-22 11:26 ` [PATCH 00/18] ARM: Add minimal Raspberry Pi 4 support Matthias Brugger
2019-07-22 13:18 ` Nicolas Saenz Julienne
2019-07-22 18:10 ` Stefan Wahren
2019-07-23 9:34 ` Christoph Hellwig
2019-07-23 13:32 ` Nicolas Saenz Julienne
2019-07-23 14:33 ` Christoph Hellwig
2019-07-23 16:26 ` Stefan Wahren
2019-07-23 17:33 ` Nicolas Saenz Julienne
2019-07-23 21:30 ` Stefan Wahren
2019-07-24 2:53 ` Chen-Yu Tsai
2019-07-24 8:37 ` Nicolas Saenz Julienne [this message]
[not found] ` <3daef629-8baf-3c5c-16a4-73d67604d1e5@gmx.net>
2019-07-29 5:44 ` brcmfmac: Probing regression in Linux 5.3-rc1 Stefan Wahren
2019-07-25 8:22 ` [PATCH 00/18] ARM: Add minimal Raspberry Pi 4 support Nicolas Saenz Julienne
2019-07-25 22:09 ` Stefan Wahren
2019-07-22 18:01 ` Eric Anholt
2019-07-28 11:22 ` Stefan Wahren
2019-08-05 9:33 ` Linus Walleij
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=ab7af8537ebcbc7a7bdf04d2c06152ba6821b333.camel@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=adrian.hunter@intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=hch@lst.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mbrugger@suse.com \
--cc=mturquette@baylibre.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sbranden@broadcom.com \
--cc=ulf.hansson@linaro.org \
--cc=wahrenst@gmx.net \
--cc=wens@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).