Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757311Ab0DFQ5S (ORCPT ); Tue, 6 Apr 2010 12:57:18 -0400 Received: from rcsinet12.oracle.com ([148.87.113.124]:51547 "EHLO rcsinet12.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757076Ab0DFQ5J convert rfc822-to-8bit (ORCPT ); Tue, 6 Apr 2010 12:57:09 -0400 Date: Tue, 6 Apr 2010 09:56:33 -0700 From: Randy Dunlap To: Bruno =?ISO-8859-1?Q?Pr=E9mont?= Cc: Jiri Kosina , linux-kernel@vger.kernel.org, linux-input@vger.kernel.org, Andrew Morton , rvinyard@cs.nmsu.edu Subject: Re: [PATCH mmotm] hid-picolcd: depends on LCD_CLASS_DEVICE Message-Id: <20100406095633.49ec957a.randy.dunlap@oracle.com> In-Reply-To: <20100406183535.7de3c628@neptune.home> References: <201004052336.o35NaeSE015814@imap1.linux-foundation.org> <20100405220414.9d90da83.randy.dunlap@oracle.com> <20100406105635.5384a087@pluto.restena.lu> <20100406082614.79aaf1c5.randy.dunlap@oracle.com> <20100406183535.7de3c628@neptune.home> Organization: Oracle Linux Eng. X-Mailer: Sylpheed 2.7.1 (GTK+ 2.16.6; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Source-IP: acsmt353.oracle.com [141.146.40.153] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090205.4BBB67D3.0184:SCFMA4539814,ss=1,fgs=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2898 Lines: 97 On Tue, 6 Apr 2010 18:35:35 +0200 Bruno Pr?mont wrote: > On Tue, 06 April 2010 Randy Dunlap wrote: > > On Tue, 6 Apr 2010 10:56:35 +0200 Bruno Pr?mont wrote: > > > > > On Tue, 6 Apr 2010 10:40:06 +0200 Jiri Kosina wrote: > > > > > > > > [ adding Bruno to CC ] > > > > > > > > On Mon, 5 Apr 2010, Randy Dunlap wrote: > > > > > > > > > From: Randy Dunlap > > > > > > > > > > HID_PICOLCD should depend on LCD_CLASS_DEVICE, otherwise the > > > > > build fails when HID_PICOLCD=y and LCD_CLASS_DEVICE=m: > > > > > > > > > > hid-picolcd.c:(.text+0x84523f): undefined reference to `lcd_device_unregister' > > > > > hid-picolcd.c:(.text+0x8478ab): undefined reference to `lcd_device_register' > > > > > hid-picolcd.c:(.text+0x84c15f): undefined reference to `lcd_device_unregister' > > > > > > That is weird, the > > > > > > #if defined(CONFIG_LCD_CLASS_DEVICE) || defined(CONFIG_LCD_CLASS_DEVICE_MODULE) > > > feature support code > > > #else > > > empty stubs > > > #endif > > > > > > blocks should have prevented LCD_CLASS support from being built if it > > > was not enabled in configuration. > > > > > > Do you have the .config matching your build? > > > > Yes, it's attached. > > Thanks, here is the extract (only the pertinent items): > CONFIG_BACKLIGHT_LCD_SUPPORT=y > CONFIG_LCD_CLASS_DEVICE=m > CONFIG_BACKLIGHT_CLASS_DEVICE=y > CONFIG_HID_PICOLCD=y > > It triggers the issue by having PicoLCD built-in while one of the > optional dependencies as a module. Yes, basically what the patch description said. > Any idea of how this can be solved with kbuild in order to keep the > dependencies optional? > > Something that would satisfy the following pseudocode: > if CONFIG_HID_PICOLCD == y > assert(CONFIG_LCD_CLASS_DEVICE != m) > If you don't want the kconfig machinery to do that (it appears that you don't), then I guess that you'll need to expand the source code to handle CONFIG_LCD_CLASS_DEVICE=y and CONFIG_LCD_CLASS_DEVICE=m differently. Or only handle them differently if HID_PICOLCD=y. :( > > One of my attempts did end up with a circular loop with regard to FB > (some of the FB drivers did select INPUT)? (not that I can find) CONFIG_VT does select INPUT and CONFIG_DRM_I915 does select INPUT if ACPI > I had something like: > > config HID_PICOLCD > tristate ... > > config HID_PICOLCD_FB > bool ... > depends on HID_PICOLCD > select FB > select FB_... > > ... > > Then in the code I checked for CONFIG_HID_PICOLCD_FB instead of > (CONFIG_FB or CONFIG_FB_MODULE). --- ~Randy (re)read Documentation/ManagementStyle -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/