From: Jon Hunter <jon-hunter@ti.com>
To: "Cousson, Benoit" <b-cousson@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH 0/9] ARM: OMAP: DMTIMER clean-up in preparation for device-tree
Date: Wed, 16 May 2012 08:34:06 -0500 [thread overview]
Message-ID: <4FB3ACCE.1050103@ti.com> (raw)
In-Reply-To: <4FB37356.9040001@ti.com>
Hi Benoit,
On 05/16/2012 04:28 AM, Cousson, Benoit wrote:
> Hi Jon,
>
> On 5/16/2012 1:35 AM, Jon Hunter wrote:
>> From: Jon Hunter<jon-hunter@ti.com>
>>
>> In order to migrate the dmtimer driver to support device-tree I found
>> that it
>> was first necessary to clean-up the timer platform data. The goal of this
>> series is to simplify the timer platform data structure from ...
>>
>> struct dmtimer_platform_data {
>> int (*set_timer_src)(struct platform_device *pdev, int source);
>> int timer_ip_version;
>> u32 needs_manual_reset:1;
>> bool reserved;
>> bool loses_context;
>> int (*get_context_loss_count)(struct device *dev);
>> };
>>
>> to ...
>>
>> struct dmtimer_platform_data {
>> int (*set_timer_src)(struct platform_device *pdev, int source);
>
> I guess that custom set_timer_src should not be there at all anymore.
> Well at least for OMAP2+.
> We should just use the regular clock API to change the parent. I do not
> see why we should add that wrapper on top of the clock API and thus
> store some internal clock name inside the timer device init code.
Yes I really wanted to eliminate that function pointer too, but it was a
little trickier. The OMAP2+ code does use the clock framework to switch
the parent already, but the problem is that the OMAP1 code does not. So
we cannot have a common function for OMAP1 and OMAP2+.
One option would be to move the OMAP2+ function into the dmtimer because
it already uses the clock framework and then only populate the function
pointer for OMAP1. However, I admit this is ugly.
Let me look at this some more to see what I can do. I can at least test
on my old omap1 board now for prototyping :-)
Did you look at the rest of the series? Let me know if you are ok with
the approach and have any concerns on my hwmod changes/fix-ups ;-)
Cheers
Jon
next prev parent reply other threads:[~2012-05-16 13:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 23:35 [PATCH 0/9] ARM: OMAP: DMTIMER clean-up in preparation for device-tree Jon Hunter
2012-05-16 9:28 ` Cousson, Benoit
2012-05-16 13:34 ` Jon Hunter [this message]
2012-05-17 10:29 ` Cousson, Benoit
2012-05-16 20:14 ` Jon Hunter
2012-05-16 23:30 ` Paul Walmsley
2012-05-17 15:56 ` Jon Hunter
2012-05-17 16:48 ` Paul Walmsley
2012-05-22 20:33 ` Jon Hunter
2012-05-17 5:07 ` DebBarma, Tarun Kanti
2012-05-17 16:00 ` Jon Hunter
2012-06-04 14:11 ` Jon Hunter
2012-05-16 14:37 ` Santosh Shilimkar
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=4FB3ACCE.1050103@ti.com \
--to=jon-hunter@ti.com \
--cc=b-cousson@ti.com \
--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;
as well as URLs for NNTP newsgroup(s).