From: ido@wizery.com (Ido Yariv)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 6/6] arm: davinci: DA850: Add wl1271/wlan support
Date: Thu, 28 Jul 2011 21:34:54 +0300 [thread overview]
Message-ID: <20110728183454.GE1985@WorkStation> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB593024DD2CEC2@dbde02.ent.ti.com>
Hi Sekhar,
On Mon, Jul 25, 2011 at 11:10:55PM +0530, Nori, Sekhar wrote:
> Adding a new kernel parameter requires update to
> Documentation/kernel-parameters.txt as well.
>
> I am Ccing a couple of folks in case they have ideas on
> whether there is a better way to pass this information
> to the kernel. I assume there is no way to detect
> this from hardware.
Unfortunately, auto-detection of the reference clock is not currently
possible. However, it might be a better idea to have the ability to
override this value with a wl12xx module parameter instead of a kernel
parameter. I'll drop this kernel parameter.
> > +static struct davinci_mmc_config da850_mmc_wl12xx_config = {
> > + .get_ro = NULL,
> > + .get_cd = NULL,
>
> You can get rid of these NULL initializers.
Sure.
> > + .set_power = wl12xx_set_power,
> > + .wires = 4,
> > + .max_freq = 25000000,
> > + .caps = MMC_CAP_4_BIT_DATA | MMC_CAP_NONREMOVABLE |
> > + MMC_CAP_POWER_OFF_CARD,
> > + .version = MMC_CTLR_VERSION_2,
> > +};
[...]
> > + ret = gpio_request_one(DA850_WLAN_EN, GPIOF_OUT_INIT_LOW, "wl12xx_en");
> > + if (ret) {
> > + pr_err("Error initializing the wl12xx enable gpio: %d\n", ret);
> > + return;
> > + }
> > +
> > + ret = gpio_request_one(DA850_WLAN_IRQ, GPIOF_IN, "wl12xx_irq");
> > + if (ret) {
> > + pr_err("Error initializing the wl12xx irq gpio: %d\n", ret);
> > + gpio_free(DA850_WLAN_EN);
> > + return;
> > + }
> > +
> > + da850_wl12xx_wlan_data.irq = gpio_to_irq(DA850_WLAN_IRQ);
> > + da850_wl12xx_wlan_data.board_ref_clock = da850_wl12xx_fref;
> > +
> > + ret = wl12xx_set_platform_data(&da850_wl12xx_wlan_data);
> > + if (ret) {
> > + pr_err("Error setting wl12xx data: %d\n", ret);
> > + gpio_free(DA850_WLAN_IRQ);
> > + gpio_free(DA850_WLAN_EN);
>
> Why not just use the traditional goto based bail out
> mechanism? You will avoid the multiple gpio_free() calls.
Sure.
Thanks for your review,
Ido.
next prev parent reply other threads:[~2011-07-28 18:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 13:14 [PATCH v2 0/6] arm: davinci: DA850: wl12xx expansion card Ido Yariv
2011-07-10 13:14 ` [PATCH v2 1/6] arm: davinci: Fix low level gpio irq handlers' argument Ido Yariv
2011-07-11 11:58 ` Nori, Sekhar
2011-07-11 20:33 ` Ido Yariv
2011-07-11 21:03 ` [PATCH v3 " Ido Yariv
2011-07-12 9:22 ` Nori, Sekhar
2011-07-12 22:19 ` Ido Yariv
2011-07-10 13:14 ` [PATCH v2 2/6] arm: davinci: Explicitly set channel controllers' default queues Ido Yariv
2011-07-25 13:15 ` Nori, Sekhar
2011-07-25 13:33 ` Sergei Shtylyov
2011-07-25 16:31 ` Nori, Sekhar
2011-07-29 14:42 ` Ben Gardiner
2011-07-10 13:14 ` [PATCH v2 3/6] arm: davinci: mmc: Add support for set_power callback Ido Yariv
2011-07-25 13:19 ` Nori, Sekhar
2011-07-28 20:49 ` [PATCH REPOST v2] mmc: davinci: " Ido Yariv
2011-07-28 22:02 ` Chris Ball
2011-07-10 13:14 ` [PATCH v2 4/6] arm: davinci: DA850: Add MMC/SD1 pinmux configuration Ido Yariv
2011-07-10 13:14 ` [PATCH v2 5/6] arm: davinci: DA850: Add GPIO pinmux configuration for wl1271 Ido Yariv
2011-07-25 13:23 ` Nori, Sekhar
2011-07-10 13:14 ` [PATCH v2 6/6] arm: davinci: DA850: Add wl1271/wlan support Ido Yariv
2011-07-25 17:40 ` Nori, Sekhar
2011-07-28 18:34 ` Ido Yariv [this message]
2011-07-28 20:52 ` [PATCH v3] davinci: Add wl1271/wlan support for AM18x Ido Yariv
2011-07-28 21:15 ` Troy Kisky
2011-07-28 22:06 ` Ido Yariv
2011-07-29 18:51 ` Troy Kisky
2011-08-03 13:27 ` Nori, Sekhar
2011-08-04 7:51 ` [PATCH v4] ARM: davinci: AM18x: Add wl1271/wlan support Ido Yariv
2011-08-04 8:40 ` Jaya Kumar
2011-08-04 9:22 ` Ido Yariv
2011-09-01 11:59 ` Nori, Sekhar
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=20110728183454.GE1985@WorkStation \
--to=ido@wizery.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).