From: Mike Chan <mike@android.com>
To: Wang Sawsd-A24013 <cqwang@motorola.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2] Support OMAP3 VC adaptation with different Power IC
Date: Thu, 25 Jun 2009 12:25:58 -0700 [thread overview]
Message-ID: <4A43CF46.60706@android.com> (raw)
In-Reply-To: <B00E06E2766C2744B022DE9BAF3C59D5465B7B@zmy16exm69.ds.mot.com>
Wang Sawsd-A24013 wrote:
>> -----Original Message-----
>> From: Mike Chan [mailto:mike@android.com]
>> Sent: 2009年6月25日 9:25
>> To: Wang Sawsd-A24013
>> Cc: linux-omap@vger.kernel.org
>> Subject: Re: [PATCH 1/2] Support OMAP3 VC adaptation with
>> different Power IC
>>
>> Wang Sawsd-A24013 wrote:
>>
>>> From c1aba8ba7af3ddd16346d95795bda71e65baa4d0 Mon Sep 17
>>>
>> 00:00:00 2001
>>
>>> From: Chunqiu Wang <cqwang@motorola.com>
>>> Date: Wed, 24 Jun 2009 06:48:52 +0800
>>> Subject: [PATCH] Support OMAP3 VC adaptation with different Power IC
>>>
>>> Current OMAP SmartReflex driver only supports TI Triton
>>> Power IC, add a callback to make it possible to use
>>> different PowerIC and use different settings to
>>> configure OMAP3 Voltage Controller for DVFS
>>>
>>> Board file can setup a new function to have different settings
>>> on SR to configure their Power IC for voltage scaling
>>>
>>> Signed-off-by: Chunqiu Wang <cqwang@motorola.com>
>>> ---
>>> arch/arm/mach-omap2/smartreflex.c | 13 +++++++++++++
>>> arch/arm/mach-omap2/smartreflex.h | 4 ++++
>>> arch/arm/plat-omap/Kconfig | 2 +-
>>> 3 files changed, 18 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/arch/arm/mach-omap2/smartreflex.c
>>> b/arch/arm/mach-omap2/smartreflex.c
>>> index 9d462e3..bacf602 100644
>>> --- a/arch/arm/mach-omap2/smartreflex.c
>>> +++ b/arch/arm/mach-omap2/smartreflex.c
>>> @@ -52,6 +52,8 @@ struct omap_sr {
>>>
>>> #define SR_REGADDR(offs) (sr->srbase_addr + offset)
>>>
>>> +static omap3_voltagescale_vcbypass_t omap3_volscale_vcbypass_fun;
>>>
>>>
>> Perhaps use
>> static int (*omap3_volscale_vcbypass_fun) (u32, u32, u8, u8);
>>
>> This gets rid of the compiler warning on incompatible pointer
>> types when
>> you register a function via omap3_voltagescale_vcbypass_setup().
>>
>> -- Mike
>>
> Thanks Mike, but we do not see the warnning with the original
> Code, note this patch is slightly different with the one we sent
> To you based on K29, this new patch have four parameters
> Sinc some change has been made in the
> sr_voltagescale_vcbypass to add two more parameters.
>
> Is your warnning caused by this?
>
>
This patch stand-alone doesn't give me any warnings. Its only when you
hook into this from your board file. Might be the compiler I'm using.
I used this patch + modified version of the patches you sent me before
to get the two working. (Yes, 4 params).
-- MIke
> Thanks,
> Chunqiu
>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-25 19:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 0:15 [PATCH 1/2] Support OMAP3 VC adaptation with different Power IC Wang Sawsd-A24013
2009-06-24 0:19 ` Kevin Hilman
2009-06-24 16:10 ` Wang Sawsd-A24013
2009-06-25 17:38 ` Kevin Hilman
2009-06-25 20:10 ` Wang Sawsd-A24013
2009-06-25 1:25 ` Mike Chan
2009-06-25 16:00 ` Wang Sawsd-A24013
2009-06-25 19:25 ` Mike Chan [this message]
2009-06-25 20:12 ` Wang Sawsd-A24013
2009-06-25 21:18 ` Mike Chan
-- strict thread matches above, loose matches on Subject: below --
2009-06-25 23:55 sawsd wang
2009-06-26 14:57 ` Kevin Hilman
2009-09-30 18:57 ` Kevin Hilman
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=4A43CF46.60706@android.com \
--to=mike@android.com \
--cc=cqwang@motorola.com \
--cc=linux-omap@vger.kernel.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.