From: "Madhusudhan Chikkature" <madhu.cr@ti.com>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: tony@atomide.com, linux-omap@vger.kernel.org
Subject: Re: [PATCH]OMAP HDQ driver ioremap changes
Date: Mon, 22 Sep 2008 18:43:10 +0530 [thread overview]
Message-ID: <018001c91cb4$f8088a10$LocalHost@wipultra1303> (raw)
In-Reply-To: 20080922130621.GC30680@2ka.mipt.ru
Hi Evgeniy Polyakov,
Thanks for the comments. I will incorporate them and send the patch again. My comments inlined.
Regards,
Madhu
----- Original Message -----
From: "Evgeniy Polyakov" <johnpol@2ka.mipt.ru>
To: "Madhusudhan Chikkature" <madhu.cr@ti.com>
Cc: <tony@atomide.com>; <linux-omap@vger.kernel.org>
Sent: Monday, September 22, 2008 6:36 PM
Subject: Re: [PATCH]OMAP HDQ driver ioremap changes
> Hi.
>
> On Mon, Sep 22, 2008 at 03:45:57PM +0530, Madhusudhan Chikkature (madhu.cr@ti.com) wrote:
>> This patch provides the HDQ driver modifications to use ioremap for the base
>> address.
>
> Looks good.
> Couple of small comments inline.
>
>> --- linux-omap-2.6.orig/drivers/w1/masters/omap_hdq.c 2008-08-18
>> 14:48:26.000000000 +0530
>> +++ linux-omap-2.6/drivers/w1/masters/omap_hdq.c 2008-09-22 14:56:28.000000000
>> +0530
>> @@ -53,7 +53,7 @@ DECLARE_WAIT_QUEUE_HEAD(hdq_wait_queue);
>> int W1_ID;
>>
>> struct hdq_data {
>> - resource_size_t hdq_base;
>> + void __iomem *hdq_base;
>> struct semaphore hdq_semlock;
>
> Shouldn't it use mutex or it does counting?
Yes. RMK had given the same comment. I am working on it now. I will submit that as a second patch to use mutex
instead of semaphores.
>
>> @@ -577,7 +577,7 @@ static int __init omap_hdq_probe(struct
>> return -ENXIO;
>> }
>>
>> - hdq_data->hdq_base = res->start;
>> + hdq_data->hdq_base = ioremap(res->start, SZ_4K);
>
> Suppose it does not fail on this arch?
I will add a check for that.
>
>> /* get interface & functional clock objects */
>> hdq_data->hdq_ick = clk_get(&pdev->dev, "hdq_ick");
>> @@ -588,12 +588,14 @@ static int __init omap_hdq_probe(struct
>> if (IS_ERR(hdq_data->hdq_ick)) {
>> ret = PTR_ERR(hdq_data->hdq_ick);
>> platform_set_drvdata(pdev, NULL);
>> + iounmap(hdq_data->hdq_base);
>> kfree(hdq_data);
>> return ret;
>> }
>> if (IS_ERR(hdq_data->hdq_fck)) {
>> ret = PTR_ERR(hdq_data->hdq_fck);
>> platform_set_drvdata(pdev, NULL);
>> + iounmap(hdq_data->hdq_base);
>> kfree(hdq_data);
>> return ret;
>> }
>
> Don't you want to use goto and single exit path here and in other places?
Yes. I will make those changes as well.
>
> --
> Evgeniy Polyakov
>
>
next prev parent reply other threads:[~2008-09-22 13:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 10:15 [PATCH]OMAP HDQ driver ioremap changes Madhusudhan Chikkature
2008-09-22 13:06 ` Evgeniy Polyakov
2008-09-22 13:13 ` Madhusudhan Chikkature [this message]
2008-09-22 13:27 ` Felipe Balbi
2008-09-22 13:31 ` Madhusudhan Chikkature
2008-09-22 13:38 ` Felipe Balbi
2008-09-22 14:37 ` Felipe Balbi
2008-09-22 20:14 ` Evgeniy Polyakov
2008-09-23 2:24 ` Felipe Balbi
2008-09-23 4:52 ` Madhusudhan Chikkature
2008-09-23 6:52 ` Evgeniy Polyakov
2008-09-23 4:37 ` Madhusudhan Chikkature
2008-09-23 10:57 ` Felipe Balbi
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='018001c91cb4$f8088a10$LocalHost@wipultra1303' \
--to=madhu.cr@ti.com \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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