From: Arend van Spriel <arend@broadcom.com>
To: "Jörg Krause" <joerg.krause@embedded.rocks>
Cc: Arend van Spriel <aspriel@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
brcm80211-dev-list <brcm80211-dev-list@broadcom.com>
Subject: Re: brcmfmac: Failed to create interface p2p-dev-p2p0: -28 (No space left on device)
Date: Tue, 23 Jun 2015 14:08:32 +0200 [thread overview]
Message-ID: <55894C40.1070108@broadcom.com> (raw)
In-Reply-To: <1435059083.4765.2.camel@embedded.rocks>
[-- Attachment #1: Type: text/plain, Size: 648 bytes --]
On 06/23/15 13:31, Jörg Krause wrote:
> Hi Arend,
>
> On So, 2015-06-21 at 23:18 +0200, Arend van Spriel wrote:
>>
>> My bad. The patch removes p2pdev from interface modes, but it is
>> still
>> listed in the interface combinations and cfg80211 will complain about
>> it. Have to extend the patch. I better do that after a good nights
>> sleep.
>
> Never mind! Did you had a good night sleep already :-) ?
Several ;-) Did not get to this earlier. Thanks for the reminder.
Had a closer look at wiphy_verify_combinations() and I am hopeful the
attached patch will fix the wiphy_register() failure.
Regards,
Arend
> Best regards
> Jörg Krause
[-- Attachment #2: 0001-brcmfmac-no-p2pdev-limit-needed-when-p2pon-1-is-used.patch --]
[-- Type: text/plain, Size: 1148 bytes --]
From f490a7cdb2a754ac79af9d9082b8526812164d4f Mon Sep 17 00:00:00 2001
From: Arend van Spriel <arend@broadcom.com>
Date: Tue, 23 Jun 2015 13:59:23 +0200
Subject: [PATCH] brcmfmac: no p2pdev limit needed when p2pon=1 is used
Avoid failure upon wiphy_register() by not providing the limit
for iftype P2P_DEVICE.
Signed-off-by: Arend van Spriel <arend@broadcom.com>
---
drivers/net/wireless/brcm80211/brcmfmac/cfg80211.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/net/wireless/brcm80211/brcmfmac/cfg80211.c b/drivers/net/wireless/brcm80211/brcmfmac/cfg80211.c
index 10eaabf..ffa9aca 100644
--- a/drivers/net/wireless/brcm80211/brcmfmac/cfg80211.c
+++ b/drivers/net/wireless/brcm80211/brcmfmac/cfg80211.c
@@ -5802,6 +5802,10 @@ static int brcmf_setup_wiphy(struct wiphy *wiphy, struct brcmf_if *ifp)
ifc_combo.n_limits = ARRAY_SIZE(brcmf_iface_limits_mbss),
ifc_combo.limits = brcmf_iface_limits_mbss;
}
+ /* don't give p2pdev limit when p2pon is set */
+ if (ifp->drvr->iflist[1])
+ ifc_combo.limits--;
+
wiphy->iface_combinations = kmemdup(&ifc_combo,
sizeof(ifc_combo),
GFP_KERNEL);
--
1.9.1
next prev parent reply other threads:[~2015-06-23 12:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 12:35 brcmfmac: brcmf_p2p_create_p2pdev: timeout occurred Jörg Krause
2015-06-08 12:41 ` Arend van Spriel
2015-06-08 12:56 ` Jörg Krause
2015-06-08 13:48 ` Jörg Krause
2015-06-08 16:46 ` Arend van Spriel
2015-06-08 20:17 ` Jörg Krause
2015-06-08 21:14 ` Arend van Spriel
2015-06-08 21:19 ` Jörg Krause
2015-06-16 9:59 ` brcmfmac: Failed to create interface p2p-dev-p2p0: -28 (No space left on device) Jörg Krause
2015-06-16 14:26 ` Arend van Spriel
2015-06-18 6:13 ` Jörg Krause
2015-06-18 8:27 ` Arend van Spriel
2015-06-18 20:07 ` Jörg Krause
2015-06-21 21:18 ` Arend van Spriel
2015-06-23 11:31 ` Jörg Krause
2015-06-23 12:08 ` Arend van Spriel [this message]
2015-07-07 7:47 ` Jörg Krause
2015-07-23 11:05 ` Jörg Krause
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=55894C40.1070108@broadcom.com \
--to=arend@broadcom.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=joerg.krause@embedded.rocks \
--cc=linux-wireless@vger.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).