From: "stanley.miao" <stanley.miao@windriver.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH v2] OMAP: Fix McBSP spin_lock deadlock.
Date: Wed, 14 Jan 2009 09:39:05 +0800 [thread overview]
Message-ID: <1231897145.29324.31.camel@localhost> (raw)
In-Reply-To: <20090112104611.GB9373@atomide.com>
On Mon, 2009-01-12 at 12:46 +0200, Tony Lindgren wrote:
> * stanley.miao <stanley.miao@windriver.com> [090112 12:34]:
> > On Thu, 2009-01-08 at 15:33 +0200, Tony Lindgren wrote:
> > > * stanley.miao <stanley.miao@windriver.com> [081107 15:47]:
> > > > This solution keeps the virtual clock in place and enable the child
> > > > clocks before enable the virtual clock. So, any comments ?
> > >
> > > What if we just removed the custom clock and had a struct **clk
> > > in struct omap_mcbsp that contains the clocks for each instance?
> >
> > It works. This is what I did in my first patch.
>
> OK, sorry for all this going back and forth..
It's OK. In order to make the code better, it is worth a little more
job.
> We still don't
> have a good long term solution on how to handle different clocks..
>
<snip>
>
> Sounds like we should just apply your original patch, then figure
> out a good long term approacth.
>
> Can you please repost your first version of the patch?
I will post the patch V3.
Stanley.
>
> Regards,
>
> Tony
next prev parent reply other threads:[~2009-01-14 1:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 12:44 [PATCH v2] OMAP: Fix McBSP spin_lock deadlock Stanley.Miao
2008-11-07 13:52 ` stanley.miao
2009-01-08 13:33 ` Tony Lindgren
2009-01-12 10:42 ` stanley.miao
2009-01-12 10:46 ` Tony Lindgren
2009-01-14 1:39 ` stanley.miao [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-13 9:08 Eero Nurkkala
2009-01-13 10:06 ` 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=1231897145.29324.31.camel@localhost \
--to=stanley.miao@windriver.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 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.