From: Yann Dirson <ydirson@free.fr>
To: Rodrigo Siqueira Jordao <rjordrigo@amd.com>
Cc: "Harry Wentland" <Harry.Wentland@amd.com>,
"Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
"Mark Yacoub" <markyacoub@chromium.org>,
"Michel Dänzer" <michel@daenzer.net>,
"Bas Nieuwenhuizen" <bas@basnieuwenhuizen.nl>,
"Roman Li" <roman.li@amd.com>,
"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
"Roman Gilg" <subdiff@gmail.com>,
"Marek Olšák" <marek.olsak@amd.com>,
"Pekka Paalanen" <ppaalanen@gmail.com>,
"Aurabindo Pillai" <aurabindo.pillai@amd.com>,
"nicholas choi" <nicholas.choi@amd.com>,
"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
"Simon Ser" <contact@emersion.fr>,
"Alex Deucher" <alexdeucher@gmail.com>,
"Sean Paul" <seanpaul@chromium.org>,
"Qingqing Zhuo" <qingqing.zhuo@amd.com>,
"Bhawanpreet Lakha" <bhawanpreet.lakha@amd.com>,
"Nicholas Kazlauskas" <nicholas.kazlauskas@amd.com>,
"Rodrigo Siqueira" <Rodrigo.Siqueira@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>
Subject: Re: [PATCH 6/6] Documentation/gpu: Add DC glossary
Date: Tue, 30 Nov 2021 20:55:58 +0100 (CET) [thread overview]
Message-ID: <1893256771.1756365.1638302158271.JavaMail.root@zimbra39-e7> (raw)
In-Reply-To: <3bfcb46a-6d7c-fb11-4b78-d068a620baa3@amd.com>
----- Mail original -----
> De: "Rodrigo Siqueira Jordao" <rjordrigo@amd.com>
> À: ydirson@free.fr, "Rodrigo Siqueira" <Rodrigo.Siqueira@amd.com>, "Christian König" <christian.koenig@amd.com>,
> "Alex Deucher" <alexander.deucher@amd.com>
> Cc: "Harry Wentland" <Harry.Wentland@amd.com>, "Linux Doc Mailing List" <linux-doc@vger.kernel.org>, "Mark Yacoub"
> <markyacoub@chromium.org>, "Michel Dänzer" <michel@daenzer.net>, "Bas Nieuwenhuizen" <bas@basnieuwenhuizen.nl>,
> "Roman Li" <roman.li@amd.com>, "amd-gfx list" <amd-gfx@lists.freedesktop.org>, "Roman Gilg" <subdiff@gmail.com>,
> "Marek Olšák" <marek.olsak@amd.com>, "Pekka Paalanen" <ppaalanen@gmail.com>, "Aurabindo Pillai"
> <aurabindo.pillai@amd.com>, "nicholas choi" <nicholas.choi@amd.com>, "Maling list - DRI developers"
> <dri-devel@lists.freedesktop.org>, "Simon Ser" <contact@emersion.fr>, "Alex Deucher" <alexdeucher@gmail.com>, "Sean
> Paul" <seanpaul@chromium.org>, "Qingqing Zhuo" <qingqing.zhuo@amd.com>, "Bhawanpreet Lakha"
> <bhawanpreet.lakha@amd.com>, "Nicholas Kazlauskas" <nicholas.kazlauskas@amd.com>
> Envoyé: Mardi 30 Novembre 2021 16:53:55
> Objet: Re: [PATCH 6/6] Documentation/gpu: Add DC glossary
>
>
>
> On 2021-11-29 3:48 p.m., ydirson@free.fr wrote:
> > Hi Rodrigo,
> >
> > That will really be helpful!
> >
> > I know drawing the line is a difficult problem (and can even make
> > things
> > harder when searching), but maybe it would make sense to keep
> > generic
> > acronyms not specific to amdgpu in a separate list. I bet a number
> > of
> > them would be useful in the scope of other drm drivers (e.g. CRTC,
> > DCC,
> > MST), and some are not restricted to the drm subsystem at all (e.g.
> > FEC,
> > LUT), but still have value as not necessarily easy to look up.
> >
> > Maybe "DC glossary" should just be "Glossary", since quite some
> > entries
> > help to read adm/amdgpu/ too. Which brings me to the result of my
> > recent
> > searches as suggested entries:
> >
> > KIQ (Kernel Interface Queue), MQD (memory queue descriptor), HQD
> > (hardware
> > queue descriptor), EOP (still no clue :)
> >
> > Maybe some more specific ones just to be spelled out in clear where
> > they
> > are used ? KCQ (compute queue?), KGQ (gfx queue?)
> >
> > More suggestions inlined.
> >
> > Best regards,
> >
>
> Hi all,
>
> I'll address all the highlighted problems in the V2. Thanks a lot for
> all the feedback.
>
> Yann,
> For the generic acronyms, how about keeping it in this patch for now?
> After it gets merged, I can prepare a new documentation patch that
> creates a glossary for DRM where I move the generic acronyms to the
> DRM
> documentation. I prefer this approach to keep the improvement small
> and
> manageable.
Sure, especially as the Right Solution(tm) is not necessarily obvious :)
One thing I thought about is that a context could be specified together
with terms. Like "BPP (graphics)", "FEC (CS)", "DMCUB (amdgpu)". Well,
"CS" may not be a good choice but you get the idea: that would keep all
terms together and keep it easy for the reader.
That way it could be easily be generalized at some point by just moving
it to a generic kernel level - provided the solution suits the doc
community at large.
Best regards,
--
Yann
prev parent reply other threads:[~2021-11-30 19:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 15:38 [PATCH 0/6] Expand display core documentation Rodrigo Siqueira
2021-11-25 15:38 ` [PATCH 1/6] Documentation/gpu: Reorganize DC documentation Rodrigo Siqueira
2021-11-26 10:35 ` Christian König
2021-11-26 15:40 ` Daniel Vetter
2021-11-26 15:42 ` Daniel Vetter
2021-11-29 12:06 ` Jani Nikula
2021-11-30 15:46 ` Rodrigo Siqueira Jordao
2021-11-30 15:48 ` Harry Wentland
2021-11-30 15:59 ` Rodrigo Siqueira Jordao
2021-11-30 16:03 ` Harry Wentland
2021-11-30 20:38 ` Yann Dirson
2021-11-25 15:38 ` [PATCH 2/6] Documentation/gpu: Document amdgpu_dm_visual_confirm debugfs entry Rodrigo Siqueira
2021-11-25 15:38 ` [PATCH 3/6] Documentation/gpu: Document pipe split visual confirmation Rodrigo Siqueira
2021-11-25 15:38 ` [PATCH 4/6] Documentation/gpu: How to collect DTN log Rodrigo Siqueira
2021-11-25 15:38 ` [PATCH 6/6] Documentation/gpu: Add DC glossary Rodrigo Siqueira
2021-11-29 20:08 ` Alex Deucher
2021-11-29 20:48 ` ydirson
2021-11-30 10:09 ` Christian König
2021-11-30 14:39 ` Alex Deucher
2021-11-30 15:53 ` Rodrigo Siqueira Jordao
2021-11-30 19:55 ` Yann Dirson [this message]
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=1893256771.1756365.1638302158271.JavaMail.root@zimbra39-e7 \
--to=ydirson@free.fr \
--cc=Harry.Wentland@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=aurabindo.pillai@amd.com \
--cc=bas@basnieuwenhuizen.nl \
--cc=bhawanpreet.lakha@amd.com \
--cc=christian.koenig@amd.com \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=marek.olsak@amd.com \
--cc=markyacoub@chromium.org \
--cc=michel@daenzer.net \
--cc=nicholas.choi@amd.com \
--cc=nicholas.kazlauskas@amd.com \
--cc=ppaalanen@gmail.com \
--cc=qingqing.zhuo@amd.com \
--cc=rjordrigo@amd.com \
--cc=roman.li@amd.com \
--cc=seanpaul@chromium.org \
--cc=subdiff@gmail.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;
as well as URLs for NNTP newsgroup(s).