From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/3] soc: brcmstb: Add Bus Interface Unit control setup
Date: Thu, 17 Sep 2015 10:42:18 -0700 [thread overview]
Message-ID: <55FAFB7A.4010105@gmail.com> (raw)
In-Reply-To: <CADtm3G6SkczVkFK0n=fpMCkocj_ijGWtHkfipTZZfp8deC=6zg@mail.gmail.com>
On 16/09/15 23:08, Gregory Fong wrote:
>> [...]
>> diff --git a/drivers/soc/brcmstb/biuctrl.c b/drivers/soc/brcmstb/biuctrl.c
>> new file mode 100644
>> index 000000000000..1d4deada1c4d
>> --- /dev/null
>> +++ b/drivers/soc/brcmstb/biuctrl.c
>> @@ -0,0 +1,119 @@
>> [...]
>> +int __init brcmstb_biuctrl_init(void)
>> +{
>> + int ret = 0;
>> +
>> + ret = setup_hifcpubiuctrl_regs();
>> + if (ret)
>> + return ret;
>> +
>> + ret = mcp_write_pairing_set();
>> + if (ret) {
>> + pr_err("MCP: Unable to disable write pairing!\n");
>> + return ret;
>
> The return value isn't used in patch 3. Is there a point to returning
> an error from this function in either of the above two locations,
> considering that?
>
> Looks good otherwise.
>
> Acked-by: Gregory Fong <gregory.0xf0@gmail.com>
Not really, how about this:
void __init brcmstb_biuctrl_init(void)
{
int ret;
setup_hifcpubiuctrl_regs();
ret = mcp_write_pairing_set();
if (ret) {
pr_err("MCP: Unable to disable write pairing!\n");
return;
}
#ifdef CONFIG_PM_SLEEP
register_syscore_ops(&brcmstb_cpu_credit_syscore_ops);
#endif
}
and updating the function prototype accordingly in the header file?
--
Florian
WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Gregory Fong
<gregory.0xf0-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Florian Fainelli
<f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
Brian Norris
<computersforpeace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
bcm-kernel-feedback-list
<bcm-kernel-feedback-list-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH v2 2/3] soc: brcmstb: Add Bus Interface Unit control setup
Date: Thu, 17 Sep 2015 10:42:18 -0700 [thread overview]
Message-ID: <55FAFB7A.4010105@gmail.com> (raw)
In-Reply-To: <CADtm3G6SkczVkFK0n=fpMCkocj_ijGWtHkfipTZZfp8deC=6zg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 16/09/15 23:08, Gregory Fong wrote:
>> [...]
>> diff --git a/drivers/soc/brcmstb/biuctrl.c b/drivers/soc/brcmstb/biuctrl.c
>> new file mode 100644
>> index 000000000000..1d4deada1c4d
>> --- /dev/null
>> +++ b/drivers/soc/brcmstb/biuctrl.c
>> @@ -0,0 +1,119 @@
>> [...]
>> +int __init brcmstb_biuctrl_init(void)
>> +{
>> + int ret = 0;
>> +
>> + ret = setup_hifcpubiuctrl_regs();
>> + if (ret)
>> + return ret;
>> +
>> + ret = mcp_write_pairing_set();
>> + if (ret) {
>> + pr_err("MCP: Unable to disable write pairing!\n");
>> + return ret;
>
> The return value isn't used in patch 3. Is there a point to returning
> an error from this function in either of the above two locations,
> considering that?
>
> Looks good otherwise.
>
> Acked-by: Gregory Fong <gregory.0xf0-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Not really, how about this:
void __init brcmstb_biuctrl_init(void)
{
int ret;
setup_hifcpubiuctrl_regs();
ret = mcp_write_pairing_set();
if (ret) {
pr_err("MCP: Unable to disable write pairing!\n");
return;
}
#ifdef CONFIG_PM_SLEEP
register_syscore_ops(&brcmstb_cpu_credit_syscore_ops);
#endif
}
and updating the function prototype accordingly in the header file?
--
Florian
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-09-17 17:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 18:14 [PATCH v2 0/3] ARM: brcmstb: Bus Interface Unit support Florian Fainelli
2015-09-15 18:14 ` Florian Fainelli
2015-09-15 18:14 ` [PATCH v2 1/3] Documentation: bindings: brcmstb: Document write-pairing Florian Fainelli
2015-09-15 18:14 ` Florian Fainelli
2015-09-17 6:09 ` Gregory Fong
2015-09-17 6:09 ` Gregory Fong
2015-09-17 17:28 ` Florian Fainelli
2015-09-17 17:28 ` Florian Fainelli
2015-09-15 18:14 ` [PATCH v2 2/3] soc: brcmstb: Add Bus Interface Unit control setup Florian Fainelli
2015-09-15 18:14 ` Florian Fainelli
2015-09-17 6:08 ` Gregory Fong
2015-09-17 6:08 ` Gregory Fong
2015-09-17 17:42 ` Florian Fainelli [this message]
2015-09-17 17:42 ` Florian Fainelli
2015-09-18 13:12 ` Gregory Fong
2015-09-18 13:12 ` Gregory Fong
2015-09-18 19:22 ` Florian Fainelli
2015-09-18 19:22 ` Florian Fainelli
2015-09-15 18:15 ` [PATCH v2 3/3] ARM: brcmstb: Setup BIU control registers during boot Florian Fainelli
2015-09-15 18:15 ` Florian Fainelli
2015-09-17 6:10 ` Gregory Fong
2015-09-17 6:10 ` Gregory Fong
2015-09-18 19:23 ` Florian Fainelli
2015-09-18 19:23 ` Florian Fainelli
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=55FAFB7A.4010105@gmail.com \
--to=f.fainelli@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.