Am 31.01.23 um 10:17 schrieb Chen, Guchun:
Hi Piccoli,
Please ignore my request of full dmesg log. I can reproduce the issue and get
the same failure callstack by returning early with an error code prior to
amdgpu_device_init_schedulers.
Regards,
Guchun
-Original Message-
From: Chen,
On Mon, 9 Jan 2023 at 18:30:25 +0530, Siddh Raman Pant wrote:
> This patchset aims to remove usages of deprecated DRM_* macros from the
> files residing in drivers/gpu/drm root.
>
> In process, I found out that NULL as first argument of drm_dbg_* wasn't
> working, but it was listed as the alternat
On Tuesday, January 31st, 2023 at 10:25, Pekka Paalanen
wrote:
> indeed, what about simply using a 1x1 framebuffer for real? Why was that
> approach rejected?
Ideally we don't want to allocate any GPU memory for the solid-fill
stuff. And if we special-case 1x1 FB creation to not be backed by re
[AMD Official Use Only - General]
Hi Christian,
I was not able to check about the handover from fbdev to gdm as I was having
issues with setting it up proper driver in the environment with display.
Regarding exporting DMA-buf, when the X starts it acquires file descriptor for
the buffer with cr
A later bad compute job can block a good gfx job
The gang submit/barrier approach makes sure that only one application at
a time can use the gfx/compute block.
So when application B makes a compute submission while a GFX submission
of application A is still running we will wait for that GFX
Hi,
thanks a lot. I've added your patches to drm-misc-next. They should be
in Linux v6.4.
Best regards
Thomas
Am 26.01.23 um 19:24 schrieb Rayyan Ansari:
Hello,
The following patches:
- Add support for configuring the width-mm and height-mm DRM mode
properties in the SimpleDRM driver via
On Wed, 25 Jan 2023 at 16:24, Matthew Auld
wrote:
>
> On Wed, 25 Jan 2023 at 16:15, Christian König
> wrote:
> >
> > Am 25.01.23 um 17:13 schrieb Matthew Auld:
> > > On Wed, 25 Jan 2023 at 15:50, Christian König
> > > wrote:
> > >> This reverts commit 00984ad39599bb2a1e6ec5d4e9c75a749f7f45c9.
>
On Fri, 6 Jan 2023 23:49:34 +0200
Dmitry Baryshkov wrote:
> On Fri, 6 Jan 2023 at 20:41, Daniel Vetter wrote:
> >
> > On Fri, Jan 06, 2023 at 05:43:23AM +0200, Dmitry Baryshkov wrote:
> > > On Fri, 6 Jan 2023 at 02:38, Jessica Zhang
> > > wrote:
> > > >
> > > >
> > > >
> > > > On 1/5/2023
Applied to drm-misc-next.
Thanks.
On 26.01.2023 17:37, Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> When CONFIG_PM is disabled, the driver fails to build:
>
> drivers/accel/ivpu/ivpu_pm.c: In function 'ivpu_rpm_get':
> drivers/accel/ivpu/ivpu_pm.c:240:84: error: 'struct dev_pm_info' has no
>
On 31.01.2023 09:53, Oded Gabbay wrote:
> On Sat, Jan 28, 2023 at 12:15 AM Arnd Bergmann wrote:
>>
>> From: Arnd Bergmann
>>
>> At the moment, accel drivers can be built-in even with CONFIG_DRM=m,
>> but this causes a link failure:
>>
>> x86_64-linux-ld: drivers/accel/ivpu/ivpu_drv.o: in function
Hi Piccoli,
Please ignore my request of full dmesg log. I can reproduce the issue and get
the same failure callstack by returning early with an error code prior to
amdgpu_device_init_schedulers.
Regards,
Guchun
-Original Message-
From: Chen, Guchun
Sent: Tuesday, January 31, 2023 2:37
On Mon, 9 Jan 2023 14:38:09 -0100
Melissa Wen wrote:
> On 01/09, Melissa Wen wrote:
> > Hi,
> >
> > After collecting comments in different places, here is a second version
> > of the work on adding DRM CRTC 3D LUT support to the current DRM color
> > mgmt interface. In comparison to previous pro
Am 26.01.23 um 19:24 schrieb Rayyan Ansari:
Parse the width-mm and height-mm devicetree properties of the panel node,
and use this to set the DRM Display Mode instead of calculating it
based on a hardcoded DPI.
Signed-off-by: Rayyan Ansari
Reviewed-by: Thomas Zimmermann
---
drivers/gpu
On Sat, Jan 28, 2023 at 12:15 AM Arnd Bergmann wrote:
>
> From: Arnd Bergmann
>
> At the moment, accel drivers can be built-in even with CONFIG_DRM=m,
> but this causes a link failure:
>
> x86_64-linux-ld: drivers/accel/ivpu/ivpu_drv.o: in function `ivpu_dev_init':
> ivpu_drv.c:(.text+0x1535): un
Il 31/01/23 02:59, xinlei@mediatek.com ha scritto:
From: Xinlei Lee
For "boe,tv105wum-nw0" this special panel, it is stipulated in
the panel spec that MIPI needs to keep the LP11 state before
the lcm_reset pin is pulled high.
Signed-off-by: Xinlei Lee
Reviewed-by: AngeloGioacchino Del R
Il 31/01/23 02:59, xinlei@mediatek.com ha scritto:
From: Xinlei Lee
Reduce the delay after LCM reset by removing an extra delay in the
initialization commands array. The required delay of at least 6ms after
reset is guaranteed by boe_panel_prepare().
Signed-off-by: Xinlei Lee
Reviewed-b
Heiko, Sandy,
Ok to apply these patches?
Sascha
On Wed, Jan 18, 2023 at 02:22:10PM +0100, Sascha Hauer wrote:
> It's been some time since I last sent this series. This version fixes
> a regression Dan Johansen reported. The reason turned out to be simple,
> I used the YUV420 register values inst
Am 31.01.23 um 04:35 schrieb Zack Rusin:
From: Zack Rusin
Rename dummy to is_iomem because that's what it is even if we're not
activelly using it. Makes the code easier to read.
Signed-off-by: Zack Rusin
Reviewed-by: Thomas Zimmermann
---
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 16
101 - 118 of 118 matches
Mail list logo
