Il 18/11/24 03:51, Jason-JH.Lin ha scritto:
mediatek-drm driver reported the capability of 180-degree rotation by
adding `DRM_MODE_ROTATE_180` to the plane property, as flip-x combined
with flip-y equals a 180-degree rotation. However, we did not handle
the rotation property in the driver and lea
Hi all,
On Mon, 18 Nov 2024 03:09:39 +0100 "Jason A. Donenfeld" wrote:
>
> This pull request contains a single series from Uros to replace uses of
> #include with prandom.h or other more specific headers, as
> needed, in order to avoid a circular header issue. Uros' goal is to be able to
> use p
Hi Marek,
On 11/15/2024, Marek Vasut wrote:
> On 11/14/24 7:57 AM, Liu Ying wrote:
> > This reverts commit ff06ea04e4cf3ba2f025024776e83bfbdfa05155.
> >
> > media_disp1_pix clock is the pixel clock of the first i.MX8MP LCDIFv3
> > display controller, while media_disp2_pix clock is the pixel clock
mtk_crtc_finish_page_flip() is used to notify the page flip that has
been completed to the userspace, so userspace can free the frame buffer
of the last frame and commit the next frame.
However, mtk_crtc_finish_page_flip() cannot guarantee the GCE has
configured all the display hardware settings o
patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Adri-n-Larumbe/drm-panthor-register-size-of-internal-objects-through-fdinfo/20241117-000321
base: git://anongit.freed
mediatek-drm driver reported the capability of 180-degree rotation by
adding `DRM_MODE_ROTATE_180` to the plane property, as flip-x combined
with flip-y equals a 180-degree rotation. However, we did not handle
the rotation property in the driver and lead to rotation issues.
Fixes: 74608d8feefd ("d
On 11/14/24 10:27 AM, Alexander Stein wrote:
Hi Marek,
Hi,
Am Samstag, 26. Oktober 2024, 06:10:42 CET schrieb Marek Vasut:
The driver configures mostly Pixel PLL from the clock cached in
local copy of the mode. Make sure the driver uses adjusted mode
which contains the updated Pixel PLL sett
On Sun, 17 Nov 2024 at 22:54, Laurent Pinchart
wrote:
>
> Hi Dmitry,
>
> Thank you for the patch.
>
> On Fri, Nov 15, 2024 at 11:09:26PM +0200, Dmitry Baryshkov wrote:
> > The mode_valid() callbacks of drm_encoder, drm_crtc and drm_bridge
> > accept const struct drm_display_mode argument. Change t
On Mon, Nov 18, 2024 at 01:22:12AM +0200, Dmitry Baryshkov wrote:
> On Sun, 17 Nov 2024 at 22:54, Laurent Pinchart wrote:
> > On Fri, Nov 15, 2024 at 11:09:26PM +0200, Dmitry Baryshkov wrote:
> > > The mode_valid() callbacks of drm_encoder, drm_crtc and drm_bridge
> > > accept const struct drm_disp
On Sun, Nov 17, 2024 at 01:26:29PM -0700, Jeffrey Hugo wrote:
> The documentation for vfree() says that passing in NULL is ok. Therefore
> we can drop the null check as redundant.
>
> Reported-by: kernel test robot
> Closes:
> https://lore.kernel.org/oe-kbuild-all/202410301732.abf5md4e-...@intel
On Mon, 18 Nov 2024 at 01:33, Laurent Pinchart
wrote:
>
> On Mon, Nov 18, 2024 at 01:22:12AM +0200, Dmitry Baryshkov wrote:
> > On Sun, 17 Nov 2024 at 22:54, Laurent Pinchart wrote:
> > > On Fri, Nov 15, 2024 at 11:09:26PM +0200, Dmitry Baryshkov wrote:
> > > > The mode_valid() callbacks of drm_en
Hi All,
I'm getting this error on v6.11 from Linus' tree. Any help would be
appreciated.
[ 5.277709] nouveau :01:00.0: sec2(gsp): mbox 000b 000f
[ 5.277712] nouveau :01:00.0: sec2(gsp):booter-load: boot failed: -5
[ 5.277728] [ cut here ]
[
Hi Dmitry,
Thank you for the patch.
On Fri, Nov 15, 2024 at 11:09:29PM +0200, Dmitry Baryshkov wrote:
> The mode_valid() callbacks of drm_encoder, drm_crtc and drm_bridge
> accept const struct drm_display_mode argument. Change the mode_valid_ctx
> callback of drm_connector to also accept const ar
On Sun, 17 Nov 2024 at 23:24, Laurent Pinchart
wrote:
>
> Hi Dmitry,
>
> Thank you for the patch.
>
> On Fri, Nov 15, 2024 at 11:09:30PM +0200, Dmitry Baryshkov wrote:
> > The mode_valid() callbacks of drm_encoder, drm_crtc and drm_bridge
> > accept const struct drm_display_mode argument. Change t
On 11/12/2024 12:47 PM, Lizhi Hou wrote:
@@ -88,6 +91,8 @@ struct amdxdna_client {
struct list_headnode;
pid_t pid;
struct mutexhwctx_lock; /* protect hwctx */
+ /* do NOT wait this srcu when hwctx_lock is
Hi Dmitry,
Thank you for the patch.
On Fri, Nov 15, 2024 at 11:09:30PM +0200, Dmitry Baryshkov wrote:
> The mode_valid() callbacks of drm_encoder, drm_crtc and drm_bridge
> accept const struct drm_display_mode argument. Change the mode_valid
> callback of drm_connector to also accept const argume
From: Christian Gmeiner
Add a new ioctl, DRM_IOCTL_V3D_PERFMON_SET_GLOBAL, to allow
configuration of a global performance monitor (perfmon).
Use the global perfmon for all jobs to ensure consistent
performance tracking across submissions. This feature is
needed to implement a Perfetto datasources
Hi Dmitry,
Thank you for the patch.
On Fri, Nov 15, 2024 at 11:09:28PM +0200, Dmitry Baryshkov wrote:
> Make hda_get_mode_idx() accept const struct drm_display_mode pointer
> instead of just raw struct drm_display_mode. This is a preparation to
> converting the mode_valid() callback of drm_conne
Hi Dmitry,
Thank you for the patch.
On Fri, Nov 15, 2024 at 11:09:27PM +0200, Dmitry Baryshkov wrote:
> Make amdgpu_dm_connector_mode_valid() duplicate the mode during the
> test rather than modifying the passed mode. This is a preparation to
> converting the mode_valid() callback of drm_connecto
Hi Dmitry,
Thank you for the patch.
On Fri, Nov 15, 2024 at 11:09:26PM +0200, Dmitry Baryshkov wrote:
> The mode_valid() callbacks of drm_encoder, drm_crtc and drm_bridge
> accept const struct drm_display_mode argument. Change the mode_valid
> callback of drm_encoder_slave to also accept const ar
The documentation for vfree() says that passing in NULL is ok. Therefore
we can drop the null check as redundant.
Reported-by: kernel test robot
Closes:
https://lore.kernel.org/oe-kbuild-all/202410301732.abf5md4e-...@intel.com/
Signed-off-by: Jeffrey Hugo
---
drivers/accel/qaic/sahara.c | 3 +-
The order of the devcoredump event flow is:
drm-scheduler -> guc-submission-execq-timed-out-job ->
guc-submission-kill-job -> xe-devcoredump (once the work
is confirmed to have been killed).
As we are aware, the GuC-FW IRQ for error-capture delivery
and extraction could have happenned before the s
The GuC-Error-Capture is currently reaching into xe_devcoredump
structure to store its own place-holder snaphot to workaround
the race between G2H-Error-Capture-Notification vs Drm-Scheduler
triggering GuC-Submission-exec-queue-timeout/kill.
Part of that race workaround design included GuC-Error-C
The arguments for __dma_buf_debugfs_list_del do not match for both the
CONFIG_DEBUG_FS case and the !CONFIG_DEBUG_FS case. The !CONFIG_DEBUG_FS
case should take a struct dma_buf *, but it's currently struct file *.
This can lead to the build error:
error: passing argument 1 of ‘__dma_buf_debugfs_l
On Mon, 30 Sep 2024 13:20:46 +0200, Julia Lawall wrote:
> Reorganize kerneldoc parameter names to match the parameter
> order in the function header.
>
> The misordered cases were identified using the following
> Coccinelle semantic patch:
>
> //
> @initialize:ocaml@
> @@
>
> [...]
Applied to
Hi Dave and Alex,
在 2024-11-17 06:17，Dave Airlie 写道：
Hi Linus,
Alex sent on a last minute revert for a regression found with swsmu
patch for final,
I saw this patch earlier from the stable list and was a little confused
as to what the regression was (what exact hardware
configurations/workl
On 10/21/24 02:08, Dmitry Osipenko wrote:
> From: Dongwon Kim
>
> Use drm_gem_plane_helper_prepare_fb() helper for explicit framebuffer
> synchronization. We need to wait for explicit fences in a case of
> Venus and native contexts when guest user space uses explicit fencing.
>
> Signed-off-by:
On 10/21/24 01:47, Dmitry Osipenko wrote:
> From: Pierre-Eric Pelloux-Prayer
>
> Xorg context creation fails for native contexts that use
> VIRTGPU_CONTEXT_INIT because context is already initialized implicitly
> when dumb buffer is created. Fix it by not creating default vrend context
> if conte
On 11/13/24 11:44, Ryosuke Yasuoka wrote:
> From: Jocelyn Falempe
>
> Virtio gpu supports the drm_panic module, which displays a message to
> the screen when a kernel panic occurs.
>
> Signed-off-by: Ryosuke Yasuoka
> Signed-off-by: Jocelyn Falempe
> ---
I'll apply this patch tomorrow with a
On 10/29/24 09:18, Kasireddy, Vivek wrote:
BTW, is any DG2 GPU suitable for testing of this patchset? Will I be
able to test it using a regular consumer A750 card?
>>> Yes, you can test with any DG2 dGPU as long as you can passthrough it to
>> the
>>> Guest VM. And, if there is an iGPU av
ig: x86_64-rhel-8.3
(https://download.01.org/0day-ci/archive/20241117/202411171611.9lezwwse-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241117/202411171611.9lezwwse-...@intel.com/reproduce)
If you fix
32 matches
Mail list logo
