From: "Arend van Spriel" <arend@broadcom.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
brcm80211-dev-list@broadcom.com,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: linux-next: Tree for Aug 30 (brcmfmac)
Date: Sun, 1 Sep 2013 14:31:41 +0200 [thread overview]
Message-ID: <522333AD.9080004@broadcom.com> (raw)
In-Reply-To: <522238A1.3080008@hauke-m.de>
On 08/31/13 20:40, Hauke Mehrtens wrote:
> On 08/31/2013 08:21 PM, Arend van Spriel wrote:
>> On 08/31/13 19:37, Geert Uytterhoeven wrote:
>>> On Fri, Aug 30, 2013 at 11:12 PM, Randy Dunlap<rdunlap@infradead.org>
>>> wrote:
>>>> This bool kconfig symbol:
>>>>
>>>> config BRCMFMAC_SDIO
>>>> bool "SDIO bus interface support for FullMAC driver"
>>>> depends on MMC
>>>>
>>>> allows BRCMFMAC_SDIO to be y even when MMC=m.
>>>>
>>>> Is there a reasonable solution to this?
>>
>> Actually, BRCMFMAC should be built in same form as the MMC and/or USB,
>> but only when BRCMFMAC_SDIO or BRCMFMAC_USB are selected.
>>
>> So valid combinations are:
>> MMC=m, USB=m, BRCMFMAC_SDIO=y, BRCMFMAC_USB=y => BRCMFMAC=m
>> MMC=m, USB=y, BRCMFMAC_SDIO=y, BRCMFMAC_USB=y => BRCMFMAC=m
>> MMC=y, USB=m, BRCMFMAC_SDIO=y, BRCMFMAC_USB=y => BRCMFMAC=m
>> MMC=m, USB=y, BRCMFMAC_SDIO=y, BRCMFMAC_USB=n => BRCMFMAC=m
>> MMC=m, USB=y, BRCMFMAC_SDIO=n, BRCMFMAC_USB=y => BRCMFMAC=m|y
>> MMC=y, USB=m, BRCMFMAC_SDIO=y, BRCMFMAC_USB=n => BRCMFMAC=m|y
>> MMC=y, USB=m, BRCMFMAC_SDIO=n, BRCMFMAC_USB=y => BRCMFMAC=m
>> MMC=y, USB=y, BRCMFMAC_SDIO=y, BRCMFMAC_USB=y => BRCMFMAC=m|y
>> MMC=y, USB=y, BRCMFMAC_SDIO=y, BRCMFMAC_USB=n => BRCMFMAC=m|y
>> MMC=y, USB=y, BRCMFMAC_SDIO=n, BRCMFMAC_USB=y => BRCMFMAC=m|y
>>
>> Not sure how to express the above.
>
> This should be expressed with this Kconfig:
>
> config BRCMFMAC_USB
> bool "USB bus interface support for FullMAC driver"
> depends on (USB = y || USB = BRCMFMAC)
> depends on BRCMFMAC
>
> config BRCMFMAC_SDIO
> bool "SDIO bus interface support for FullMAC driver"
> depends on (MMC = y || MMC = BRCMFMAC)
> depends on BRCMFMAC
> select FW_LOADER
>
> I haven't tested it, but we had a similar problem in b43 and fixed it
> like this.
Thanks, Hauke
I will create a patch fixing this.
Regards,
Arend
prev parent reply other threads:[~2013-09-01 12:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 10:00 linux-next: Tree for Aug 29 Stephen Rothwell
2013-08-29 10:00 ` Stephen Rothwell
2013-08-29 15:25 ` linux-next: Tree for Aug 29 (xen) Randy Dunlap
2013-08-30 14:24 ` Konrad Rzeszutek Wilk
2013-08-30 14:24 ` Konrad Rzeszutek Wilk
2013-08-29 15:25 ` Randy Dunlap
2013-08-30 19:59 ` linux-next: Tree for Aug 30 (nouveau) Randy Dunlap
2013-09-06 17:14 ` Randy Dunlap
2013-08-30 21:12 ` linux-next: Tree for Aug 30 (brcmfmac) Randy Dunlap
2013-08-31 17:37 ` Geert Uytterhoeven
2013-08-31 18:21 ` Arend van Spriel
2013-08-31 18:40 ` Hauke Mehrtens
2013-09-01 12:31 ` Arend van Spriel [this message]
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=522333AD.9080004@broadcom.com \
--to=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=geert@linux-m68k.org \
--cc=hauke@hauke-m.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.