From: viresh.kumar@st.com (Viresh KUMAR)
To: linux-arm-kernel@lists.infradead.org
Subject: QUERY: How to handle SOC Configuration (Peripheral Multiplexing) in linux
Date: Mon, 15 Mar 2010 12:36:09 +0530 [thread overview]
Message-ID: <4B9DDC61.3090609@st.com> (raw)
In-Reply-To: <20100315062041.GD31126@trinity.fluff.org>
Ben,
On 3/15/2010 11:50 AM, Ben Dooks wrote:
>> > I have provided this selection from "make menuconfig", based on selection I
>> > configure hardware at initialization time. Basically these selections will
>> > decide which device is present in the system when it boots.
> This is really bad idea, what happens if you have a selection of
> boards with mutually-exclusive peripheral sets?
In this case, we can have different defconfig files for different boards.
> Making these sorts of
> decisions at compile time is always a bad idea, it leaves people making
> distributitions a lot of extra work.
>
I agree with this point but what is the other way for this.
Doing this at runtime will have following issue:
User have inserted a module and by mistake or lack of knowledge,
he disabled already working IP(due to multiplexing). Now with Kconfig concept
this is taken care of at the beginning only. User can't select peripherals which
can't be enabled simultaneously.
regards,
viresh kumar.
next prev parent reply other threads:[~2010-03-15 7:06 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 4:31 QUERY: How to handle SOC Configuration (Peripheral Multiplexing) in linux Viresh KUMAR
2010-03-15 4:47 ` jassi brar
2010-03-15 5:14 ` Shiraz HASHIM
2010-03-15 5:41 ` jassi brar
2010-03-15 6:32 ` Viresh KUMAR
2010-03-15 6:46 ` jassi brar
2010-03-15 12:55 ` Bill Gatliff
2010-03-15 13:15 ` Russell King - ARM Linux
2010-03-15 13:22 ` Bill Gatliff
2010-03-16 2:01 ` jassi brar
2010-03-15 12:52 ` Bill Gatliff
2010-03-15 16:02 ` Armando VISCONTI
2010-03-15 16:53 ` Nicolas Pitre
2010-03-15 16:53 ` Bill Gatliff
2010-03-15 17:09 ` Mark Brown
2010-03-15 18:57 ` Tony Lindgren
2010-03-15 18:58 ` Bill Gatliff
2010-03-15 16:58 ` Russell King - ARM Linux
2010-03-15 4:57 ` Shilimkar, Santosh
2010-03-15 5:15 ` Shiraz HASHIM
2010-03-15 5:28 ` Shilimkar, Santosh
2010-03-15 6:34 ` Viresh KUMAR
2010-03-15 6:20 ` Ben Dooks
2010-03-15 6:28 ` Viresh KUMAR
2010-03-15 8:42 ` Armando VISCONTI
2010-03-15 9:09 ` Shiraz HASHIM
2010-03-15 9:37 ` jassi brar
2010-03-15 10:22 ` Shiraz HASHIM
2010-03-15 10:34 ` jassi brar
2010-03-15 10:55 ` Russell King - ARM Linux
2010-03-15 10:37 ` Russell King - ARM Linux
2010-03-15 10:10 ` Armando VISCONTI
2010-03-15 10:27 ` Shiraz HASHIM
2010-03-15 7:06 ` Viresh KUMAR [this message]
2010-03-17 16:30 ` Ben Dooks
2010-03-19 4:45 ` Viresh KUMAR
2010-03-15 17:55 ` Linus Walleij
2010-03-16 13:39 ` Shiraz HASHIM
2010-03-16 21:55 ` Linus Walleij
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=4B9DDC61.3090609@st.com \
--to=viresh.kumar@st.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).