From: Dave Jones <davej@redhat.com>
To: Dave Airlie <airlied@linux.ie>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [rfc][patch] DRM initial function table support.
Date: Tue, 31 Aug 2004 16:20:15 +0100 [thread overview]
Message-ID: <20040831152015.GC22978@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0408311409530.18657@skynet>
On Tue, Aug 31, 2004 at 02:11:11PM +0100, Dave Airlie wrote:
> Okay this is the first driver function table patch for the DRM, something
> similar has been running in DRM CVS for a month or so (underneath another
> 5-10 patches removing all the rest of the macros..)
I like this. Lots.
Mostly because of this..
(16:14:11:davej@delerium:~)$ grep ^-# foo.diff | wc -l
87
It's like someone revoked the drm folks preprocessor license 8-)
> One thing we've discussed on dri-devel was changing the
> if (dev->fn_tbl.function)
> dev->fn_tbl.function();
>
> to something else but in future patches I've had slightly more complex
> checks to do and this check looks to be the most obvious from a
> readability point of view, if the driver supports the function call it..
Looks ok, and pretty much matches similar conventions used in other
parts of the kernel.
> The other option was to use default noop fns, this also caused issues
> later on with some places where the code did more than just call the
> function..
>
> So please any comments on it?
One thing that would make things even nicer would be..
instead of this..
> +void gamma_driver_register_fns(drm_device_t *dev)
> +{
> + dev->fn_tbl.preinit = gamma_driver_preinit;
> + dev->fn_tbl.pretakedown = gamma_driver_pretakedown;
> + dev->fn_tbl.dma_ready = gamma_driver_dma_ready;
> + dev->fn_tbl.dma_quiescent = gamma_driver_dma_quiescent;
> + dev->fn_tbl.dma_flush_block_and_flush = gamma_flush_block_and_flush;
> + dev->fn_tbl.dma_flush_unblock = gamma_flush_unblock;
> +}
having a per-driver struct with regular C99 initialisers..
struct gamma_driver_fntbl {
.preinit = gamma_driver_preinit,
.pretakedown = gamma_driver_pretakedown,
.dma_ready = gamma_driver_dma_ready,
.dma_quiescent = gamma_driver_dma_quiescent,
.dma_flush_block_and_flush = gamma_flush_block_and_flush,
.dma_flush_unblock = gamma_flush_unblock,
};
Thanks for doing this work, it really is starting to look a little more
like a Linux driver 8-)
Dave
next prev parent reply other threads:[~2004-08-31 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 13:11 [rfc][patch] DRM initial function table support Dave Airlie
2004-08-31 15:20 ` Dave Jones [this message]
2004-08-31 16:07 ` Ian Romanick
2004-08-31 17:01 ` Christoph Hellwig
2004-08-31 17:52 ` Ian Romanick
2004-08-31 23:39 ` Dave Airlie
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=20040831152015.GC22978@redhat.com \
--to=davej@redhat.com \
--cc=airlied@linux.ie \
--cc=linux-kernel@vger.kernel.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