From: Tony Lindgren <tony@atomide.com>
To: Shahar Lev <shahar@wizery.com>
Cc: linux-omap@vger.kernel.org,
linux-arm <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] omap3evm: Add Mistral WL12XX config support
Date: Tue, 14 Jun 2011 05:34:00 -0700 [thread overview]
Message-ID: <20110614123359.GB23145@atomide.com> (raw)
In-Reply-To: <1308053788-25937-1-git-send-email-shahar@wizery.com>
* Shahar Lev <shahar@wizery.com> [110614 05:12]:
>
> +config OMAP3EVM_MISTRAL_WL12XX
> + bool "Enable Mistral WL12XX daughter board support"
> + depends on MACH_OMAP3EVM
> + help
> + Support for the Mistral WL12XX daughter board.
> + This extension board which supports both WLAN and Bluetooth.
> + Specifically, for WL1271, more info can be found at
> + http://mistralsolutions.com/component/jumi/Download_Common_Code.html?docid=298
> +
> +config OMAP3EVM_MISTRAL_WL12XX_REFCLOCK
> + int "Ref clock value"
> + range 0 5
> + depends on OMAP3EVM_MISTRAL_WL12XX
> + default 2
> + help
> + Set ref clock value for the Mistral WL12XX daughter board.
> + Select 0 for 19.2 MHz.
> + Select 1 for 26 MHz.
> + Select 2 for 38.4 MHz.
> + Select 3 for 52 MHz.
> + Select 4 for 38.4 MHz, XTAL.
> + Select 5 for 26 MHz, XTAL.
> +
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?
Tony
next prev parent reply other threads:[~2011-06-14 12:34 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 [this message]
2011-06-14 13:26 ` Shahar Lev
2011-06-14 13:55 ` Tony Lindgren
2011-06-16 12:20 ` Vitaly Wool
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=20110614123359.GB23145@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=shahar@wizery.com \
/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