From: Inki Dae <inki.dae@samsung.com>
To: airlied@linux.ie, daniel@ffwll.ch
Cc: linux-samsung-soc@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: [GIT PULL v2] exynos-drm-next
Date: Mon, 17 Apr 2023 19:06:24 +0900 [thread overview]
Message-ID: <20230417100624.35229-1-inki.dae@samsung.com> (raw)
In-Reply-To: CGME20230417100624epcas1p3d39ab3b88da18da0b365d67ad1062086@epcas1p3.samsung.com
Hi Dave and Daniel,
Sorry for late. Just one patch series which converts Exynos's fbdev code
to struct drm_client.
Please let me know if there is any problem.
Thanks,
Inki Dae
The following changes since commit e82c98f2ca439356d5595ba8c9cd782f993f6f8c:
Merge tag 'amd-drm-next-6.4-2023-04-14' of https://gitlab.freedesktop.org/agd5f/linux into drm-next (2023-04-17 10:54:59 +1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos tags/exynos-drm-next-for-v6.4-2
for you to fetch changes up to 49953b70e7d38dd714f4cf22224e8a7ce14f3c48:
drm/exynos: Implement fbdev emulation as in-kernel client (2023-04-17 16:47:55 +0900)
----------------------------------------------------------------
A patch series for implementing fbdev emulation as in-kernel client.
- This patch series refactors fbdev callbacks to DRM client functions and
simplifies fbdev emulation initialization including some code cleanups.
The changes make fbdev emulation behave like a regular DRM client.
----------------------------------------------------------------
Thomas Zimmermann (5):
drm/exynos: Remove exynos_gem from struct exynos_drm_fbdev
drm/exynos: Remove struct exynos_drm_fbdev
drm/exynos: Remove fb_helper from struct exynos_drm_private
drm/exynos: Initialize fbdev DRM client
drm/exynos: Implement fbdev emulation as in-kernel client
drivers/gpu/drm/exynos/exynos_drm_drv.c | 13 +--
drivers/gpu/drm/exynos/exynos_drm_drv.h | 2 -
drivers/gpu/drm/exynos/exynos_drm_fb.c | 2 -
drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 174 +++++++++++++++---------------
drivers/gpu/drm/exynos/exynos_drm_fbdev.h | 20 +---
5 files changed, 94 insertions(+), 117 deletions(-)
next parent reply other threads:[~2023-04-17 10:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230417100624epcas1p3d39ab3b88da18da0b365d67ad1062086@epcas1p3.samsung.com>
2023-04-17 10:06 ` Inki Dae [this message]
[not found] <CGME20241106010943epcas1p1f43d635384661d8dc4a401c5b82b25af@epcas1p1.samsung.com>
2024-11-06 1:09 ` [GIT PULL v2] exynos-drm-next Inki Dae
[not found] <CGME20181214072711epcas2p4f9d1016da37bae403a9416d00a1c0e78@epcas2p4.samsung.com>
2018-12-14 7:27 ` Inki Dae
2018-12-14 16:11 ` Daniel Vetter
2018-12-14 16:42 ` Daniel Vetter
[not found] <CGME20180525063159epcas1p488f55ec164803d9d7e515421dcac3fee@epcas1p4.samsung.com>
2018-05-25 6:31 ` Inki Dae
2014-04-04 12:49 Inki Dae
-- strict thread matches above, loose matches on Subject: below --
2013-07-04 7:31 Inki Dae
2013-02-15 4:24 [GIT PULL] exynos-drm-next Inki Dae
2013-02-21 6:40 ` [GIT PULL v2] exynos-drm-next Inki Dae
2012-11-29 12:11 Inki Dae
2012-11-29 14:34 ` Daniel Vetter
2012-11-30 5:27 ` Inki Dae
2012-11-30 16:28 ` Daniel Vetter
2012-10-04 2:12 [GIT PULL] exynos-drm-next Inki Dae
2012-10-05 11:04 ` [GIT PULL v2] exynos-drm-next Inki Dae
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=20230417100624.35229-1-inki.dae@samsung.com \
--to=inki.dae@samsung.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-samsung-soc@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox