All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: Kevin Hilman <khilman@mvista.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH] dmtimer posting
Date: Wed, 19 Mar 2008 17:58:35 +0200	[thread overview]
Message-ID: <20080319155835.GE14860@atomide.com> (raw)
In-Reply-To: <3B6D69C3A9EBCA4BA5DA60D91302742903CCA4F9@dlee13.ent.ti.com>

* Woodruff, Richard <r-woodruff2@ti.com> [080319 16:47]:
> Hi,
> 
> > Cool. Here's a version that gets rid of the lookup table by encoding
> the
> > posted write pending bit into the reg offset. This should be OK, as
> the
> > functions are used within dmtimer.c only.
> 
> Ok, that looks nice and will generate a bit better code.  I thought
> briefly on that it but wanted the change to be small and was a little
> worried someone might use the offset somewhere else.  But, they way you
> did it makes the 2nd aspect go away.
> 
> * You have defined WPSHIFT to 8.  However, that bit is currently taken
> by WP_TOCR.  I chose 15 hoping if the register expanded it would be the
> last one in a u_int16 and still can be encoded in an op code as a shift
> value.  A 16 would be a good codegen value, but always assume u_int32
> register.  As the registers are u_int32 in current implementations,
> probably 16 is a better value.

OK, good catch.

> > The init of other timers into posted mode is not done yet, so I
> changed
> > the timer->posted handling too.
> 
> Not inited in software, BUT the power on reset of the timer module is to
> posted mode in reset.  Its better to have someone shut it off in both
> places as its on by default.

OK

> I'll tweak the points mentioned and fix a typo in the description and
> send a version.

OK

Tony

  reply	other threads:[~2008-03-19 19:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ae36f8040803061301y6e0823a8pbdf0b6f0b47e5639@mail.gmail.com>
     [not found] ` <3B6D69C3A9EBCA4BA5DA60D91302742903AFC880@dlee13.ent.ti.com>
     [not found]   ` <20080307071454.GC7635@atomide.com>
2008-03-15  0:24     ` [PATCH] [RFC] dmtimer library is very inefficient today Woodruff, Richard
2008-03-18 18:33       ` Kevin Hilman
2008-03-18 18:51         ` Woodruff, Richard
2008-03-19  2:40         ` [PATCH] dmtimer posting Woodruff, Richard
2008-03-19 14:15           ` Tony Lindgren
2008-03-19 14:47             ` Woodruff, Richard
2008-03-19 15:58               ` Tony Lindgren [this message]
2008-03-19 22:13                 ` Woodruff, Richard
2008-03-20 11:57                   ` Tony Lindgren
2008-03-20 12:19                     ` Tony Lindgren
2008-03-21  0:13                       ` Woodruff, Richard
2008-03-21  0:01                     ` Woodruff, Richard
2008-03-31 10:49                       ` Tony Lindgren
2008-03-31 12:18                         ` Woodruff, Richard
2008-04-02  7:23                           ` Tony Lindgren
2008-04-04  4:50                             ` Woodruff, Richard
2008-04-04 20:03                             ` [PATCH] timer optimization part 2 Woodruff, Richard
2008-04-04 20:23                               ` Idle picture for those interested Woodruff, Richard
2008-04-04 20:56                                 ` David Brownell
2008-04-04 21:45                                   ` Woodruff, Richard
2008-04-04 21:56                                   ` Woodruff, Richard
2008-04-04 22:07                                     ` David Brownell
     [not found]                             ` <49DA3A9F04A0E5498FF06EFCC343DCF90203DA56FF@dlee13.ent.ti.com>
2008-05-07 23:46                               ` [PATCH] timer optimization part 2 Woodruff, Richard
2008-05-08 17:40                                 ` Tony Lindgren
2008-03-19 19:52         ` [PATCH] [RFC] dmtimer library is very inefficient today Ladislav Michl
2008-03-20  8:58           ` Tony Lindgren

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=20080319155835.GE14860@atomide.com \
    --to=tony@atomide.com \
    --cc=khilman@mvista.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=r-woodruff2@ti.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 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.