[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150916201657.GC19780@bremse.senecacollege.ca>
Date: Wed, 16 Sep 2015 13:16:57 -0700
From: Daniel Vetter <daniel@...ll.ch>
To: Daniel Stone <daniel@...ishbar.org>
Cc: Xinwei Kong <kong.kongxinwei@...ilicon.com>,
yinshengbao@...ilicon.com, xuyiping@...ilicon.com,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>, yanhaifeng@...ilicon.com,
dri-devel <dri-devel@...ts.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
andy.green@...aro.org, haojian.zhuang@...aro.org,
fangdechun@...ilicon.com, puck.chen@...ilicon.com,
ml.yang@...ilicon.com, gongyu@...ilicon.com, xuwei5@...ilicon.com,
liguozhu@...ilicon.com, qijiwen@...ilicon.com,
james.yanglong@...ilicon.com
Subject: Re: [PATCH RFC 0/8] Add New DRM Driver for Hisilicon's Hi6220 SoC
On Wed, Sep 16, 2015 at 04:23:35PM +0100, Daniel Stone wrote:
> The biggest issue though, is that this driver should become an atomic
> modesetting driver. Atomic modesetting, rather than sending small
> individual commands (enable CRTC, change plane position, etc) is based
> on validating and passing around complete sets of hardware state.
> Daniel Vetter's blog has an article on how to convert your driver:
> http://blog.ffwll.ch/2014/11/atomic-modeset-support-for-kms-drivers.html
Yeah, any new driver should really be built on top of atomic - it's a lot
more flexible than the old thing and it's also what you want long-term.
I've also just done a presenation about atomic for drivers:
http://people.freedesktop.org/~danvet/presentations/xdc-2015.pdf
Cheers, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists