linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tomi.valkeinen@ti.com (Tomi Valkeinen)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP: DSS hwmod/reset fixes for 3.2
Date: Tue, 15 Nov 2011 09:06:36 +0200	[thread overview]
Message-ID: <1321340796.1895.8.camel@deskari> (raw)
In-Reply-To: <20111114220423.GQ31337@atomide.com>

On Mon, 2011-11-14 at 14:04 -0800, Tony Lindgren wrote:
> * Paul Walmsley <paul@pwsan.com> [111114 13:05]:
> > On Mon, 14 Nov 2011, Tony Lindgren wrote:
> > 
> > > I suggest we only merge the ones with "fix" in the subject during the -rc
> > > cycle. The others add new features for the reset, so they should wait until
> > > v3.3 merge window.
> > 
> > Most of the other patches in the branch discuss what they fix in the patch 
> > descriptions, rather than the subject lines.  Do you want the subject 
> > lines rewritten to highlight this?
> 
> Well we should only merge major bugs and regressions during the -rc cycle.
> It seems that at least "OMAP: HWMOD: Unify DSS resets for OMAPs" has high
> flame potential based on that? Maybe we should wait until the next merge
> window to start removing some of these workarounds?

I'm not sure what you mean...

The "Unify DSS resets..." patch itself fixes only a minor bug: "This
causes causes the HWMOD reset to fail for dss_dispc and dss_rfbi". But
it makes the next patch, "Ensure DSS works correctly...", possible. And
that patch fixes a bigger bug, DSS or the whole device hanging if the
bootloader had enabled the display (which I believe is the default on
the shipped beagles/pandas).

There's one patch in the series that is not a fix, though: "ARM: OMAP4:
HWMOD: remove extra clocks". I'm fine with queuing that for the next
merge window. But most of the patches have now somehow missed two merge
windows, and I'd really like to get them in.

 Tomi

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20111115/a4c8aab2/attachment.sig>

  reply	other threads:[~2011-11-15  7:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-07  0:07 [GIT PULL] ARM: OMAP: DSS hwmod/reset fixes for 3.2 Paul Walmsley
2011-11-05  0:35 ` Tony Lindgren
2011-11-08  7:50   ` Paul Walmsley
2011-11-08 10:08     ` Tomi Valkeinen
2011-11-08 10:33       ` Paul Walmsley
2011-11-08 12:14         ` Tomi Valkeinen
2011-11-14 20:46           ` Tony Lindgren
2011-11-14 21:40             ` Paul Walmsley
2011-11-14 22:04               ` Tony Lindgren
2011-11-15  7:06                 ` Tomi Valkeinen [this message]
2011-11-19  0: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=1321340796.1895.8.camel@deskari \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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).