Hello,
This series is based on Thierry's for-next.
It starts with some cleanups that were all sent out separately already:
- "pwm: Reduce number of pointer dereferences in pwm_device_request()"
https://lore.kernel.org/linux-pwm/20231130072105.966848-1-u.kleine-koe...@pengutronix.de
-
Hi Karolina,
On Wed, Dec 06, 2023 at 12:28:14PM +0100, Karolina Stolarek wrote:
> On 5.12.2023 16:39, Andi Shyti wrote:
...
> > Hi Karolina and Christian,
...
> > > Karolina Stolarek (8): drm/ttm/tests: Add tests for ttm_resource and
> > > ttm_sys_man drm/ttm/tests: Add tests for ttm_tt
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 26.10.23 19:33, Alexey Klimov wrote:
> #regzbot introduced: 1cfb4d612127
> #regzbot title: rx7600 stopped working after "1cfb4d612127 drm/amdgpu: put
> MQDs in VRAM"
>
>
Hi Andi,
On 5.12.2023 16:39, Andi Shyti wrote:
Hi Karolina and Christian,
Karolina Stolarek (8): drm/ttm/tests: Add tests for ttm_resource
and ttm_sys_man drm/ttm/tests: Add tests for ttm_tt drm/ttm/tests:
Add tests for ttm_bo functions drm/ttm/tests: Fix argument in
ttm_tt_kunit_init()
Hi Sascha:
On 12/6/23 19:20, Sascha Hauer wrote:
On Wed, Dec 06, 2023 at 06:20:58PM +0800, Andy Yan wrote:
Hi Sascha:
+ unsigned int n = vop2->data->regs_dump_size;
'n' is used only once, it might be clearer just to use the value where
needed and drop the extra variable.
Okay, will
On Tue, Dec 05, 2023 at 02:56:38PM -0800, Randy Dunlap wrote:
> Fix kernel-doc warnings found when using "W=1".
>
> ili922x.c:85: warning: This comment starts with '/**', but isn't a kernel-doc
> comment. Refer Documentation/doc-guide/kernel-doc.rst
> ili922x.c:85: warning: missing initial short
From: Fabio Estevam
i.MX23 has two LCDIF interrupts instead of a single one like other
i.MX devices.
Take this into account for properly describing the i.MX23 LCDIF
interrupts.
This fixes the following dt-schema warning:
imx23-olinuxino.dtb: lcdif@8003: interrupts: [[46], [45]] is too
On Wed, Dec 06, 2023 at 06:20:58PM +0800, Andy Yan wrote:
> Hi Sascha:
>
> > > + unsigned int n = vop2->data->regs_dump_size;
> >
> > 'n' is used only once, it might be clearer just to use the value where
> > needed and drop the extra variable.
>
> Okay, will do.
> >
> > > + unsigned int i;
>
On 05.12.23 06:35, Vivek Kasireddy wrote:
For drivers that would like to longterm-pin the pages associated
with a memfd, the pin_user_pages_fd() API provides an option to
not only pin the pages via FOLL_PIN but also to check and migrate
them if they reside in movable zone or CMA block. This API
From: Vasiliy Kovalev
This reverts commit 5a46dc8e4a064769e916d87bf9bccae75afc7289.
Commit 50b6f2c8297793f7f3315623db78dcff85158e96 upstream.
Commit 5a46dc8e4a0647 ("drm/edid: Fix csync detailed mode parsing") fixed
EDID detailed mode sync parsing. Unfortunately, there are quite a few
displays
From: Vasiliy Kovalev
This reverts commit 5a46dc8e4a064769e916d87bf9bccae75afc7289.
Commit 50b6f2c8297793f7f3315623db78dcff85158e96 upstream.
Commit 5a46dc8e4a0647 ("drm/edid: Fix csync detailed mode parsing") fixed
EDID detailed mode sync parsing. Unfortunately, there are quite a few
displays
From: Vasiliy Kovalev
This reverts commit 5a46dc8e4a064769e916d87bf9bccae75afc7289.
Commit 50b6f2c8297793f7f3315623db78dcff85158e96 upstream.
Commit 5a46dc8e4a0647 ("drm/edid: Fix csync detailed mode parsing") fixed
EDID detailed mode sync parsing. Unfortunately, there are quite a few
displays
All of the current encoder init / allocation functions behave slightly
differently when it comes to argument sanitizing:
- drm_connector_init() and drm_connector_init_with_ddc() implicitly
panic if the drm_device pointer, or the drm_connector pointer are
NULL, and will call WARN_ON and
All of the current CRTC init / allocation functions behave slightly
differently when it comes to argument sanitizing:
- drm_crtc_init_with_planes() implicitly panics if the drm_device
pointer, the drm_crtc pointer, or the drm_crtc_funcs pointer are
NULL, and calls WARN_ON if there's no
All of the current encoder init / allocation functions behave slightly
differently when it comes to argument sanitizing:
- drm_encoder_init() implicitly panics if the drm_device pointer, or
the drm_encoder pointer are NULL, and calls WARN_ON if there's no
destroy implementation but goes on
All of the current plane init / allocation functions behave slightly
differently when it comes to argument sanitizing:
- drm_universal_plane_init() implicitly panics if the drm_device
pointer or the drm_plane_funcs pointer are NULL, and calls WARN_ON if
there's no destroy implementation
On 05/12/2023 18:49, Fabio Estevam wrote:
> From: Fabio Estevam
>
> i.MX23 has two i.MX23 interrupts instead of a single one like other
> i.MX devices.
>
> Take this into account for properly describing the i.MX23 LCDIF
> interrupts.
>
> This fixes the following dt-schema warning:
>
>
On 05/12/2023 19:47, Fabio Estevam wrote:
> From: Fabio Estevam
>
> i.MX23 has two LCDIF interrupts instead of a single one like other
> i.MX devices.
>
> Take this into account for properly describing the i.MX23 LCDIF
> interrupts.
>
> This fixes the following dt-schema warning:
>
>
Hi Rob,
Thanks for reviewing this!
On Tue, Dec 05, 2023 at 02:48:27PM -0600, Rob Herring wrote:
> On Mon, Dec 04, 2023 at 06:33:06PM +0100, Boris Brezillon wrote:
> > From: Liviu Dudau
> >
> > Arm has introduced a new v10 GPU architecture that replaces the Job Manager
> > interface with a new
Hi,
On 2023/12/6 17:45, Thomas Zimmermann wrote:
Hi
Am 04.12.23 um 20:53 schrieb Sui Jingfeng:
Hi,
On 2023/12/4 17:27, Thomas Zimmermann wrote:
Get the global screen_info's address once and access the data via
this pointer. Limits the use of global state.
Signed-off-by: Thomas Zimmermann
Hi John,
On 12/5/2023 8:50 PM, John Harrison wrote:
On 12/5/2023 02:39, Nirmoy Das wrote:
Hi John,
On 12/5/2023 10:10 AM, John Harrison wrote:
On 12/5/2023 00:52, Nirmoy Das wrote:
gen8_engine_reset_prepare() can fail when HW fails to set
RESET_CTL_READY_TO_RESET bit. In some cases this is
Hi Sascha:
On 12/5/23 17:15, Sascha Hauer wrote:
On Thu, Nov 30, 2023 at 08:24:49PM +0800, Andy Yan wrote:
From: Andy Yan
/sys/kernel/debug/dri/vop2/summary: dump vop display state
/sys/kernel/debug/dri/vop2/regs: dump whole vop registers
/sys/kernel/debug/dri/vop2/active_regs: only dump
As the renamed drm_atomic_helper_check_wb_connector_state() now accepts
drm_writeback_connector as the first argument (instead of drm_encoder),
move the VKMS writeback atomic_check from drm_encoder_helper_funcs to
drm_connector_helper_funcs. Also drop the vkms_wb_encoder_helper_funcs,
which have
The function drm_atomic_helper_check_wb_encoder_state() doesn't use
drm_encoder for anything sensible. Internally it checks
drm_writeback_connector's state. Thus it makes sense to let this
function accept drm_connector object and the drm_atomic_state
and rename it to
The drm_atomic_helper_check_wb_encoder_state() function doesn't use
encoder for anything other than getting the drm_device instance. The
function's description talks about checking the writeback connector
state, not the encoder state. Moreover, there is no such thing as an
encoder state, encoders
Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
for once, to make this easily accessible to everyone.
Gerd, it seems this regression[1] fell through the cracks. Could you
please take a look? Or is there a good reason why this can't be
addressed? Or was it dealt with and I
Hi, Stefan
Thanks for your comment and review
On 2023/11/24 22:54, Stefan Wahren wrote:
> Hi Shengyang,
>
> [fix address of Emma]
>
> Am 24.11.23 um 11:44 schrieb Shengyang Chen:
>> This patchset adds waveshare 7inch touchscreen panel support
>> for the StarFive JH7110 SoC.
>>
>> Patch 1 add
Hi, Conor
On 2023/11/24 20:31, Conor Dooley wrote:
> On Fri, Nov 24, 2023 at 06:44:50PM +0800, Shengyang Chen wrote:
>> The waveshare 7inch touchscreen panel is a kind of raspberrypi pi
>> panel
>
> Can you be more specific about what "is a kind of rpi panel" means?
> Are they using identical
Hi
Am 04.12.23 um 20:53 schrieb Sui Jingfeng:
Hi,
On 2023/12/4 17:27, Thomas Zimmermann wrote:
Get the global screen_info's address once and access the data via
this pointer. Limits the use of global state.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Javier Martinez Canillas
On Sat, 02 Dec 2023 00:18:32 +0300, Dmitry Baryshkov wrote:
> In a lots of places in DPU driver memory is allocated by using the
> kzalloc and then manually freed using kfree. However thes memory chunks
> have a well-defined life cycle. They are either a part of the driver's
> runtime and can be
On Sun, 03 Dec 2023 03:24:37 +0300, Dmitry Baryshkov wrote:
> On sc7280 there are two clk bits for WB2: vbif_cli and clk_ctrl. While
> programming the VBIF params of WB, the driver should be toggling the
> former bit, while the sc7180_mdp, sc7280_mdp and sm8250_mdp structs
> list the latter one.
From: Fabio Estevam
When using audio from ADV7533 or ADV7535 and describing the audio
card via simple-audio-card, the '#sound-dai-cells' needs to be passed.
Document the '#sound-dai-cells' property to fix the following
dt-schema warning:
imx8mn-beacon-kit.dtb: hdmi@3d: '#sound-dai-cells' does
Hi
Am 06.12.23 um 10:09 schrieb Dmitry Baryshkov:
On Wed, 6 Dec 2023 at 10:22, Thomas Zimmermann wrote:
Hi
Am 06.12.23 um 08:27 schrieb Dinghao Liu:
__drm_universal_plane_init() frees plane->format_types and
plane->modifiers on failure. However, sometimes its callers
will free these two
Merged into drm-misc-next, except for patch 1. It's fairly independent
from the other patches and I'll resend it directly to the the PPC list.
Best regards
Thomas
Am 22.11.23 um 13:09 schrieb Thomas Zimmermann:
The old drivers for user-space mode setting have been removed in Linux
v6.3. No
On Wed, 6 Dec 2023 at 00:06, Rob Clark wrote:
>
> From: Rob Clark
>
> Introduce a6xx_info where we can stash gen specific stuff without
> polluting the toplevel adreno_info struct.
>
> Signed-off-by: Rob Clark
> ---
> drivers/gpu/drm/msm/adreno/a6xx_catalog.c | 55 +--
>
On Wed, 6 Dec 2023 at 00:06, Rob Clark wrote:
>
> From: Rob Clark
>
> Move the hwcg tables into the hw catalog.
>
> Signed-off-by: Rob Clark
> ---
> drivers/gpu/drm/msm/adreno/a6xx_catalog.c | 560 ++
> drivers/gpu/drm/msm/adreno/a6xx_gpu.c | 558 -
>
On Wed, 6 Dec 2023 at 00:06, Rob Clark wrote:
>
> From: Rob Clark
>
> Split each gen's gpu table into it's own file. Only code-motion, no
> functional change.
>
> Signed-off-by: Rob Clark
> ---
> drivers/gpu/drm/msm/Makefile | 5 +
> drivers/gpu/drm/msm/adreno/a2xx_catalog.c
On Wed, 6 Dec 2023 at 00:05, Rob Clark wrote:
>
> From: Rob Clark
>
> Split into a separate table per generation, in preparation to move each
> gen's device table to it's own file.
>
> Signed-off-by: Rob Clark
Reviewed-by: Dmitry Baryshkov
> ---
> drivers/gpu/drm/msm/adreno/adreno_device.c
On Wed, 6 Dec 2023 at 10:22, Thomas Zimmermann wrote:
>
> Hi
>
> Am 06.12.23 um 08:27 schrieb Dinghao Liu:
> > __drm_universal_plane_init() frees plane->format_types and
> > plane->modifiers on failure. However, sometimes its callers
> > will free these two pointers again, which may lead to a
> >
Am 05.12.23 um 18:14 schrieb Rob Clark:
On Tue, Dec 5, 2023 at 8:56 AM Rob Clark wrote:
On Tue, Dec 5, 2023 at 7:58 AM Christian König wrote:
Am 05.12.23 um 16:41 schrieb Rob Clark:
On Mon, Dec 4, 2023 at 10:46 PM Christian König
wrote:
Am 04.12.23 um 22:54 schrieb Rob Clark:
On Thu,
On Mon, Dec 04, 2023 at 08:33:14PM +0800, Keith Zhao wrote:
> add hdmi driver as encoder and connect
>
> Signed-off-by: Keith Zhao
> ---
> drivers/gpu/drm/verisilicon/Kconfig | 8 +
> drivers/gpu/drm/verisilicon/Makefile| 1 +
> drivers/gpu/drm/verisilicon/starfive_hdmi.c |
On 06/12/2023 02:28, Fabio Estevam wrote:
> From: Fabio Estevam
>
> When using audio from ADV7533 or ADV7535 and describing the audio
> card via simple-audio-card, the '#sound-dai-cells' needs to be passed.
>
> Document the '#sound-dai-cells' property to fix the following
> dt-schema warning:
>
On Mon, Dec 04, 2023 at 08:33:13PM +0800, Keith Zhao wrote:
> +static const struct vs_plane_info dc_hw_planes_rev0[PLANE_NUM] = {
> + {
> + .name = "Primary",
> + .id = PRIMARY_PLANE_0,
> + .type =
On 2023/11/25 0:04, Dave Stevenson wrote:
> On Fri, 24 Nov 2023 at 15:00, Stefan Wahren wrote:
>>
>> Hi Shengyang,
>>
>> [fix address of Emma]
>
> Not merged to master yet, but Emma has stepped back from maintenance.
> https://lists.freedesktop.org/archives/dri-devel/2023-October/428829.html
Hi
Am 04.12.23 um 20:53 schrieb Sui Jingfeng:
Hi,
On 2023/12/4 17:27, Thomas Zimmermann wrote:
Get the global screen_info's address once and access the data via
this pointer. Limits the use of global state.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Javier Martinez Canillas
On 06/12/2023 09:15, Yunfei Dong wrote:
> The capture buffer has two planes for format MM21, but user space only
> allocate secure memory for plane[0], and the size is Y data + uv data.
> The driver need to support one plane decoder for svp mode.
For a future v4: note the typo in the Subject
-173019
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20231204092812.2612-2-tzimmermann%40suse.de
patch subject: [PATCH v2 1/4] fbdev/efifb: Replace references to global
screen_info by local pointer
config: x86_64-randconfig-006-20231206
On Tue, Dec 05, 2023 at 04:40:40PM +0100, Danilo Krummrich wrote:
> On Tue, Dec 05, 2023 at 04:35:00PM +0100, Maxime Ripard wrote:
> > Hi,
> >
> > On Wed, Nov 29, 2023 at 11:07:59PM +0100, Danilo Krummrich wrote:
> > > Some major GPUVM changes landed just before v8 of the PowerVR series.
> > >
Hi
Am 06.12.23 um 08:27 schrieb Dinghao Liu:
__drm_universal_plane_init() frees plane->format_types and
plane->modifiers on failure. However, sometimes its callers
will free these two pointers again, which may lead to a
double-free. One possible call chain is:
mdp5_plane_init
|->
Initialize tee private data to support secure decoder.
Release tee related information for each instance when decoder
done.
Signed-off-by: Yunfei Dong
---
.../platform/mediatek/vcodec/decoder/mtk_vcodec_dec_drv.c | 8
1 file changed, 8 insertions(+)
diff --git
Setting msg and vsi information to shared buffer, then call tee invoke
function to send it to optee-os.
Signed-off-by: Yunfei Dong
---
.../vcodec/decoder/mtk_vcodec_dec_optee.c | 140 ++
.../vcodec/decoder/mtk_vcodec_dec_optee.h | 51 +++
2 files changed, 191
Waiting interrupt in optee-os for svp mode, need to disable it in kernel
in case of interrupt is cleaned.
Signed-off-by: Yunfei Dong
---
.../vcodec/decoder/mtk_vcodec_dec_hw.c| 34 +--
.../vcodec/decoder/mtk_vcodec_dec_pm.c| 6 +-
Getting secure video playback (svp) flag when request output buffer, then
calling init interface to init svp parameters in optee-os.
Signed-off-by: Yunfei Dong
---
.../mediatek/vcodec/decoder/mtk_vcodec_dec.c | 144 --
1 file changed, 94 insertions(+), 50 deletions(-)
diff
Adding capture formats to support V4L2_PIX_FMT_MS21. This format has
one plane and only be used for secure video playback at current period.
Signed-off-by: Yunfei Dong
---
.../platform/mediatek/vcodec/decoder/mtk_vcodec_dec.c| 4 +++-
.../mediatek/vcodec/decoder/mtk_vcodec_dec_stateless.c
The hardware can parse syntax to get nal_info, needn't to use cpu.
Signed-off-by: Yunfei Dong
---
.../vcodec/decoder/vdec/vdec_h264_req_multi_if.c| 13 ++---
1 file changed, 2 insertions(+), 11 deletions(-)
diff --git
Need to call dma heap interface to allocate/free secure memory when playing
secure video.
Signed-off-by: Yunfei Dong
---
.../media/platform/mediatek/vcodec/Kconfig| 1 +
.../mediatek/vcodec/common/mtk_vcodec_util.c | 122 +-
.../mediatek/vcodec/common/mtk_vcodec_util.h |
Need secure buffer size to convert secure handle to secure
pa in optee-os, re-construct the vsi struct to store each
secure buffer size.
Separate svp and normal wait interrupt condition for svp mode
waiting hardware interrupt in optee-os.
Signed-off-by: Yunfei Dong
---
The capture buffer has two planes for format MM21, but user space only
allocate secure memory for plane[0], and the size is Y data + uv data.
The driver need to support one plane decoder for svp mode.
Signed-off-by: Yunfei Dong
---
.../mediatek/vcodec/decoder/mtk_vcodec_dec.c | 7 -
From: "T.J. Mercier"
The docs for dma_heap_get_name were incorrect, and since they were
duplicated in the header they were wrong there too.
The docs formatting was inconsistent so I tried to make it more
consistent across functions since I'm already in here doing cleanup.
Remove multiple
The vsi buffer is allocated by tee share memory for svp mode, need to
use the share memory as the vsi address to store vsi data.
Signed-off-by: Yunfei Dong
---
.../vcodec/decoder/vdec/vdec_h264_req_multi_if.c | 9 +++--
.../media/platform/mediatek/vcodec/decoder/vdec_vpu_if.c | 8
Need to initialize msg and vsi information before sending to optee-os, then
calling optee invoke command to send the information to optee-os.
For the optee communication interface is different with scp, using
flag to separate them.
Signed-off-by: Yunfei Dong
---
Define one uncompressed capture format V4L2_PIX_FMT_MS21 in order to
support one plane memory. The buffer size is luma + chroma, luma is
stored at the start and chrome is stored at the end.
Signed-off-by: Yunfei Dong
---
Documentation/userspace-api/media/v4l/pixfmt-reserved.rst | 8
Open tee context to initialize the environment in order to communication
with optee-os, then open tee session as the communication pipeline for
lat and core to send data for hardware decode.
Signed-off-by: Yunfei Dong
---
.../platform/mediatek/vcodec/decoder/Makefile | 1 +
Allocate two share memory for each lat and core hardware used to share
information with optee-os. Msg buffer used to send ipi command and get ack
command with optee-os, data buffer used to store vsi information which
used for hardware decode.
Signed-off-by: Yunfei Dong
---
From: John Stultz
Add proper refcounting on the dma_heap structure.
While existing heaps are built-in, we may eventually
have heaps loaded from modules, and we'll need to be
able to properly handle the references to the heaps
Signed-off-by: John Stultz
Signed-off-by: T.J. Mercier
From: John Stultz
This allows drivers who don't want to create their own
DMA-BUF exporter to be able to allocate DMA-BUFs directly
from existing DMA-BUF Heaps.
There is some concern that the premise of DMA-BUF heaps is
that userland knows better about what type of heap memory
is needed for a
From: Jeffrey Kardatzke
Verfies in the dmabuf implementations that if the secure memory flag is
set for a queue that the dmabuf submitted to the queue is unmappable.
Signed-off-by: Jeffrey Kardatzke
Signed-off-by: Yunfei Dong
---
drivers/media/common/videobuf2/videobuf2-dma-contig.c | 6
From: Jeffrey Kardatzke
Adds documentation for V4L2_MEMORY_FLAG_SECURE.
Signed-off-by: Jeffrey Kardatzke
Signed-off-by: Yunfei Dong
---
Documentation/userspace-api/media/v4l/buffer.rst | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git
From: Jeffrey Kardatzke
Validates the secure memory flags when setting up a queue and ensures
the queue has the proper capability.
Signed-off-by: Jeffrey Kardatzke
Signed-off-by: Yunfei Dong
---
.../media/common/videobuf2/videobuf2-core.c | 23 +
From: Jeffrey Kardatzke
Adds a V4L2 flag which indicates that a queue is using secure dmabufs
and the corresponding capability flag.
Signed-off-by: Jeffrey Kardatzke
Signed-off-by: Yunfei Dong
---
include/media/videobuf2-core.h | 8 +++-
include/uapi/linux/videodev2.h | 2 ++
2 files
The patch series used to enable secure video playback (SVP) on MediaTek
hardware in the Linux kernel.
Memory Definitions:
secure memory - Memory allocated in the TEE (Trusted Execution
Environment) which is inaccessible in the REE (Rich Execution
Environment, i.e. linux kernel/userspace).
secure
On Tue, Dec 05, 2023 at 12:45:07PM -0800, Doug Anderson wrote:
> Hi,
>
> On Fri, Nov 17, 2023 at 3:00 PM Doug Anderson wrote:
> >
> > Hi,
> >
> > On Fri, Sep 22, 2023 at 2:06 PM Lyude Paul wrote:
> > >
> > > actually very glad to see this because I think I've seen one bug in the
> > > wild
> >
101 - 172 of 172 matches
Mail list logo
