Return-path: Received: from mail-pd0-f182.google.com ([209.85.192.182]:46649 "EHLO mail-pd0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751170AbaJITZ1 (ORCPT ); Thu, 9 Oct 2014 15:25:27 -0400 Date: Thu, 9 Oct 2014 12:25:20 -0700 From: Guenter Roeck To: Hauke Mehrtens Cc: Arend van Spriel , =?utf-8?B?UmFmYcWCIE1pxYJlY2tp?= , "linux-wireless@vger.kernel.org" , Linux Kernel Mailing List , Arnd Bergmann Subject: Re: [PATCH] bcma: Add dependency on OF_ADDRESS Message-ID: <20141009192520.GA6552@roeck-us.net> (sfid-20141009_212549_647729_25BDD8EE) References: <1412872877-1771-1-git-send-email-linux@roeck-us.net> <5436C2B4.6030801@broadcom.com> <5436C367.5080908@broadcom.com> <20141009172924.GD2410@roeck-us.net> <5436D3CF.2030506@hauke-m.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 In-Reply-To: <5436D3CF.2030506@hauke-m.de> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, Oct 09, 2014 at 08:28:31PM +0200, Hauke Mehrtens wrote: > On 10/09/2014 07:29 PM, Guenter Roeck wrote: > > On Thu, Oct 09, 2014 at 07:18:31PM +0200, Arend van Spriel wrote: > >> On 10/09/14 19:15, Arend van Spriel wrote: > >>> On 10/09/14 18:54, Rafał Miłecki wrote: > >>>> On 9 October 2014 18:41, Guenter Roeck wrote: > >>>>> Commit 2101e533f41a ("bcma: register bcma as device tree driver") > >>>>> introduces a hard dependency on OF_ADDRESS into the bcma driver. > >>>>> OF_ADDRESS is specifically disabled for the sparc architecture. > >>>>> This results in the following error when building sparc64:allmodconfig. > >>> > >>> Does this mean on sparc (using allmodconfig) you will get CONFIG_OF and > >>> !CONFIG_OF_ADDRESS? Does that makes sense? > >> > >> Is CONFIG_OF is used on sparc to access OpenBoot information? > >> > > I have no idea. All I know is that the driver doesn't build anymore with OF > > enabled and OF_ADDRESS disabled. > > Device tree support in bcma is only needed on some SoC, when this is > used on a PCIe card it is not needed. > > I would just deactivate the parts that are using device tree in bcma > when it is not available. I will send a patch after having something to eat. > Devicetree dependency is already covered with #ifdef CONFIG_OF. Problem is that it really needs #ifdef CONFIG_OF_ADDRESS. Though even that might be better than my patch, since it would at least build the driver on sparc as it used to do. > Is there a better method which is compatible with SPARC than using > of_translate_address() to get the reg address and also take the ranges > attribute of the bus into account? > No idea, sorry. Can you by any chance use pcie device information instead of depending on devicetree data ? Guenter