From: Haneen Mohammed <hamohammed.sa@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, Sean Paul <seanpaul@google.com>,
Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH V3 0/3] Expanding the basic vkms features
Date: Thu, 24 May 2018 05:42:02 +0300 [thread overview]
Message-ID: <20180524024202.GA13492@Haneen> (raw)
In-Reply-To: <20180523091518.GU3438@phenom.ffwll.local>
On Wed, May 23, 2018 at 11:15:18AM +0200, Daniel Vetter wrote:
> On Mon, May 21, 2018 at 10:04:23PM -0300, Rodrigo Siqueira wrote:
> > This series of patches add a centralized initialization mechanism, a
> > single CRTC with a plane, an encoder, and extra module information.
> >
> > Changes in v2:
> > - Remove unused definitions
> > - Improve file names
> > - Improve code separation
> > - Remove unnecessary formats
>
> Oops, I merged v2 already. I think we need follow-up patches.
>
> > Changes in v3:
> > - Adds drm_crtc_helper_funcs with a simple atomic_check
>
> Sorry for the late comment on v2, but I think we need to figure out why
> this goes boom first. It imo shouldn't.
>
> > - Adds extra hooks for drm_connector_funcs hooks (reset,
> > atomic_duplicate_state, atomic_destroy_state)
>
> Hm, reset shouldn't be required. Why do you need it?
>
I've checked the code, and I think the memory for [plane/connector/crtc]
states that are used later in duplicate/destroy are allocated in drm_atomic_helper_*_reset.
Otherwise checking /sys/kernel/debug/dri/0/state or running the igt
tests causes null pointer dereference error.
> Wrt duplicate/destroy state, those are mandatory. I think it'd be good to
> have checks for those in the drm_*_init functions, but only for atomic
> drivers. You can use drm_drv_uses_atomic_modeset() and WARN_ON(). There's
> a bunch of examples already for checking for this stuff, see e.g.
> dma_fence_init().
>
> > - Adds drm_connector_helper_funcs
> > - Adds drm_plane_helper_funcs
>
> Same here, would be good to add WARN_ON to the relevant _init() functions
> to make sure all the mandatory stuff is there to begin with.
>
> Since Rodrigo has typed the fixes to vkms already, could you Haneen look
> into adding these checks to the core drm core?
>
Sure, I'll work on that.
> Thanks, Daniel
>
> > - Changes in the commit messages
> >
> > Rodrigo Siqueira (3):
> > drm/vkms: Add mode_config initialization
> > drm/vkms: Add basic CRTC initialization
> > drm/vkms: Add extra information about vkms
> >
> > drivers/gpu/drm/Kconfig | 8 +-
> > drivers/gpu/drm/vkms/Makefile | 2 +-
> > drivers/gpu/drm/vkms/vkms_crtc.c | 47 ++++++++++++
> > drivers/gpu/drm/vkms/vkms_drv.c | 55 +++++---------
> > drivers/gpu/drm/vkms/vkms_drv.h | 33 +++++++-
> > drivers/gpu/drm/vkms/vkms_output.c | 118 +++++++++++++++++++++++++++++
> > drivers/gpu/drm/vkms/vkms_plane.c | 62 +++++++++++++++
> > 7 files changed, 285 insertions(+), 40 deletions(-)
> > create mode 100644 drivers/gpu/drm/vkms/vkms_crtc.c
> > create mode 100644 drivers/gpu/drm/vkms/vkms_output.c
> > create mode 100644 drivers/gpu/drm/vkms/vkms_plane.c
> >
> > --
> > 2.17.0
> >
>
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-05-24 2:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 1:04 [PATCH V3 0/3] Expanding the basic vkms features Rodrigo Siqueira
2018-05-22 1:04 ` [PATCH V3 1/3] drm/vkms: Add mode_config initialization Rodrigo Siqueira
2018-05-22 1:06 ` [PATCH V3 2/3] drm/vkms: Add basic CRTC initialization Rodrigo Siqueira
2018-05-22 2:57 ` Haneen Mohammed
2018-05-22 12:02 ` Rodrigo Siqueira
2018-10-22 15:30 ` Emil Velikov
2018-10-22 23:57 ` Rodrigo Siqueira
2018-10-23 12:40 ` Emil Velikov
2018-05-22 1:07 ` [PATCH V3 3/3] drm/vkms: Add extra information about vkms Rodrigo Siqueira
2018-05-23 9:15 ` [PATCH V3 0/3] Expanding the basic vkms features Daniel Vetter
2018-05-24 2:42 ` Haneen Mohammed [this message]
2018-05-24 8:15 ` Daniel Vetter
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=20180524024202.GA13492@Haneen \
--to=hamohammed.sa@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=rodrigosiqueiramelo@gmail.com \
--cc=seanpaul@google.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