From: Hsia-Jun Li <randy.li@synaptics.com>
To: dri-devel@lists.freedesktop.org
Cc: airlied@linux.ie, daniel@ffwll.ch, ezequiel@vanguardiasur.com.ar,
helen.koike@collabora.com, hverkuil-cisco@xs4all.nl,
jszhang@kernel.org, laurent.pinchart@ideasonboard.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
maarten.lankhorst@linux.intel.com, mchehab@kernel.org,
mripard@kernel.org, nicolas@ndufresne.ca, ribalda@chromium.org,
sakari.ailus@linux.intel.com, sebastian.hesselbarth@gmail.com,
tfiga@chromium.org, tzimmermann@suse.de,
"Hsia-Jun(Randy) Li" <randy.li@synaptics.com>
Subject: [PATCH v3 0/4] Add pixel formats used in Synatpics SoC
Date: Tue, 1 Nov 2022 18:04:44 +0800 [thread overview]
Message-ID: <20221101100448.66712-1-randy.li@synaptics.com> (raw)
From: "Hsia-Jun(Randy) Li" <randy.li@synaptics.com>
Those pixel formats are used in Synaptics's VideoSmart series SoCs,
likes VS640, VS680. I just disclose the pixel formats used in the video
codecs and display pipeline this time. Actually any device connected to
the MTR module could support those tiled and compressed pixel formats.
We may not be able to post any drivers here in a short time, the most of
work in this platform is done in the Trusted Execution Environment and
we didn't use the optee event its client framework.
Please notice that, the memory planes needed for video codecs could be
one more than display case. That extra planes in the video codecs is
for the decoding internal usage, it can't append to the luma or chroma
buffer as many other drivers do, because this buffer could be only
accessed by the video codecs itself, it requests a different memory
security attributes. There is not a proper place in v4l2 m2m to allocate
a large size buffer, we don't know when the users won't allocate more
graphics buffers. Although we could allocate it in a step likes
STREAMON, it would lead unusual delaying in starting of video playbacl.
https://synaptics.com/products/multimedia-solutions
Changlog
v3:
There was a mistake in format macro.
Correcting the description of 64L4 variant modifiers.
v2:
The DRM modifiers in the first draft is too simple, it can't tell
the tiles in group attribute in memory layout.
Removing the v4l2 fourcc. Adding a document for the future v4l2 extended
fmt.
v1:
first draft of DRM modifiers
Try to put basic tile formats into v4l2 fourcc
Hsia-Jun(Randy) Li (3):
drm/fourcc: Add Synaptics VideoSmart tiled modifiers
media: videodev2.h: add pixel format modifiers
media: videodev2.h: add Synaptics tiled modifiers
Randy Li (1):
media: docs: Add Synpatics tile modifiers
.../media/v4l/pixfmt-synaptics.rst | 80 +++++++++++++++++++
.../userspace-api/media/v4l/pixfmt.rst | 1 +
include/uapi/drm/drm_fourcc.h | 75 +++++++++++++++++
include/uapi/linux/videodev2.h | 50 ++++++++++++
4 files changed, 206 insertions(+)
create mode 100644 Documentation/userspace-api/media/v4l/pixfmt-synaptics.rst
--
2.17.1
next reply other threads:[~2022-11-01 10:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 10:04 Hsia-Jun Li [this message]
2022-11-01 10:04 ` [PATCH v3 1/4] drm/fourcc: Add Synaptics VideoSmart tiled modifiers Hsia-Jun Li
2022-11-01 10:04 ` [PATCH v3 2/4] media: videodev2.h: add pixel format modifiers Hsia-Jun Li
2022-11-01 17:10 ` kernel test robot
2022-11-01 19:01 ` kernel test robot
2022-11-02 1:25 ` kernel test robot
2022-11-01 10:04 ` [PATCH v3 3/4] media: videodev2.h: add Synaptics tiled modifiers Hsia-Jun Li
2022-11-01 10:04 ` [PATCH v3 4/4] media: docs: Add Synpatics tile modifiers Hsia-Jun Li
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=20221101100448.66712-1-randy.li@synaptics.com \
--to=randy.li@synaptics.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=helen.koike@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jszhang@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=ribalda@chromium.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tfiga@chromium.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