mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: "Wang J.W." <Jianwei.Wang@freescale.com>
Cc: Daniel Vetter <daniel@ffwll.ch>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"airlied@linux.ie" <airlied@linux.ie>,
	"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
	"mark.yao@rock-chips.com" <mark.yao@rock-chips.com>,
	Scott Wood <scottwood@freescale.com>,
	Huan Wang <alison.wang@freescale.com>,
	Xiubo Li <lixiubo@cmss.chinamobile.com>
Subject: Re: [PATCH v6 1/4] drm/layerscape: Add Freescale DCU DRM driver
Date: Fri, 10 Jul 2015 18:59:49 +0200	[thread overview]
Message-ID: <20150710165949.GE3736@phenom.ffwll.local> (raw)
In-Reply-To: <DM2PR0301MB1229FD0A506ABD3AE7A0C7DF9F9F0@DM2PR0301MB1229.namprd03.prod.outlook.com>

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@ffwll.ch] On Behalf Of Daniel
> > Vetter
> > Sent: Friday, July 10, 2015 4:00 PM
> > To: Wang Jianwei-B52261
> > Cc: dri-devel@lists.freedesktop.org; linux-kernel@vger.kernel.org; linux-
> > arm-kernel@lists.infradead.org; devicetree@vger.kernel.org;
> > airlied@linux.ie; daniel.vetter@ffwll.ch; mark.yao@rock-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

  parent reply	other threads:[~2015-07-10 16:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10  7:26 Jianwei Wang
2015-07-10  7:26 ` [PATCH v6 2/4] drm/panel: simple: Add support for NEC NL4827HC19-05B 480x272 panel Jianwei Wang
2015-07-10  7:26 ` [PATCH v6 3/4] arm/dts/ls1021a: Add DCU dts node Jianwei Wang
2015-07-10  7:26 ` [PATCH v6 4/4] arm/dts/ls1021a: Add a TFT LCD panel " Jianwei Wang
2015-07-10  7:59 ` [PATCH v6 1/4] drm/layerscape: Add Freescale DCU DRM driver Daniel Vetter
     [not found]   ` <DM2PR0301MB1229FD0A506ABD3AE7A0C7DF9F9F0@DM2PR0301MB1229.namprd03.prod.outlook.com>
2015-07-10 16:59     ` Daniel Vetter [this message]
     [not found] ` <DM2PR0301MB12295112F1CC589DE0FA47899F9F0@DM2PR0301MB1229.namprd03.prod.outlook.com>
2015-07-10  8:42   ` Emil Velikov

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=20150710165949.GE3736@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=Jianwei.Wang@freescale.com \
    --cc=airlied@linux.ie \
    --cc=alison.wang@freescale.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lixiubo@cmss.chinamobile.com \
    --cc=mark.yao@rock-chips.com \
    --cc=scottwood@freescale.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

all inboxes | Powered by JetHome®