All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Jisheng Zhang <jszhang@kernel.org>
Cc: Hsia-Jun Li <randy.li@synaptics.com>,
	dri-devel@lists.freedesktop.org, airlied@linux.ie,
	daniel@ffwll.ch, ezequiel@vanguardiasur.com.ar,
	helen.koike@collabora.com, 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, ayaka@soulik.info
Subject: Re: [PATCH v4] drm/fourcc: Add Synaptics VideoSmart tiled modifiers
Date: Wed, 23 Nov 2022 17:42:22 +0100	[thread overview]
Message-ID: <Y35Nbhd/fhESOFeU@phenom.ffwll.local> (raw)
In-Reply-To: <Y341AxDwqRC/0eep@xhacker>

On Wed, Nov 23, 2022 at 10:58:11PM +0800, Jisheng Zhang wrote:
> On Wed, Nov 23, 2022 at 05:19:57PM +0800, Hsia-Jun Li wrote:
> > From: "Hsia-Jun(Randy) Li" <randy.li@synaptics.com>
> > 
> > Memory Traffic Reduction(MTR) is a module in Synaptics
> > VideoSmart platform could process lossless compression image
> > and cache the tile memory line.
> > 
> > Those modifiers only record the parameters would effort pixel
> > layout or memory layout. Whether physical memory page mapping
> > is used is not a part of format.
> > 
> > We would allocate the same size of memory for uncompressed
> > and compressed luma and chroma data, while the compressed buffer
> > would request two extra planes holding the metadata for
> > the decompression.
> > 
> > Signed-off-by: Hsia-Jun(Randy) Li <randy.li@synaptics.com>
> > ---
> >  include/uapi/drm/drm_fourcc.h | 75 +++++++++++++++++++++++++++++++++++
> >  1 file changed, 75 insertions(+)
> > 
> > diff --git a/include/uapi/drm/drm_fourcc.h b/include/uapi/drm/drm_fourcc.h
> > index bc056f2d537d..ca0b4ca70b36 100644
> > --- a/include/uapi/drm/drm_fourcc.h
> > +++ b/include/uapi/drm/drm_fourcc.h
> > @@ -407,6 +407,7 @@ extern "C" {
> >  #define DRM_FORMAT_MOD_VENDOR_ARM     0x08
> >  #define DRM_FORMAT_MOD_VENDOR_ALLWINNER 0x09
> >  #define DRM_FORMAT_MOD_VENDOR_AMLOGIC 0x0a
> > +#define DRM_FORMAT_MOD_VENDOR_SYNAPTICS 0x0b
> 
> Any users in the mainline tree?

Note that drm_fourcc.h serves as the vendor-neutral registry for these
numbers, and they're referenced in both gl and vk extensions. So this is
the one case where we do _not_ require in-kernel users or open source
userspace.

If there is someone interested in an in-kernel or open userspace driver
though it would be really great to have their acks before merging. Just to
make sure that the modifiers will work with both upstream and downstream
driver stacks.

I just realized that we've failed to document this, I'll type up a patch.
-Daniel


> 
> >  
> >  /* add more to the end as needed */
> >  
> > @@ -1507,6 +1508,80 @@ drm_fourcc_canonicalize_nvidia_format_mod(__u64 modifier)
> >  #define AMD_FMT_MOD_CLEAR(field) \
> >  	(~((__u64)AMD_FMT_MOD_##field##_MASK << AMD_FMT_MOD_##field##_SHIFT))
> >  
> > +/*
> > + * Synaptics VideoSmart modifiers
> > + *
> > + * Tiles could be arranged in Groups of Tiles (GOTs), it is a small tile
> > + * within a tile. GOT size and layout varies based on platform and
> > + * performance concern. When the compression is applied, it is possible
> > + * that we would have two tile type in the GOT, these parameters can't
> > + * tell the secondary tile type.
> > + *
> > + * Besides, an 8 size 4 bytes arrary (32 bytes) would be need to store
> > + * some compression parameters for a compression meta data plane.
> > + *
> > + *       Macro
> > + * Bits  Param Description
> > + * ----  ----- -----------------------------------------------------------------
> > + *
> > + *  7:0  f     Scan direction description.
> > + *
> > + *               0 = Invalid
> > + *               1 = V4, the scan would always start from vertical for 4 pixel
> > + *                   then move back to the start pixel of the next horizontal
> > + *                   direction.
> > + *               2 = Reserved for future use.
> > + *
> > + * 15:8  m     The times of pattern repeat in the right angle direction from
> > + *             the first scan direction.
> > + *
> > + * 19:16 p     The padding bits after the whole scan, could be zero.
> > + *
> > + * 20:20 g     GOT packing flag.
> > + *
> > + * 23:21 -     Reserved for future use.  Must be zero.
> > + *
> > + * 27:24 h     log2(horizontal) of bytes, in GOTs.
> > + *
> > + * 31:28 v     log2(vertical) of bytes, in GOTs.
> > + *
> > + * 35:32 -     Reserved for future use.  Must be zero.
> > + *
> > + * 36:36 c     Compression flag.
> > + *
> > + * 55:37 -     Reserved for future use.  Must be zero.
> > + *
> > + */
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4_TILED		fourcc_mod_code(SYNAPTICS, 1)
> > +
> > +#define DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(f, m, p, g, h, v, c) \
> > +	fourcc_mod_code(SYNAPTICS, ((__u64)((f) & 0xff) | \
> > +				 ((__u64)((m) & 0xff) << 8) | \
> > +				 ((__u64)((p) & 0xf) << 16) | \
> > +				 ((__u64)((g) & 0x1) << 20) | \
> > +				 ((__u64)((h) & 0xf) << 24) | \
> > +				 ((__u64)((v) & 0xf) << 28) | \
> > +				 ((__u64)((c) & 0x1) << 36)))
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4H1 \
> > +	DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(1, 1, 0, 0, 0, 0, 0)
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4H3P8 \
> > +	DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(1, 3, 8, 0, 0, 0, 0)
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4H1_64L4_COMPRESSED \
> > +	DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(1, 1, 0, 1, 6, 2, 1)
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4H3P8_64L4_COMPRESSED \
> > +	DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(1, 3, 8, 1, 6, 2, 1)
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4H1_128L128_COMPRESSED \
> > +	DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(1, 1, 0, 1, 7, 7, 1)
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4H3P8_128L128_COMPRESSED \
> > +	DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(1, 3, 8, 1, 7, 7, 1)
> > +
> >  #if defined(__cplusplus)
> >  }
> >  #endif
> > -- 
> > 2.17.1
> > 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: Jisheng Zhang <jszhang@kernel.org>
Cc: mchehab@kernel.org, sakari.ailus@linux.intel.com,
	airlied@linux.ie, tzimmermann@suse.de, ayaka@soulik.info,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	nicolas@ndufresne.ca, Hsia-Jun Li <randy.li@synaptics.com>,
	helen.koike@collabora.com, ezequiel@vanguardiasur.com.ar,
	ribalda@chromium.org, sebastian.hesselbarth@gmail.com,
	tfiga@chromium.org, linux-media@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH v4] drm/fourcc: Add Synaptics VideoSmart tiled modifiers
Date: Wed, 23 Nov 2022 17:42:22 +0100	[thread overview]
Message-ID: <Y35Nbhd/fhESOFeU@phenom.ffwll.local> (raw)
In-Reply-To: <Y341AxDwqRC/0eep@xhacker>

On Wed, Nov 23, 2022 at 10:58:11PM +0800, Jisheng Zhang wrote:
> On Wed, Nov 23, 2022 at 05:19:57PM +0800, Hsia-Jun Li wrote:
> > From: "Hsia-Jun(Randy) Li" <randy.li@synaptics.com>
> > 
> > Memory Traffic Reduction(MTR) is a module in Synaptics
> > VideoSmart platform could process lossless compression image
> > and cache the tile memory line.
> > 
> > Those modifiers only record the parameters would effort pixel
> > layout or memory layout. Whether physical memory page mapping
> > is used is not a part of format.
> > 
> > We would allocate the same size of memory for uncompressed
> > and compressed luma and chroma data, while the compressed buffer
> > would request two extra planes holding the metadata for
> > the decompression.
> > 
> > Signed-off-by: Hsia-Jun(Randy) Li <randy.li@synaptics.com>
> > ---
> >  include/uapi/drm/drm_fourcc.h | 75 +++++++++++++++++++++++++++++++++++
> >  1 file changed, 75 insertions(+)
> > 
> > diff --git a/include/uapi/drm/drm_fourcc.h b/include/uapi/drm/drm_fourcc.h
> > index bc056f2d537d..ca0b4ca70b36 100644
> > --- a/include/uapi/drm/drm_fourcc.h
> > +++ b/include/uapi/drm/drm_fourcc.h
> > @@ -407,6 +407,7 @@ extern "C" {
> >  #define DRM_FORMAT_MOD_VENDOR_ARM     0x08
> >  #define DRM_FORMAT_MOD_VENDOR_ALLWINNER 0x09
> >  #define DRM_FORMAT_MOD_VENDOR_AMLOGIC 0x0a
> > +#define DRM_FORMAT_MOD_VENDOR_SYNAPTICS 0x0b
> 
> Any users in the mainline tree?

Note that drm_fourcc.h serves as the vendor-neutral registry for these
numbers, and they're referenced in both gl and vk extensions. So this is
the one case where we do _not_ require in-kernel users or open source
userspace.

If there is someone interested in an in-kernel or open userspace driver
though it would be really great to have their acks before merging. Just to
make sure that the modifiers will work with both upstream and downstream
driver stacks.

I just realized that we've failed to document this, I'll type up a patch.
-Daniel


> 
> >  
> >  /* add more to the end as needed */
> >  
> > @@ -1507,6 +1508,80 @@ drm_fourcc_canonicalize_nvidia_format_mod(__u64 modifier)
> >  #define AMD_FMT_MOD_CLEAR(field) \
> >  	(~((__u64)AMD_FMT_MOD_##field##_MASK << AMD_FMT_MOD_##field##_SHIFT))
> >  
> > +/*
> > + * Synaptics VideoSmart modifiers
> > + *
> > + * Tiles could be arranged in Groups of Tiles (GOTs), it is a small tile
> > + * within a tile. GOT size and layout varies based on platform and
> > + * performance concern. When the compression is applied, it is possible
> > + * that we would have two tile type in the GOT, these parameters can't
> > + * tell the secondary tile type.
> > + *
> > + * Besides, an 8 size 4 bytes arrary (32 bytes) would be need to store
> > + * some compression parameters for a compression meta data plane.
> > + *
> > + *       Macro
> > + * Bits  Param Description
> > + * ----  ----- -----------------------------------------------------------------
> > + *
> > + *  7:0  f     Scan direction description.
> > + *
> > + *               0 = Invalid
> > + *               1 = V4, the scan would always start from vertical for 4 pixel
> > + *                   then move back to the start pixel of the next horizontal
> > + *                   direction.
> > + *               2 = Reserved for future use.
> > + *
> > + * 15:8  m     The times of pattern repeat in the right angle direction from
> > + *             the first scan direction.
> > + *
> > + * 19:16 p     The padding bits after the whole scan, could be zero.
> > + *
> > + * 20:20 g     GOT packing flag.
> > + *
> > + * 23:21 -     Reserved for future use.  Must be zero.
> > + *
> > + * 27:24 h     log2(horizontal) of bytes, in GOTs.
> > + *
> > + * 31:28 v     log2(vertical) of bytes, in GOTs.
> > + *
> > + * 35:32 -     Reserved for future use.  Must be zero.
> > + *
> > + * 36:36 c     Compression flag.
> > + *
> > + * 55:37 -     Reserved for future use.  Must be zero.
> > + *
> > + */
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4_TILED		fourcc_mod_code(SYNAPTICS, 1)
> > +
> > +#define DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(f, m, p, g, h, v, c) \
> > +	fourcc_mod_code(SYNAPTICS, ((__u64)((f) & 0xff) | \
> > +				 ((__u64)((m) & 0xff) << 8) | \
> > +				 ((__u64)((p) & 0xf) << 16) | \
> > +				 ((__u64)((g) & 0x1) << 20) | \
> > +				 ((__u64)((h) & 0xf) << 24) | \
> > +				 ((__u64)((v) & 0xf) << 28) | \
> > +				 ((__u64)((c) & 0x1) << 36)))
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4H1 \
> > +	DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(1, 1, 0, 0, 0, 0, 0)
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4H3P8 \
> > +	DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(1, 3, 8, 0, 0, 0, 0)
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4H1_64L4_COMPRESSED \
> > +	DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(1, 1, 0, 1, 6, 2, 1)
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4H3P8_64L4_COMPRESSED \
> > +	DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(1, 3, 8, 1, 6, 2, 1)
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4H1_128L128_COMPRESSED \
> > +	DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(1, 1, 0, 1, 7, 7, 1)
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4H3P8_128L128_COMPRESSED \
> > +	DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(1, 3, 8, 1, 7, 7, 1)
> > +
> >  #if defined(__cplusplus)
> >  }
> >  #endif
> > -- 
> > 2.17.1
> > 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: Jisheng Zhang <jszhang@kernel.org>
Cc: Hsia-Jun Li <randy.li@synaptics.com>,
	dri-devel@lists.freedesktop.org, airlied@linux.ie,
	daniel@ffwll.ch, ezequiel@vanguardiasur.com.ar,
	helen.koike@collabora.com, 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, ayaka@soulik.info
Subject: Re: [PATCH v4] drm/fourcc: Add Synaptics VideoSmart tiled modifiers
Date: Wed, 23 Nov 2022 17:42:22 +0100	[thread overview]
Message-ID: <Y35Nbhd/fhESOFeU@phenom.ffwll.local> (raw)
In-Reply-To: <Y341AxDwqRC/0eep@xhacker>

On Wed, Nov 23, 2022 at 10:58:11PM +0800, Jisheng Zhang wrote:
> On Wed, Nov 23, 2022 at 05:19:57PM +0800, Hsia-Jun Li wrote:
> > From: "Hsia-Jun(Randy) Li" <randy.li@synaptics.com>
> > 
> > Memory Traffic Reduction(MTR) is a module in Synaptics
> > VideoSmart platform could process lossless compression image
> > and cache the tile memory line.
> > 
> > Those modifiers only record the parameters would effort pixel
> > layout or memory layout. Whether physical memory page mapping
> > is used is not a part of format.
> > 
> > We would allocate the same size of memory for uncompressed
> > and compressed luma and chroma data, while the compressed buffer
> > would request two extra planes holding the metadata for
> > the decompression.
> > 
> > Signed-off-by: Hsia-Jun(Randy) Li <randy.li@synaptics.com>
> > ---
> >  include/uapi/drm/drm_fourcc.h | 75 +++++++++++++++++++++++++++++++++++
> >  1 file changed, 75 insertions(+)
> > 
> > diff --git a/include/uapi/drm/drm_fourcc.h b/include/uapi/drm/drm_fourcc.h
> > index bc056f2d537d..ca0b4ca70b36 100644
> > --- a/include/uapi/drm/drm_fourcc.h
> > +++ b/include/uapi/drm/drm_fourcc.h
> > @@ -407,6 +407,7 @@ extern "C" {
> >  #define DRM_FORMAT_MOD_VENDOR_ARM     0x08
> >  #define DRM_FORMAT_MOD_VENDOR_ALLWINNER 0x09
> >  #define DRM_FORMAT_MOD_VENDOR_AMLOGIC 0x0a
> > +#define DRM_FORMAT_MOD_VENDOR_SYNAPTICS 0x0b
> 
> Any users in the mainline tree?

Note that drm_fourcc.h serves as the vendor-neutral registry for these
numbers, and they're referenced in both gl and vk extensions. So this is
the one case where we do _not_ require in-kernel users or open source
userspace.

If there is someone interested in an in-kernel or open userspace driver
though it would be really great to have their acks before merging. Just to
make sure that the modifiers will work with both upstream and downstream
driver stacks.

I just realized that we've failed to document this, I'll type up a patch.
-Daniel


> 
> >  
> >  /* add more to the end as needed */
> >  
> > @@ -1507,6 +1508,80 @@ drm_fourcc_canonicalize_nvidia_format_mod(__u64 modifier)
> >  #define AMD_FMT_MOD_CLEAR(field) \
> >  	(~((__u64)AMD_FMT_MOD_##field##_MASK << AMD_FMT_MOD_##field##_SHIFT))
> >  
> > +/*
> > + * Synaptics VideoSmart modifiers
> > + *
> > + * Tiles could be arranged in Groups of Tiles (GOTs), it is a small tile
> > + * within a tile. GOT size and layout varies based on platform and
> > + * performance concern. When the compression is applied, it is possible
> > + * that we would have two tile type in the GOT, these parameters can't
> > + * tell the secondary tile type.
> > + *
> > + * Besides, an 8 size 4 bytes arrary (32 bytes) would be need to store
> > + * some compression parameters for a compression meta data plane.
> > + *
> > + *       Macro
> > + * Bits  Param Description
> > + * ----  ----- -----------------------------------------------------------------
> > + *
> > + *  7:0  f     Scan direction description.
> > + *
> > + *               0 = Invalid
> > + *               1 = V4, the scan would always start from vertical for 4 pixel
> > + *                   then move back to the start pixel of the next horizontal
> > + *                   direction.
> > + *               2 = Reserved for future use.
> > + *
> > + * 15:8  m     The times of pattern repeat in the right angle direction from
> > + *             the first scan direction.
> > + *
> > + * 19:16 p     The padding bits after the whole scan, could be zero.
> > + *
> > + * 20:20 g     GOT packing flag.
> > + *
> > + * 23:21 -     Reserved for future use.  Must be zero.
> > + *
> > + * 27:24 h     log2(horizontal) of bytes, in GOTs.
> > + *
> > + * 31:28 v     log2(vertical) of bytes, in GOTs.
> > + *
> > + * 35:32 -     Reserved for future use.  Must be zero.
> > + *
> > + * 36:36 c     Compression flag.
> > + *
> > + * 55:37 -     Reserved for future use.  Must be zero.
> > + *
> > + */
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4_TILED		fourcc_mod_code(SYNAPTICS, 1)
> > +
> > +#define DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(f, m, p, g, h, v, c) \
> > +	fourcc_mod_code(SYNAPTICS, ((__u64)((f) & 0xff) | \
> > +				 ((__u64)((m) & 0xff) << 8) | \
> > +				 ((__u64)((p) & 0xf) << 16) | \
> > +				 ((__u64)((g) & 0x1) << 20) | \
> > +				 ((__u64)((h) & 0xf) << 24) | \
> > +				 ((__u64)((v) & 0xf) << 28) | \
> > +				 ((__u64)((c) & 0x1) << 36)))
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4H1 \
> > +	DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(1, 1, 0, 0, 0, 0, 0)
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4H3P8 \
> > +	DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(1, 3, 8, 0, 0, 0, 0)
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4H1_64L4_COMPRESSED \
> > +	DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(1, 1, 0, 1, 6, 2, 1)
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4H3P8_64L4_COMPRESSED \
> > +	DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(1, 3, 8, 1, 6, 2, 1)
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4H1_128L128_COMPRESSED \
> > +	DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(1, 1, 0, 1, 7, 7, 1)
> > +
> > +#define DRM_FORMAT_MOD_SYNA_V4H3P8_128L128_COMPRESSED \
> > +	DRM_FORMAT_MOD_SYNA_MTR_LINEAR_2D(1, 3, 8, 1, 7, 7, 1)
> > +
> >  #if defined(__cplusplus)
> >  }
> >  #endif
> > -- 
> > 2.17.1
> > 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-11-23 16:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23  9:19 [PATCH v4] drm/fourcc: Add Synaptics VideoSmart tiled modifiers Hsia-Jun Li
2022-11-23  9:19 ` Hsia-Jun Li
2022-11-23  9:19 ` Hsia-Jun Li
2022-11-23 14:58 ` Jisheng Zhang
2022-11-23 14:58   ` Jisheng Zhang
2022-11-23 14:58   ` Jisheng Zhang
2022-11-23 16:42   ` Daniel Vetter [this message]
2022-11-23 16:42     ` Daniel Vetter
2022-11-23 16:42     ` Daniel Vetter
2022-11-23 17:14     ` Randy Li
2022-11-23 17:14       ` Randy Li
2022-11-23 17:14       ` Randy Li
2022-11-23 17:27       ` Daniel Vetter
2022-11-23 17:27         ` Daniel Vetter
2022-11-23 17:27         ` Daniel Vetter
2022-11-23 18:06         ` Randy Li
2022-11-24  3:28         ` Hsia-Jun Li
2022-11-24  3:28           ` Hsia-Jun Li
2022-11-24  3:28           ` 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=Y35Nbhd/fhESOFeU@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@linux.ie \
    --cc=ayaka@soulik.info \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=helen.koike@collabora.com \
    --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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.