linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: vitalywool@gmail.com (Vitaly Wool)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] omap3evm: Add Mistral WL12XX config support
Date: Thu, 16 Jun 2011 14:20:27 +0200	[thread overview]
Message-ID: <BANLkTi=XocYNPwuB2_-T8AHQkfEuzUnd9Q@mail.gmail.com> (raw)
In-Reply-To: <20110614135518.GH23145@atomide.com>

Hi Shahar, Tony,

On Tue, Jun 14, 2011 at 3:55 PM, Tony Lindgren <tony@atomide.com> wrote:
> * Shahar Lev <shahar@wizery.com> [110614 06:21]:
>> On Tue, Jun 14, 2011 at 3:34 PM, Tony Lindgren <tony@atomide.com> wrote:
>> >
>> > This your should try to remove as it won't work nicely for supporting
>> > various boards with the same kernel as we already do with
>> > omap2plus_defconfig.
>> >
>> > Can you somehow detect the daughter board dynamically and then
>> > set the flags?
>> >
>>
>> We thought about multi-board kernels, but unfortunately have no
>> better solution, since there is no dynamic way to probe these cards.
>> Even worse, these cards sometimes come with different clocks in them,
>> hence the 2nd OMAP3EVM_MISTRAL_WL12XX_REFCLOCK entry we had to
>> introduce...
>>
>> Maybe we should add two bootargs with which the user can override this
>> Kconfig configuration? This should allow using the same kernel binary
>> with different omap3evm boards.

You won't need Kconfig parameters then. Just have module parameters
and supply whatever default values you find reasonable.

~Vitaly

  reply	other threads:[~2011-06-16 12:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14 12:16 [PATCH] omap3evm: Add Mistral WL12XX config support Shahar Lev
2011-06-14 12:34 ` Tony Lindgren
2011-06-14 13:26   ` Shahar Lev
2011-06-14 13:55     ` Tony Lindgren
2011-06-16 12:20       ` Vitaly Wool [this message]
2011-06-16  9:53 ` Premi, Sanjeev
2011-06-16 18:37   ` Shahar Lev

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='BANLkTi=XocYNPwuB2_-T8AHQkfEuzUnd9Q@mail.gmail.com' \
    --to=vitalywool@gmail.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).