From: Sui Jingfeng <sui.jingfeng@linux.dev>
To: Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Lucas Stach <l.stach@pengutronix.de>,
Russell King <linux+etnaviv@armlinux.org.uk>,
Christian Gmeiner <christian.gmeiner@gmail.com>
Cc: David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
etnaviv@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Sui Jingfeng <sui.jingfeng@linux.dev>
Subject: [PATCH 0/2] drm/etnaviv: Implement drm_gem_object_funcs::print_info()
Date: Mon, 26 Aug 2024 05:19:27 +0800 [thread overview]
Message-ID: <20240825211929.614631-1-sui.jingfeng@linux.dev> (raw)
It will be called by drm_gem_print_info() if have implemented, and this can
provide more information about the framebuffer objects. In order to make
the newly implemented etnaviv_gem_object_funcs::print_info() get in use,
we make the drm_gem_print_info() exported, then we re-implement the
etnaviv_gem_describe() base on it.
Sample Testing Information:
[root@fedora 0]# ls
clients DPI-1 encoder-1 gem_names mm ring
crtc-0 DPI-2 framebuffer gpu mmu state
crtc-1 encoder-0 gem internal_clients name
[root@fedora 0]# cat framebuffer
framebuffer[49]:
allocated by = Xorg
refcount=1
format=AR24 little-endian (0x34325241)
modifier=0x0
size=32x32
layers:
size[0]=32x32
pitch[0]=128
offset[0]=0
obj[0]:
name=0
refcount=3
start=00040096
size=16384
imported=no
caching mode=write-combine
active=no
vaddr=0000000000000000
framebuffer[47]:
allocated by = Xorg
refcount=2
format=XR24 little-endian (0x34325258)
modifier=0x0
size=1024x600
layers:
size[0]=1024x600
pitch[0]=4096
offset[0]=0
obj[0]:
name=0
refcount=3
start=00040000
size=2457600
imported=no
caching mode=write-combine
active=no
vaddr=0000000000000000
[root@fedora 0]# cat gem
obj[0]:
name=0
refcount=3
start=00040000
size=2457600
imported=no
caching mode=write-combine
active=no
vaddr=0000000000000000
obj[1]:
name=0
refcount=3
start=00040096
size=16384
imported=no
caching mode=write-combine
active=no
vaddr=0000000000000000
obj[2]:
name=0
refcount=2
start=00040097
size=16384
imported=no
caching mode=write-combine
active=no
vaddr=0000000000000000
Total 3 objects, 2490368 bytes
Sui Jingfeng (2):
drm/etnaviv: Implement drm_gem_object_funcs::print_info()
drm/etnaviv: Export drm_gem_print_info() and use it
drivers/gpu/drm/drm_gem.c | 1 +
drivers/gpu/drm/etnaviv/etnaviv_gem.c | 43 ++++++++++++++++++++++-----
drivers/gpu/drm/etnaviv/etnaviv_gem.h | 2 +-
include/drm/drm_gem.h | 2 ++
4 files changed, 40 insertions(+), 8 deletions(-)
--
2.34.1
next reply other threads:[~2024-08-25 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 21:19 Sui Jingfeng [this message]
2024-08-25 21:19 ` [PATCH 1/2] drm/etnaviv: Implement drm_gem_object_funcs::print_info() Sui Jingfeng
2024-08-25 21:19 ` [PATCH 2/2] drm/etnaviv: Export drm_gem_print_info() and use it Sui Jingfeng
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=20240825211929.614631-1-sui.jingfeng@linux.dev \
--to=sui.jingfeng@linux.dev \
--cc=airlied@gmail.com \
--cc=christian.gmeiner@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=l.stach@pengutronix.de \
--cc=linux+etnaviv@armlinux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/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