From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Alexander Clouter <alex@digriz.org.uk>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] ar7: register watchdog driver only if enabled in hardware configuration
Date: Wed, 05 Aug 2009 12:19:07 +0400 [thread overview]
Message-ID: <4A79407B.7070604@ru.mvista.com> (raw)
In-Reply-To: <62qmk6-g11.ln1@chipmunk.wormnet.eu>
Hello.
Alexander Clouter wrote:
>> This patch checks if the watchdog enable bit is set in the DCL
>> register meaning that the hardware watchdog actually works and
>> if so, register the ar7_wdt platform_device.
>>
>> Signed-off-by: Florian Fainelli <florian@openwrt.org>
>> ---
>> diff --git a/arch/mips/ar7/platform.c b/arch/mips/ar7/platform.c
>> index e2278c0..835f3f0 100644
>> --- a/arch/mips/ar7/platform.c
>> +++ b/arch/mips/ar7/platform.c
>> @@ -503,6 +503,7 @@ static int __init ar7_register_devices(void)
>> {
>> u16 chip_id;
>> int res;
>> + u32 *bootcr, val;
>> #ifdef CONFIG_SERIAL_8250
>> static struct uart_port uart_port[2];
>>
>> @@ -595,7 +596,13 @@ static int __init ar7_register_devices(void)
>>
>> ar7_wdt_res.end = ar7_wdt_res.start + 0x20;
>>
>> - res = platform_device_register(&ar7_wdt);
>> + bootcr = (u32 *)ioremap_nocache(AR7_REGS_DCL, 4);
>> + val = *bootcr;
>> + iounmap(bootcr);
>> +
>> + /* Register watchdog only if enabled in hardware */
>> + if (val & AR7_WDT_HW_ENA)
>> + res = platform_device_register(&ar7_wdt);
>>
>>
> I think the 'correct' way to do this is:
> ---
> void __iomem *bootcr;
> u32 val;
>
> ...
>
> bootcr = ioremap_nocache(AR7_REGS_DCL, 4);
> val = *bootcr;
>
Wait, you can't dereference a pointer to void...
WBR, Sergei
next prev parent reply other threads:[~2009-08-05 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 21:09 [PATCH] ar7: register watchdog driver only if enabled in hardware configuration Florian Fainelli
2009-08-04 22:41 ` Alexander Clouter
2009-08-05 8:19 ` Sergei Shtylyov [this message]
2009-08-05 8:34 ` Alexander Clouter
2009-08-05 8:00 ` Alexander Clouter
2009-08-07 17:27 ` Florian Fainelli
2009-10-05 9:40 ` 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=4A79407B.7070604@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=alex@digriz.org.uk \
--cc=linux-mips@linux-mips.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).