From: luciano.coelho@nokia.com (Luciano Coelho)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 2/7] wl1271: propagate set_power's return value
Date: Thu, 16 Sep 2010 22:40:18 +0300 [thread overview]
Message-ID: <1284666018.8951.66.camel@powerslave> (raw)
In-Reply-To: <1284592929-29616-3-git-send-email-ohad@wizery.com>
On Thu, 2010-09-16 at 01:22 +0200, ext Ohad Ben-Cohen wrote:
> Make it possible for the set power method to indicate a
> success/failure return value. This is needed to support
> more complex power on/off operations such as SDIO
> power manipulations.
>
> Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
> ---
Some comments below.
> diff --git a/drivers/net/wireless/wl12xx/wl1271_io.h b/drivers/net/wireless/wl12xx/wl1271_io.h
> index bc806c7..c1f92e6 100644
> --- a/drivers/net/wireless/wl12xx/wl1271_io.h
> +++ b/drivers/net/wireless/wl12xx/wl1271_io.h
> @@ -144,10 +144,13 @@ static inline void wl1271_power_off(struct wl1271 *wl)
> clear_bit(WL1271_FLAG_GPIO_POWER, &wl->flags);
> }
>
> -static inline void wl1271_power_on(struct wl1271 *wl)
> +static inline int wl1271_power_on(struct wl1271 *wl)
> {
> - wl->if_ops->power(wl, true);
> - set_bit(WL1271_FLAG_GPIO_POWER, &wl->flags);
> + int ret = wl->if_ops->power(wl, true);
I think it look nicer if you keep the "int ret" in one line by itself
and then do a ret = wl->if_ops... on another one.
> + if (ret == 0)
> + set_bit(WL1271_FLAG_GPIO_POWER, &wl->flags);
> +
> + return ret;
> }
> diff --git a/drivers/net/wireless/wl12xx/wl1271_sdio.c b/drivers/net/wireless/wl12xx/wl1271_sdio.c
> index b5d9565..1d5dc72 100644
> --- a/drivers/net/wireless/wl12xx/wl1271_sdio.c
> +++ b/drivers/net/wireless/wl12xx/wl1271_sdio.c
> @@ -159,35 +159,38 @@ static void wl1271_sdio_raw_write(struct wl1271 *wl, int addr, void *buf,
> wl1271_error("sdio write failed (%d)", ret);
> }
>
> -static void wl1271_sdio_power_on(struct wl1271 *wl)
> +static int wl1271_sdio_power_on(struct wl1271 *wl)
> {
> struct sdio_func *func = wl_to_func(wl);
>
> sdio_claim_host(func);
> sdio_enable_func(func);
> sdio_release_host(func);
> +
> + return 0;
> }
You seem to always return 0, so the whole chain to pass the value up
seems unnecessary. Is this just a preparation for a future patch?
--
Cheers,
Luca.
next prev parent reply other threads:[~2010-09-16 19:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 23:22 [PATCH v6 0/7] native wl1271 support on ZOOM Ohad Ben-Cohen
2010-09-15 23:22 ` [PATCH v6 1/7] wl12xx: make wl12xx.h common to both spi and sdio Ohad Ben-Cohen
2010-09-16 10:17 ` Teemu Paasikivi
2010-09-16 10:45 ` Ohad Ben-Cohen
2010-09-16 11:16 ` [PATCH v6 01/17] " Ohad Ben-Cohen
2010-09-16 11:50 ` [PATCH v6 1/7] " Ohad Ben-Cohen
2010-09-16 18:35 ` [PATCH v6 01/17] " Luciano Coelho
2010-09-16 19:56 ` Ohad Ben-Cohen
2010-09-16 20:00 ` Luciano Coelho
2010-09-16 20:46 ` Tony Lindgren
2010-09-15 23:22 ` [PATCH v6 2/7] wl1271: propagate set_power's return value Ohad Ben-Cohen
2010-09-16 19:40 ` Luciano Coelho [this message]
2010-09-16 19:53 ` Ohad Ben-Cohen
2010-09-16 19:56 ` Luciano Coelho
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=1284666018.8951.66.camel@powerslave \
--to=luciano.coelho@nokia.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).