From: Miguel Aguilar <miguel.aguilar-9uBrGCPFOa1Wk0Htik3J/w@public.gmane.org>
To: Dmitry Torokhov
<dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org,
clark.becker-9uBrGCPFOa1Wk0Htik3J/w@public.gmane.org,
linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
santiago.nunez-9uBrGCPFOa1Wk0Htik3J/w@public.gmane.org,
todd.fischer-9uBrGCPFOa1Wk0Htik3J/w@public.gmane.org
Subject: Re: [PATCH v4 1/2] Input: DaVinci Keypad Driver
Date: Tue, 13 Oct 2009 10:43:49 -0600 [thread overview]
Message-ID: <4AD4AE45.8050607@ridgerun.com> (raw)
In-Reply-To: <20091013054644.GF2887-WlK9ik9hQGAhIp7JRqBPierSzoNAToWh@public.gmane.org>
Dmitry,
Dmitry Torokhov wrote:
> Hi Miguel,
>
> On Fri, Oct 09, 2009 at 11:27:05AM -0600, miguel.aguilar-9uBrGCPFOa1Wk0Htik3J/w@public.gmane.org wrote:
>> From: Miguel Aguilar <miguel.aguilar-9uBrGCPFOa1Wk0Htik3J/w@public.gmane.org>
>>
>> Adds the driver for enabling keypad support for DaVinci platforms.
>>
>> DM365 is the only platform that uses this driver at the moment.
>>
>
> Looks pretty good, I have one question:
>
>> +static void davinci_ks_write(struct davinci_ks *davinci_ks, u32 val, u32 addr)
>> +{
>> + u32 base = (u32)davinci_ks->base;
>> +
>> + __raw_writel(val,(u32 *)(base + addr));
>> +}
>
> Do you really need these casts? I'd think that bare __raw_writel would
> work just fine.
>
>> +
>> +static u32 davinci_ks_read(struct davinci_ks *davinci_ks, u32 addr)
>> +{
>> + u32 base = (u32)davinci_ks->base;
>> +
>> + return __raw_readl((u32 *)(base + addr));
>> +}
>
> Could you also please try the patch below and let me know if it breaks
> things. Also iof you coulr run sparse over the driver that would be
> nice.
>
> Thanks!
>
Thanks for the patch, I will add it and resend the whole patch.
Just one thing failed:
+fail6:
+ free_irq(davinci_ks->irq);
this must be:
free_irq(davinci_ks->irq, davinci_ks);
next prev parent reply other threads:[~2009-10-13 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 17:27 [PATCH v4 1/2] Input: DaVinci Keypad Driver miguel.aguilar-9uBrGCPFOa1Wk0Htik3J/w
[not found] ` <1255109225-6833-1-git-send-email-miguel.aguilar-9uBrGCPFOa1Wk0Htik3J/w@public.gmane.org>
2009-10-12 18:27 ` Kevin Hilman
[not found] ` <874oq4sc1b.fsf-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2009-10-13 18:58 ` Miguel Aguilar
2009-10-13 5:46 ` Dmitry Torokhov
2009-10-13 16:21 ` H Hartley Sweeten
2009-10-13 16:55 ` Dmitry Torokhov
[not found] ` <20091013165524.GA21593-WlK9ik9hQGAhIp7JRqBPierSzoNAToWh@public.gmane.org>
2009-10-13 17:03 ` Miguel Aguilar
[not found] ` <20091013054644.GF2887-WlK9ik9hQGAhIp7JRqBPierSzoNAToWh@public.gmane.org>
2009-10-13 16:43 ` Miguel Aguilar [this message]
[not found] <1254772537-30836-1-git-send-email-miguel.aguilar@ridgerun.com>
[not found] ` <4ACF6DBA.8080307@ridgerun.com>
[not found] ` <20091009172011.GF1092@core.coreip.homeip.net>
2009-10-09 17:21 ` Dmitry Torokhov
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=4AD4AE45.8050607@ridgerun.com \
--to=miguel.aguilar-9ubrgcpfoa1wk0htik3j/w@public.gmane.org \
--cc=clark.becker-9uBrGCPFOa1Wk0Htik3J/w@public.gmane.org \
--cc=davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org \
--cc=dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=santiago.nunez-9uBrGCPFOa1Wk0Htik3J/w@public.gmane.org \
--cc=todd.fischer-9uBrGCPFOa1Wk0Htik3J/w@public.gmane.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).