From: Ben Dooks <ben-linux@fluff.org>
To: Ben Dooks <ben-linux@fluff.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kconfig question - multiple entries touching one integer
Date: Fri, 4 Jul 2008 11:54:07 +0100 [thread overview]
Message-ID: <20080704105407.GD24620@fluff.org.uk> (raw)
In-Reply-To: <20080704100829.GC24620@fluff.org.uk>
On Fri, Jul 04, 2008 at 11:08:29AM +0100, Ben Dooks wrote:
> I'm trying to produce a Kconfig to deal with allocating
> extra resources depending on what is selected. I'd like
> to have an integer which specifies the
>
> ie:
>
> config ARCH_EXTRA_RESOURCES
> int
> default 0
> help
> Extra resources depending on the board selected
>
> ...
>
> config BOARD_A
> set ARCH_EXTRA_RESOURCES 32
>
> config BOARD_B
> set ARCH_EXTRA_RESOURCES 64
>
> in this example, if board A is selected, then ARCH_EXTRA_RESOURCES
> would be 32, if BOARD_B is selected then it would be 64.
>
> doing
>
> config ARCH_EXTRA_RESOURCES
> int
> default 0
> default 32 if BOARD_A
> default 64 if BOARD_B
>
> doesn't work, and involves changing this part of the Kconfig
> every time a new board is added.
>
> Is there any current way of doing this, would there be any
> objections to having some form of 'set' clause in a config
> statememt?
Currently, the rather crufty approach is to do:
config ARCH_EXTRA_RESOURCES_32
bool
config ARCH_EXTRA_RESOURCES_64
bool
config BOARD_A
select ARCH_EXTRA_RESOURCES_32
config BOARD_B
select ARCH_EXTRA_RESOURCES_64
and have the following in the header file:
#ifdef ARCH_EXTRA_RESOURCES_64
#define ARCH_EXTRA_RESOURCES 64
#elif defined(ARCH_EXTRA_RESOURCES_32)
#define ARCH_EXTRA_RESOURCES 32
#else
#define ARCH_EXTRA_RESOURCES 0
#endif
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
next prev parent reply other threads:[~2008-07-04 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 10:08 Kconfig question - multiple entries touching one integer Ben Dooks
2008-07-04 10:54 ` Ben Dooks [this message]
2008-07-05 13:15 ` Jan Engelhardt
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=20080704105407.GD24620@fluff.org.uk \
--to=ben-linux@fluff.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox