Re: [PATCH 13/15] chipidea: Allow user to select PCI/IMX options

From: Jiri Slaby
Date: Wed May 15 2013 - 11:58:43 EST


On 05/08/2013 11:07 AM, Alexander Shishkin wrote:
> Jiri Slaby <jslaby@xxxxxxx> writes:
>
>> From: Jeff Mahoney <jeffm@xxxxxxxx>
>>
>> The chipidea driver currently has needless ifneq rules in the makefile
>> for things that should be config options.
>
> Please elaborate on the "should be" part.
>
>> This can be problematic,
>> especially in the IMX case, since the OF_DEVICE dependency will be met
>> on powerpc systems - which don't actually support the hardware via that
>> method.
>
> That's all right, but these things should still compile on powerpc and
> get more compilation testing like that. On the other hand, if the
> compilation does break, we're probably looking at a bug in ci13xxx_imx,
> which needs fixing.
>
>> This patch adds _PCI and _IMX config options to allow the user to
>> select whether to build the modules.
>
> I would really like to avoid unnecessary config options in the chipidea
> driver, so my question is: is there a real bug or compilation breakage
> that is triggered in the current state of things?
>
>> +config USB_CHIPIDEA_PCI
>> + bool "ChipIdea PCI support"
>> + depends on PCI
>> + help
>> + This option enables ChipIdea support on PCI.
>
> I totally don't understand this: we have CONFIG_USB_CHIPIDEA and
> CONFIG_PCI, which already enable chipidea support on PCI. This helps in
> the case when you have both options enabled, but still don't want the
> ci13xxx_pci module to be built, but it doesn't justify an extra option.

Hi, the whole point of the patch is that there is no reason in building
the imx part of the driver on powerpc, because ppc will never provide
that of_device. So we are adding that option and disable that in suse
completely by this patch plus a config option.

The PCI case is not necessarily needed, but follows the IMX case.

thanks,
--
js
suse labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/