linux-kernel - Re: [PATCH v6 1/4] drm/layerscape: Add Freescale DCU DRM driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20150710165949.GE3736@phenom.ffwll.local>
Date:	Fri, 10 Jul 2015 18:59:49 +0200
From:	Daniel Vetter <daniel@...ll.ch>
To:	"Wang J.W." <Jianwei.Wang@...escale.com>
Cc:	Daniel Vetter <daniel@...ll.ch>,
	"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"airlied@...ux.ie" <airlied@...ux.ie>,
	"daniel.vetter@...ll.ch" <daniel.vetter@...ll.ch>,
	"mark.yao@...k-chips.com" <mark.yao@...k-chips.com>,
	Scott Wood <scottwood@...escale.com>,
	Huan Wang <alison.wang@...escale.com>,
	Xiubo Li <lixiubo@...s.chinamobile.com>
Subject: Re: [PATCH v6 1/4] drm/layerscape: Add Freescale DCU DRM driver

On Fri, Jul 10, 2015 at 10:43:11AM +0000, Wang J.W. wrote:
> Hi Daniel,
> 
> Thank you very much for your review!
> See below...
> 
> > -----Original Message-----
> > From: Daniel Vetter [mailto:daniel.vetter@...ll.ch] On Behalf Of Daniel
> > Vetter
> > Sent: Friday, July 10, 2015 4:00 PM
> > To: Wang Jianwei-B52261
> > Cc: dri-devel@...ts.freedesktop.org; linux-kernel@...r.kernel.org; linux-
> > arm-kernel@...ts.infradead.org; devicetree@...r.kernel.org;
> > airlied@...ux.ie; daniel.vetter@...ll.ch; mark.yao@...k-chips.com; Wood
> > Scott-B07421; Wang Huan-B18965; Xiubo Li
> > Subject: Re: [PATCH v6 1/4] drm/layerscape: Add Freescale DCU DRM driver
> > 
> > On Fri, Jul 10, 2015 at 03:26:52PM +0800, Jianwei Wang wrote:
> > > +	.atomic_check = fsl_dcu_drm_encoder_atomic_check,
> > 
> > .atomic_check is optional
> > 
> 
> I try to remove .atomic_check, but it will cause CPU hang when starting up
> And I find this in drivers/gpu/drm/drm_atomic_helper.c
> 
>  293                 if (funcs->atomic_check) {
>  294                         ret = funcs->atomic_check(encoder, crtc_state,
>  295                                                   conn_state);
>  296                         if (ret) {
>  297                                 DRM_DEBUG_ATOMIC("[ENCODER:%d:%s] check failed\n",
>  298                                                  encoder->base.id, encoder->name);
>  299                                 return ret;
>  300                         }
>  301                 } else {
>  302                         ret = funcs->mode_fixup(encoder, &crtc_state->mode,
>  303                                                 &crtc_state->adjusted_mode);
>  304                         if (!ret) {
>  305                                 DRM_DEBUG_ATOMIC("[ENCODER:%d:%s] fixup failed\n",
>  306                                                  encoder->base.id, encoder->name);
>  307                                 return -EINVAL;
>  308                         }
>  309                 }
> It means that I have to implement at least one of atomic_check and mode_fixup.
> So I reserve atomic_check.
> Is there problem? Please give me some more comments if necessary. Thanks!

Ah sorry you are right, atomic check is not optional. Unfortunately the
optional-or-not thing has grown a bit organically so there's no clear
rules.
-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/