From: "Arend van Spriel" <arend@broadcom.com>
To: "Arend van Spriel" <arend@broadcom.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"Linux Wireless List" <linux-wireless@vger.kernel.org>,
"Larry Finger" <Larry.Finger@lwfinger.net>
Subject: Re: [PATCH] bcma: add support for on-chip OTP memory used for SPROM storage
Date: Tue, 6 Mar 2012 15:44:03 +0100 [thread overview]
Message-ID: <4F5622B3.8000702@broadcom.com> (raw)
In-Reply-To: <1331040873-10290-1-git-send-email-arend@broadcom.com>
On 03/06/2012 02:34 PM, Arend van Spriel wrote:
> Wireless Broadcom chips can have either their SPROM data stored
> on either external SPROM or on-chip OTP memory. Both are accessed
> through the same register space. This patch adds support for the
> on-chip OTP memory.
John,
Please drop this patch. Better to split down this patch as it addresses
two issues (although related).
> diff --git a/drivers/bcma/sprom.c b/drivers/bcma/sprom.c
> index 916ae25..cdcf75c 100644
> --- a/drivers/bcma/sprom.c
> +++ b/drivers/bcma/sprom.c
> @@ -49,10 +49,23 @@ int bcma_arch_register_fallback_sprom(int (*sprom_callback)(struct bcma_bus *bus
> static int bcma_fill_sprom_with_fallback(struct bcma_bus *bus,
> struct ssb_sprom *out)
> {
> - if (!get_fallback_sprom)
> - return -ENOENT;
> + int err;
>
> - return get_fallback_sprom(bus, out);
> + if (!get_fallback_sprom) {
> + err = -ENOENT;
> + goto fail;
> + }
> +
> + err = get_fallback_sprom(bus, out);
> + if (err)
> + goto fail;
> +
> + pr_debug("Using SPROM revision %d provided by"
> + " platform.\n", bus->sprom.revision);
> + return 0;
> +fail:
> + pr_warn("Using fallback SPROM failed (err %d)\n", err);
> + return err;
> }
Commit message does not cover the above change.
Gr. AvS
prev parent reply other threads:[~2012-03-06 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 13:34 [PATCH] bcma: add support for on-chip OTP memory used for SPROM storage Arend van Spriel
2012-03-06 14:44 ` Arend van Spriel [this message]
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=4F5622B3.8000702@broadcom.com \
--to=arend@broadcom.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).