From: Daniel Vetter <daniel@ffwll.ch>
To: "Cheng, Yao" <yao.cheng@intel.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Vetter, Daniel" <daniel.vetter@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Jiang, Fei" <fei.jiang@intel.com>
Subject: Re: [RFC PATCH 1/3] drm/i915: add vxd392 bridge in i915
Date: Sun, 19 Oct 2014 13:27:11 +0200 [thread overview]
Message-ID: <20141019112711.GL26941@phenom.ffwll.local> (raw)
In-Reply-To: <8FF7D634BEE4C2428EFFAB6B7E919E4B017BCFE7@shsmsx102.ccr.corp.intel.com>
On Thu, Oct 16, 2014 at 03:05:07PM +0000, Cheng, Yao wrote:
> > Ok, bunch of comments. First a high-level one: I think this qualifies as a new
> > subsystem of i915, and so it would be good to extract this into a new file
> > (i915_ved.c maybe), including adding kerneldoc for the setup function, a
> > short DOC: overview section and pulling it all into the drm kerneldoc
> > (probably a new subsection in the driver core section).
> >
> > Aside from the lack of documentation just a few small comments below.
> > Overall I really like how cleanly we can integrate vxd support into i915, so
> > good work.
>
> I915_ved.c sounds to be a good place for these code, thx for this suggestion!
>
> For the kerneldoc, I'll add a subsection in the core section for your review.
Yeah, i915 driver core section sounds like the right place. Btw there's a
small blog post from me with some tips for how to go about this:
http://blog.ffwll.ch/2014/06/documentation-for-drmi915.html
> > > +
> > > +static void valleyview_ved_cleanup(struct drm_device *dev) {
> > > + int irq;
> > > + struct drm_i915_private *dev_priv = dev->dev_private;
> > > +
> > > + irq = platform_get_irq(dev_priv->ved_platdev, 0);
> > > + if (irq >= 0)
> > > + irq_free_desc(irq);
> > > +
> > > + platform_device_unregister(dev_priv->ved_platdev);
> >
> > I think you should unregister the platform device _before_ you free the irq.
> > Otherwise the driver cleanup might freak out. Aside: Does the module reload
> > test for i915 in i-g-t still work with the vxd driver loaded on vlv? Iirc you need
> > to manually unload the vxd driver first to avoid inherit races in the platform
> > device support code, so if that's the case you need to supply a patch for igt,
> > too.
>
> Sorry, what is i-g-t? I'll follow your suggestion, test i-g-t, and patch it if needed.
i-g-t is the i915 kernel driver regression test suite. For a quick intro
see:
http://blog.ffwll.ch/2013/08/recent-drmi915-testsuite-improvements.html
The igt repo is at
http://cgit.freedesktop.org/xorg/app/intel-gpu-tools/
The README file in there also has some good information.
Cheers, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-10-19 11:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 12:15 [RFC PATCH 0/3] drm driver for baytrail's vxd392 Yao Cheng
2014-10-13 12:15 ` [RFC PATCH 1/3] drm/i915: add vxd392 bridge in i915 Yao Cheng
2014-10-14 13:26 ` Jani Nikula
2014-10-15 2:02 ` [Intel-gfx] " Cheng, Yao
2014-10-16 10:15 ` Daniel Vetter
2014-10-16 15:05 ` Cheng, Yao
2014-10-19 11:27 ` Daniel Vetter [this message]
2014-10-13 12:15 ` [RFC PATCH 2/3] drm/ipvr: drm driver for vxd392 Yao Cheng
2014-10-13 14:26 ` David Herrmann
2014-10-15 2:14 ` Cheng, Yao
2014-10-16 9:46 ` David Herrmann
2014-10-16 10:28 ` Daniel Vetter
2014-10-16 13:39 ` [Intel-gfx] " Cheng, Yao
2014-10-16 13:47 ` David Herrmann
2014-10-19 11:28 ` Daniel Vetter
2014-10-14 11:53 ` [RFC PATCH 0/3] drm driver for baytrail's vxd392 Thierry Reding
2014-10-14 15:50 ` [Intel-gfx] " Sean V Kelley
2014-10-15 2:04 ` Cheng, Yao
2014-10-15 8:13 ` [Intel-gfx] " Thierry Reding
2014-10-15 8:18 ` Stéphane Marchesin
2014-10-15 8:31 ` Thierry Reding
2014-10-16 10:34 ` [Intel-gfx] " Daniel Vetter
2014-10-16 18:42 ` Rob Clark
2014-10-17 0:40 ` Jiang, Fei
2014-10-16 11:45 ` Daniel Vetter
2014-10-16 14:36 ` [Intel-gfx] " Cheng, Yao
2014-10-16 16:26 ` Sean V Kelley
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=20141019112711.GL26941@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fei.jiang@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=yao.cheng@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox