All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Archit Taneja <archit@ti.com>,
	dri-devel@lists.freedesktop.org, robdclark@gmail.com
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH v3 0/4] drm/omap: fix issues in omap_drv probe/remove
Date: Wed, 8 Jan 2014 15:22:46 +0200	[thread overview]
Message-ID: <52CD5126.60804@ti.com> (raw)
In-Reply-To: <1388654394-5708-1-git-send-email-archit@ti.com>

[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]

On 2014-01-02 11:19, Archit Taneja wrote:
> At the moment, the omapdrm driver doesn't work on panda/beagle when built-in
> the kernel. The problem is that omapdrm doesn't defer probe if resources like
> regulator/I2C etc are missing. The first patch fixes that.
> 
> The next 3 patches make sure that omapdrm module can be inserted and removed
> successively, and that omapdss is left in a consistent state when omapdrm is
> removed.
> 
> In the previous version of this series, there was a warning related to apply_irq
> being registered seen while removing omapdrm. This was a relatively scary
> warning, therefore, the "change dev_unload order" patch was added to make sure
> we don't see that.
> 
> After these fixes, I still see the warning below once in a while. I don't know
> how to fix it at the moment, but it's harmless and omapdrm is now usable again.
> These are critical fixes which I have posted since 3.12-rcs, it would be nice if
> they can go in as soon as possible.

These look ok to me:

Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ti.com>

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

      parent reply	other threads:[~2014-01-08 13:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-02  9:19 [PATCH v3 0/4] drm/omap: fix issues in omap_drv probe/remove Archit Taneja
2014-01-02  9:19 ` [PATCH v3 1/4] drm/omap: fix: Defer probe if an omapdss device requests for it at connect Archit Taneja
2014-01-02  9:19 ` [PATCH v3 2/4] drm/omap: fix: disconnect devices when omapdrm module is removed Archit Taneja
2014-01-02  9:19 ` [PATCH v3 3/4] drm/omap: fix: disable encoder before destroying it Archit Taneja
2014-01-02  9:19 ` [PATCH v3 4/4] drm/omap: fix: change dev_unload order Archit Taneja
2014-01-08 13:22 ` Tomi Valkeinen [this message]

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=52CD5126.60804@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=archit@ti.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robdclark@gmail.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.