All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: 'Russell King - ARM Linux' <linux@arm.linux.org.uk>,
	linux-arm-kernel@lists.infradead.org, arm@kernel.org,
	'Linus Walleij' <linus.walleij@linaro.org>,
	linux-samsung-soc@vger.kernel.org
Subject: Re: Build failure: OMAP4430 failed due to exynos4 pinctrl
Date: Mon, 12 Nov 2012 14:40:13 +0000	[thread overview]
Message-ID: <201211121440.13980.arnd@arndb.de> (raw)
In-Reply-To: <007b01cdc0bf$50c9ee70$f25dcb50$%kim@samsung.com>

On Monday 12 November 2012, Kukjin Kim wrote:
> Russell King - ARM Linux wrote:
> > 
> > Last night's randconfig for OMAP4430 failed with:
> > 
> > drivers/built-in.o:(.rodata+0x1a60): undefined reference to
> > `exynos4210_pin_ctrl'
> > 
> > Config and log:
> > http://www.arm.linux.org.uk/developer/build/file.php?type=config&idx=2693
> > http://www.arm.linux.org.uk/developer/build/result.php?type=build&idx=2693
> 
> Oops, yeah right.

Hmm, I found the same thing earlier and it got lost in my backlog of unsubmitted
patches.

> diff --git a/drivers/pinctrl/Kconfig b/drivers/pinctrl/Kconfig
> index 7bf914d..18b473b 100644
> --- a/drivers/pinctrl/Kconfig
> +++ b/drivers/pinctrl/Kconfig
> @@ -179,11 +179,13 @@ config PINCTRL_COH901
>  
>  config PINCTRL_SAMSUNG
>  	bool "Samsung pinctrl driver"
> +	depends on PLAT_SAMSUNG
>  	select PINMUX
>  	select PINCONF
>  
>  config PINCTRL_EXYNOS4
>  	bool "Pinctrl driver data for Exynos4 SoC"
> +	depends on PINCTRL_SAMSUNG && ARCH_EXYNOS4
>  	select PINCTRL_SAMSUNG

This won't work. A driver can't "select" and "depend on"
another symbol at the same time.

This is what I came up with earlier.

	Arnd
8<----------------
>From a15cc6277a3a43c8b5c1dd90ca71732b2ffe2b18 Mon Sep 17 00:00:00 2001
From: Arnd Bergmann <arnd@arndb.de>
Date: Wed, 10 Oct 2012 13:31:45 +0000
Subject: [PATCH] pinctrl: samsung: don't allow enabling pinctrl-samsung
 standalone

The main samsung pinctrl module references the specific exynos4210
pinctrl driver, which selects the main driver in Kconfig.

Making the main driver a silent "bool" option avoid this potential
build error if CONFIG_PINCTRL_SAMSUNG=y && CONFIG_PINCTRL_EXYNOS4=n:

drivers/built-in.o:(.rodata+0x4e4): undefined reference to `exynos4210_pin_ctrl'

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Cc: Tomasz Figa <t.figa@samsung.com>
Cc: Kyungmin Park <kyungmin.park@samsung.com>
Cc: Linus Walleij <linus.walleij@linaro.org>
Cc: Kukjin Kim <kgene.kim@samsung.com>

diff --git a/drivers/pinctrl/Kconfig b/drivers/pinctrl/Kconfig
index 7bf914d..9f54bd4 100644
--- a/drivers/pinctrl/Kconfig
+++ b/drivers/pinctrl/Kconfig
@@ -178,7 +178,7 @@ config PINCTRL_COH901
 	  ports of 8 GPIO pins each.
 
 config PINCTRL_SAMSUNG
-	bool "Samsung pinctrl driver"
+	bool
 	select PINMUX
 	select PINCONF
 

WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Build failure: OMAP4430 failed due to exynos4 pinctrl
Date: Mon, 12 Nov 2012 14:40:13 +0000	[thread overview]
Message-ID: <201211121440.13980.arnd@arndb.de> (raw)
In-Reply-To: <007b01cdc0bf$50c9ee70$f25dcb50$%kim@samsung.com>

On Monday 12 November 2012, Kukjin Kim wrote:
> Russell King - ARM Linux wrote:
> > 
> > Last night's randconfig for OMAP4430 failed with:
> > 
> > drivers/built-in.o:(.rodata+0x1a60): undefined reference to
> > `exynos4210_pin_ctrl'
> > 
> > Config and log:
> > http://www.arm.linux.org.uk/developer/build/file.php?type=config&idx=2693
> > http://www.arm.linux.org.uk/developer/build/result.php?type=build&idx=2693
> 
> Oops, yeah right.

Hmm, I found the same thing earlier and it got lost in my backlog of unsubmitted
patches.

> diff --git a/drivers/pinctrl/Kconfig b/drivers/pinctrl/Kconfig
> index 7bf914d..18b473b 100644
> --- a/drivers/pinctrl/Kconfig
> +++ b/drivers/pinctrl/Kconfig
> @@ -179,11 +179,13 @@ config PINCTRL_COH901
>  
>  config PINCTRL_SAMSUNG
>  	bool "Samsung pinctrl driver"
> +	depends on PLAT_SAMSUNG
>  	select PINMUX
>  	select PINCONF
>  
>  config PINCTRL_EXYNOS4
>  	bool "Pinctrl driver data for Exynos4 SoC"
> +	depends on PINCTRL_SAMSUNG && ARCH_EXYNOS4
>  	select PINCTRL_SAMSUNG

This won't work. A driver can't "select" and "depend on"
another symbol at the same time.

This is what I came up with earlier.

	Arnd
8<----------------
>From a15cc6277a3a43c8b5c1dd90ca71732b2ffe2b18 Mon Sep 17 00:00:00 2001
From: Arnd Bergmann <arnd@arndb.de>
Date: Wed, 10 Oct 2012 13:31:45 +0000
Subject: [PATCH] pinctrl: samsung: don't allow enabling pinctrl-samsung
 standalone

The main samsung pinctrl module references the specific exynos4210
pinctrl driver, which selects the main driver in Kconfig.

Making the main driver a silent "bool" option avoid this potential
build error if CONFIG_PINCTRL_SAMSUNG=y && CONFIG_PINCTRL_EXYNOS4=n:

drivers/built-in.o:(.rodata+0x4e4): undefined reference to `exynos4210_pin_ctrl'

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Cc: Tomasz Figa <t.figa@samsung.com>
Cc: Kyungmin Park <kyungmin.park@samsung.com>
Cc: Linus Walleij <linus.walleij@linaro.org>
Cc: Kukjin Kim <kgene.kim@samsung.com>

diff --git a/drivers/pinctrl/Kconfig b/drivers/pinctrl/Kconfig
index 7bf914d..9f54bd4 100644
--- a/drivers/pinctrl/Kconfig
+++ b/drivers/pinctrl/Kconfig
@@ -178,7 +178,7 @@ config PINCTRL_COH901
 	  ports of 8 GPIO pins each.
 
 config PINCTRL_SAMSUNG
-	bool "Samsung pinctrl driver"
+	bool
 	select PINMUX
 	select PINCONF
 

  reply	other threads:[~2012-11-12 14:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 10:20 Build failure: OMAP4430 failed due to exynos4 pinctrl Kukjin Kim
2012-11-12 14:40 ` Arnd Bergmann [this message]
2012-11-12 14:40   ` Arnd Bergmann
2012-11-13  5:11   ` Kukjin Kim
2012-11-13  5:11     ` Kukjin Kim
2012-11-15 10:59     ` Linus Walleij
2012-11-15 10:59       ` Linus Walleij
  -- strict thread matches above, loose matches on Subject: below --
2012-11-12  9:33 Russell King - ARM Linux
2012-11-12 10:02 ` Kukjin Kim

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=201211121440.13980.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=arm@kernel.org \
    --cc=kgene.kim@samsung.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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.