Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: airlied@linux.ie, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: sprite init failure on pre-SNB is not a failure
Date: Thu, 12 Jan 2012 08:59:37 -0800	[thread overview]
Message-ID: <20120112085937.30da2174@jbarnes-desktop> (raw)
In-Reply-To: <CAKMK7uHHYBnUx+Pcxq0n3SHzZvzBZoVXffLbbFV2SMTTua1-HQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2805 bytes --]

On Thu, 12 Jan 2012 17:54:50 +0100
Daniel Vetter <daniel@ffwll.ch> wrote:

> On Thu, Jan 12, 2012 at 17:08, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > We can call the plane init function unconditionally, but don't need to
> > complain if it fails, since that will only happen if we're out of
> > memory (and other things will fail) or if we're on the wrong platform
> > (which is ok).
> >
> > And remove the DRM_ERRORs from the sprite code itself to avoid dmesg
> > spam.
> >
> > Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
> >
> > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> > index 29743de..e3bfa50 100644
> > --- a/drivers/gpu/drm/i915/intel_display.c
> > +++ b/drivers/gpu/drm/i915/intel_display.c
> > @@ -9027,12 +9027,9 @@ void intel_modeset_init(struct drm_device *dev)
> >
> >        for (i = 0; i < dev_priv->num_pipe; i++) {
> >                intel_crtc_init(dev, i);
> > -               if (HAS_PCH_SPLIT(dev)) {
> > -                       ret = intel_plane_init(dev, i);
> > -                       if (ret)
> > -                               DRM_ERROR("plane %d init failed: %d\n",
> > -                                         i, ret);
> > -               }
> > +               ret = intel_plane_init(dev, i);
> > +               if (ret)
> > +                       DRM_DEBUG_KMS("plane %d init failed: %d\n", i, ret);
> >        }
> >
> >        /* Just disable it once at startup */
> > diff --git a/drivers/gpu/drm/i915/intel_sprite.c b/drivers/gpu/drm/i915/intel_sprite.c
> > index b26e7c4..32909e3 100644
> > --- a/drivers/gpu/drm/i915/intel_sprite.c
> > +++ b/drivers/gpu/drm/i915/intel_sprite.c
> > @@ -466,10 +466,8 @@ intel_update_plane(struct drm_plane *plane, struct drm_crtc *crtc,
> >        mutex_lock(&dev->struct_mutex);
> >
> >        ret = intel_pin_and_fence_fb_obj(dev, obj, NULL);
> > -       if (ret) {
> > -               DRM_ERROR("failed to pin object\n");
> > +       if (ret)
> >                goto out_unlock;
> > -       }
> >
> >        intel_plane->obj = obj;
> >
> > @@ -632,10 +630,8 @@ intel_plane_init(struct drm_device *dev, enum pipe pipe)
> >        unsigned long possible_crtcs;
> >        int ret;
> >
> > -       if (!(IS_GEN6(dev) || IS_GEN7(dev))) {
> > -               DRM_ERROR("new plane code only for SNB+\n");
> > +       if (!(IS_GEN6(dev) || IS_GEN7(dev)))
> >                return -ENODEV;
> > -       }
> 
> Why not return 0; to avoid the "plane init" spam at kms debug level?
> After all, nothing failed, there's just no plane there to init ...

ENODEV actually does tell you why the init failed, in case you want to
look at the debug logs...

-- 
Jesse Barnes, Intel Open Source Technology Center

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2012-01-12 16:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-12 16:08 [PATCH] drm/i915: sprite init failure on pre-SNB is not a failure Jesse Barnes
2012-01-12 16:54 ` Daniel Vetter
2012-01-12 16:59   ` Jesse Barnes [this message]
2012-01-13 16:10     ` Keith Packard
2012-01-13 22:55       ` Daniel Vetter
2012-01-12 17:03 ` Keith Packard
2012-01-13 23:50 ` Keith Packard
2012-01-14  0:56   ` Jesse Barnes
2012-01-14  1:05   ` Jesse Barnes
2012-01-14  6:25     ` Keith Packard

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=20120112085937.30da2174@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.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