From: Dave Airlie <airlied@gmail.com>
To: dri-devel@lists.freedesktop.org
Subject: drm/amdgpu: start using graphics object ids from DAL.
Date: Thu, 14 Apr 2016 12:56:03 +1000 [thread overview]
Message-ID: <1460602570-20641-1-git-send-email-airlied@gmail.com> (raw)
DAL has a concept of storing the graphics object ids in a special
small struct, and adding type safety to them.
I'm starting to contemplate bringing some pieces of DAL into the
mainline modesetting code (like the bios parser for a start),
and I think this is the best first step in that direction.
This series converts connectors, encoders and crtcs id to the
DAL objects. I haven't done PLLs yet they are a bit messier and
I probably need to think about them a bit more.
Also DAL doesn't support any of the DVO/external encoders, I've no idea
if they even exist on DCE8 or newer GPUs, so I've done a separate
patch to drop them.
Dave.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-04-14 2:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 2:56 Dave Airlie [this message]
2016-04-14 2:56 ` [PATCH 1/7] drm/amdgpu: drop apply quirks for now Dave Airlie
2016-04-14 2:56 ` [PATCH 2/7] drm/amdgpu: introduce grph object id from DAL Dave Airlie
2016-04-14 2:56 ` [PATCH 3/7] drm/amdgpu: introduce graphics object id helpers Dave Airlie
2016-04-15 18:54 ` Emil Velikov
2016-04-14 2:56 ` [PATCH 4/7] drm/amdgpu: use graphics objects for connectors Dave Airlie
2016-04-14 2:56 ` [PATCH 5/7] [RFC] drm/amdgpu: drop DVO encoders support Dave Airlie
2016-04-14 14:08 ` Harry Wentland
2016-04-14 2:56 ` [PATCH 6/7] drm/amdgpu: convert encoders to using the graphics object ids Dave Airlie
2016-04-14 2:56 ` [PATCH 7/7] drm/amdgpu: convert crtc to using " Dave Airlie
2016-04-14 8:25 ` drm/amdgpu: start using graphics object ids from DAL Christian König
2016-04-15 12:46 ` Harry Wentland
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=1460602570-20641-1-git-send-email-airlied@gmail.com \
--to=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.