From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hsia-Jun Li <randy.li@synaptics.com>
Cc: dri-devel@lists.freedesktop.org,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@linux.ie, daniel@ffwll.ch,
mchehab@kernel.org, hverkuil-cisco@xs4all.nl,
ezequiel@vanguardiasur.com.ar, sakari.ailus@linux.intel.com,
ribalda@chromium.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, tfiga@chromium.org,
sebastian.hesselbarth@gmail.com, jszhang@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] Add pixel formats used in Synatpics SoC
Date: Fri, 19 Aug 2022 02:08:35 +0300 [thread overview]
Message-ID: <Yv7Gc+mSEXBnV0Oc@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20220808162750.828001-1-randy.li@synaptics.com>
Hi Hsia-Jun,
On Tue, Aug 09, 2022 at 12:27:48AM +0800, Hsia-Jun Li wrote:
> 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 with a MTR
> module could support those tiled and compressed pixel formats. The more
> detail about MTR module could be found in the first patch of this serial
> of mail.
>
> 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 framework.
Is that so for the display side too, or only for the video decoder ?
> Please notice that, the memory planes used for video codecs would be 5
> when the compression is invoked while it would be 4 for display, the
> extra planes in the video codecs is for the decoding internally usage,
> it can't append 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. Any other reason is
> described in the v4l pixel formats's patch. I don't know whether a
> different numbers of memory planes between drm and v4l2 is acceptable.
I don't think that's a problem as such, as long as both the V4L2 and DRM
formats make sense on their own.
> I only posted the compression fourcc for the v4l2, because it is really
> hard to put the uncompression version of pixel formats under the fourcc.
> I would be better that we could have something likes format modifers in
> drm here.
Agreed, we need modifiers support in V4L2. This has been discussed
previously ([1]), and a proposal ([2]) has been submitted two years ago,
it needs to be revived.
[1] https://lore.kernel.org/linux-media/20170821155203.GB38943@e107564-lin.cambridge.arm.com/
[2] https://lore.kernel.org/linux-media/20200804192939.2251988-1-helen.koike@collabora.com/
> https://synaptics.com/products/multimedia-solutions
>
> Hsia-Jun(Randy) Li (2):
> drm/fourcc: Add Synaptics VideoSmart tiled modifiers
> [WIP]: media: Add Synaptics compressed tiled format
>
> drivers/media/v4l2-core/v4l2-common.c | 1 +
> drivers/media/v4l2-core/v4l2-ioctl.c | 2 ++
> include/uapi/drm/drm_fourcc.h | 49 +++++++++++++++++++++++++++
> include/uapi/linux/videodev2.h | 2 ++
> 4 files changed, 54 insertions(+)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2022-08-18 23:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 16:27 Hsia-Jun Li
2022-08-08 16:27 ` [PATCH 1/2] drm/fourcc: Add Synaptics VideoSmart tiled modifiers Hsia-Jun Li
2022-08-18 6:07 ` Tomasz Figa
2022-08-18 6:49 ` Hsia-Jun Li
2022-08-18 23:16 ` Laurent Pinchart
2022-08-18 23:37 ` Hsia-Jun Li
2022-08-08 16:27 ` [PATCH 2/2] [WIP]: media: Add Synaptics compressed tiled format Hsia-Jun Li
2022-08-18 6:06 ` Tomasz Figa
2022-08-18 6:33 ` Hsia-Jun Li
2022-08-18 23:13 ` Laurent Pinchart
2022-08-18 23:51 ` Hsia-Jun Li
2022-08-19 15:28 ` Nicolas Dufresne
2022-08-19 15:44 ` Hsia-Jun Li
2022-08-19 19:17 ` Nicolas Dufresne
2022-08-20 0:10 ` Hsia-Jun Li
2022-08-22 14:15 ` Nicolas Dufresne
2022-08-23 7:40 ` Hsia-Jun Li
2022-08-23 13:44 ` Nicolas Dufresne
2022-08-23 6:05 ` Tomasz Figa
2022-08-23 7:03 ` Hsia-Jun Li
2022-08-23 14:02 ` Nicolas Dufresne
2022-08-19 15:26 ` Nicolas Dufresne
2022-08-18 23:08 ` Laurent Pinchart [this message]
2022-08-18 23:28 ` [PATCH 0/2] Add pixel formats used in Synatpics SoC 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=Yv7Gc+mSEXBnV0Oc@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jszhang@kernel.org \
--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=randy.li@synaptics.com \
--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
all inboxes | Powered by JetHome®