On Tuesday, January 2, 2024 6:07:56 PM UTC Ondřej Jirman wrote:
> On Tue, Jan 02, 2024 at 05:15:47PM +0100, Manuel Traut wrote:
> > +&pcie2x1 {
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&pcie_reset_h>;
> > + reset-gpios = <&gpio1 RK_PB2 GPIO_ACTIVE_HIGH>;
> > + vpcie3v3-supply = <
Hi Vegard,
On 12/25/23 09:08, Randy Dunlap wrote:
>
>
> On 12/25/23 00:30, Vegard Nossum wrote:
>>
>> On 25/12/2023 08:40, Randy Dunlap wrote:
>>> I do see one thing that I don't like in the generated html output.
>>> It's not a problem with this patch.
>>> The #defines for DRM_NOUVEAU_VM_BIND_O
./drivers/gpu/drm/xe/xe_vm.c:187:25-27: WARNING !A || A && B is equivalent to
!A || B.
Reported-by: Abaci Robot
Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=7818
Signed-off-by: Jiapeng Chong
---
drivers/gpu/drm/xe/xe_vm.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
dif
Hi all,
On Wed, 3 Jan 2024 12:19:11 +1100 Stephen Rothwell
wrote:
>
> On Tue, 2 Jan 2024 11:12:22 +1100 Stephen Rothwell
> wrote:
> >
> > After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
> > produced this warning:
> >
> > In file included from include/drm/drm_mm.h:51
The header files test-bug.h is included twice in xe_pci.c,
so one inclusion can be removed.
./drivers/gpu/drm/xe/tests/xe_pci.c: kunit/test-bug.h is included more than
once.
Signed-off-by: Yang Li
---
drivers/gpu/drm/xe/tests/xe_pci.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/
Hi all,
On Tue, 2 Jan 2024 11:12:22 +1100 Stephen Rothwell
wrote:
>
> After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> In file included from include/drm/drm_mm.h:51,
> from drivers/gpu/drm/xe/xe_bo_types.h:11,
>
./drivers/gpu/drm/xe/xe_rtp.c:168:2-3: Unneeded semicolon
Signed-off-by: Yang Li
---
drivers/gpu/drm/xe/xe_rtp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/xe/xe_rtp.c b/drivers/gpu/drm/xe/xe_rtp.c
index fb44cc7521d8..316ed2f6d1f0 100644
--- a/drivers/gpu
On Sun, 31 Dec 2023 at 08:08, Randy Dunlap wrote:
>
> Correct all kernel-doc warnings in dpu_encoder.c and dpu_rm.c:
>
> dpu_encoder.c:212: warning: Excess struct member 'crtc_kickoff_cb'
> description in 'dpu_encoder_virt'
> dpu_encoder.c:212: warning: Excess struct member 'crtc_kickoff_cb_data'
From: John Harrison
A failure to load the HuC is occasionally observed where the cause is
believed to be a low GT frequency leading to very long load times.
So a) increase the timeout so that the user still gets a working
system even in the case of slow load. And b) report the frequency
during t
On 12/30/2023 10:08 PM, Randy Dunlap wrote:
Correct all kernel-doc warnings in dpu_encoder.c and dpu_rm.c:
dpu_encoder.c:212: warning: Excess struct member 'crtc_kickoff_cb' description
in 'dpu_encoder_virt'
dpu_encoder.c:212: warning: Excess struct member 'crtc_kickoff_cb_data'
description
On Tue, Jan 02, 2024 at 09:56:20PM +0100, Jonas Karlman wrote:
> Hi Manuel and Ondřej,
>
> On 2024-01-02 19:07, Ondřej Jirman wrote:
> > Hello Manuel,
>
> [...]
>
> >> +
> >> +&sfc {
> >> + pinctrl-names = "default";
> >> + pinctrl-0 = <&fspi_dual_io_pins>;
> >> + status = "okay";
> >> + #ad
On 01/01/2024 17:15, Dario Binacchi wrote:
> The patch adds the FRIDA FRD400B25025-A-CTK panel, which belongs to the
> Novatek NT35510-based panel family.
>
> Signed-off-by: Dario Binacchi
>
> ---
>
> Changes in v2:
> - Add a dash in front of each "items:"
>
> .../bindings/display/panel/novat
Hi Manuel and Ondřej,
On 2024-01-02 19:07, Ondřej Jirman wrote:
> Hello Manuel,
[...]
>> +
>> +&sfc {
>> +pinctrl-names = "default";
>> +pinctrl-0 = <&fspi_dual_io_pins>;
>> +status = "okay";
>> +#address-cells = <1>;
>> +#size-cells = <0>;
>> +
>> +flash@0 {
>> +
On 1/1/2024 1:00 PM, Artur Weber wrote:
It turns out that I had misconfigured the device I was using the panel
with; the bus data polarity is not high for this panel, I had to change
the config on the display controller's side.
Fix the panel config to properly reflect its accurate settings.
On 2.01.2024 20:33, Rob Clark wrote:
> From: Rob Clark
>
> We'd miss actually activating LLC.
>
> Signed-off-by: Rob Clark
> ---
> drivers/gpu/drm/msm/adreno/a6xx_gpu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/msm/adreno/a6xx_gpu.c
> b/drivers/
Hi Artur,
On Mon, Jan 01, 2024 at 10:00:16PM +0100, Artur Weber wrote:
> It turns out that I had misconfigured the device I was using the panel
> with; the bus data polarity is not high for this panel, I had to change
> the config on the display controller's side.
>
> Fix the panel config to prop
From: Rob Clark
We'd miss actually activating LLC.
Signed-off-by: Rob Clark
---
drivers/gpu/drm/msm/adreno/a6xx_gpu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/msm/adreno/a6xx_gpu.c
b/drivers/gpu/drm/msm/adreno/a6xx_gpu.c
index a5660d63535b..54dc5eb37
On Fri, 22 Dec 2023 18:41:52 +0100, Alex Bee wrote:
> The integration for this SoC is different from the currently existing: It
> needs it's PHY's reference clock rate to calculate the DDC bus frequency
> correctly. The controller is also part of a powerdomain, so this gets added
> as an mandator
On 2023-12-31 09:37, Dafna Hirschfeld wrote:
Few fixes to amdkfd and the doc of
devm_request_free_mem_region.
Signed-off-by: Dafna Hirschfeld
---
drivers/gpu/drm/amd/amdkfd/kfd_migrate.c | 6 +++---
kernel/resource.c| 2 +-
2 files changed, 4 insertions(+), 4 delet
Hello Manuel,
see below...
On Tue, Jan 02, 2024 at 05:15:47PM +0100, Manuel Traut wrote:
> From: Alexander Warnecke
>
> [...]
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3566-pinetab2.dtsi
> b/arch/arm64/boot/dts/rockchip/rk3566-pinetab2.dtsi
> new file mode 100644
> index ..5d
On Wed, 2023-12-27 at 20:55 -0800, Teres Alexis, Alan Previn wrote:
> This series is the result of debugging issues root caused to
> races between the GuC's destroyed_worker_func being triggered
> vs repeating suspend-resume cycles with concurrent delayed
> fence signals for engine-freeing.
>
alan
Hi Thomas,
On Tue, Jan 02, 2024 at 09:26:27AM +0100, Thomas Zimmermann wrote:
> Hi Sam
>
> Am 19.12.23 um 23:03 schrieb Sam Ravnborg via B4 Relay:
> > From: Sam Ravnborg
> >
> > The p9100 driver is only relevant for the Sparcbook 3 machine,
> > and with sun4m support removed this driver is no l
From: Alexander Warnecke
This includes support for both the v0.1 units that were sent to developers and
the v2.0 units from production.
v1.0 is not included as no units are known to exist.
Working/Tested:
- SDMMC
- UART
- Buttons
- Charging/Battery/PMIC
- Audio
- USB
- Display
Signed-off-by: A
From: Alexander Warnecke
The BOE TH101MB31IG002-28A panel is a WXGA panel.
It is used in Pine64 PineTab2 and PineTab-V.
Signed-off-by: Alexander Warnecke
Signed-off-by: Manuel Traut
---
drivers/gpu/drm/panel/Kconfig | 11 +
drivers/gpu/drm/panel/Makefile
Add devicvetree binding documentation for Pine64 PineTab2
which uses the Rockchip RK3566 SoC.
Signed-off-by: Manuel Traut
Acked-by: Krzysztof Kozlowski
---
Documentation/devicetree/bindings/arm/rockchip.yaml | 8
1 file changed, 8 insertions(+)
diff --git a/Documentation/devicetree/bi
This adds support for the BOE TH101MB31IG002 LCD Panel used in PineTab2 [1] and
PineTab-V [2] as well as the devictrees for the PineTab2 v0.1 and v2.0.
The BOE LCD Panel patch was retrieved from [3]. The function-name prefix has
been adapted and the LCD init section was simplified.
The PineTab2 d
Add bindings for the BOE TH101MB31IG002-28A LCD panel. It is
used e.g. in the Pine64 PineTab2 and PineTab-V.
Signed-off-by: Manuel Traut
Reviewed-by: Krzysztof Kozlowski
---
.../display/panel/boe,th101mb31ig002-28a.yaml | 58 ++
1 file changed, 58 insertions(+)
diff --
Maxime Ripard schreef op 2024-01-02 11:03:
Hi,
On Wed, Dec 27, 2023 at 04:19:19PM +0100, AL13N wrote:
I have a RPI4B with upstream kernel 6.1 64bit and there is no
/dev/video10
present. I thought if I waited a bit more, it would appear in the
kernel,
but that was folly on my part.
Currently,
On 1/1/2024 4:52 PM, Stephen Rothwell wrote:
Hi all,
Today's linux-next merge of the drm tree got a conflict in:
drivers/accel/qaic/qaic_data.c
between commit:
78f5d33f3dd4 ("mm, treewide: rename MAX_ORDER to MAX_PAGE_ORDER")
from the mm tree and commit:
47fbee5f27ed ("accel/qaic:
Hi Maxime
On Mon, 14 Nov 2022 at 13:00, Maxime Ripard wrote:
>
> The current construction of the named mode parsing doesn't allow to extend
> it easily. Let's move it to a separate function so we can add more
> parameters and modes.
>
> In order for the tests to still pass, some extra checks are
From: Tomer Tayar
When the DRAM region size in the BAR is not a power of 2, calculating
the corresponding BAR base address should be done using the offset from
the DRAM start address, and not using directly the DRAM address.
Signed-off-by: Tomer Tayar
Reviewed-by: Oded Gabbay
Signed-off-by: Od
From: Tomer Tayar
The mechanism of aborting device reset for consecutive fatal errors is
currently only for fatal errors that are reported by FW.
A non-responsive FW and consecutive heartbeat failures is also
considered fatal, so add them as well to this mechanism to avoid
recurring device reset
From: Farah Kassabri
Currently the HMMU page tables reside in the host memory,
which will cause host access from the device for every page walk.
This can affect PCIe bandwidth in certain scenarios.
To prevent that problem, HMMU page tables will be moved to the device
memory so the miss transacti
From: Koby Elbaz
Fix a warning of a buffer overflow:
‘snprintf’ output between 38 and 47 bytes into a destination of size 32
Signed-off-by: Koby Elbaz
Reviewed-by: Oded Gabbay
Signed-off-by: Oded Gabbay
---
drivers/accel/habanalabs/common/habanalabs.h | 2 +-
1 file changed, 1 insertion(+),
From: Dani Liberman
User interrupts are MSIx interrupts coming from Gaudi2, that have
specific range of IDs and are assigned to the sole use of the user
process that opened the Gaudi2 device (reminder: there can be only
a single user process running on Gaudi2 at any given time).
The interrupts a
From: Dafna Hirschfeld
print err log if eventfd_signal return val is not 1 as expected.
Signed-off-by: Dafna Hirschfeld
Reviewed-by: Oded Gabbay
Signed-off-by: Oded Gabbay
---
drivers/accel/habanalabs/common/device.c | 14 ++
1 file changed, 10 insertions(+), 4 deletions(-)
diff
On Sat, 23 Dec 2023, Dario Binacchi wrote:
> The Makefile enables/disables the file compilation depending on
> CONFIG_DEBUG_FS.
>
> Signed-off-by: Dario Binacchi
> Reviewed-by: Jani Nikula
Thanks for the patch, pushed to drm-misc-next.
BR,
Jani.
>
> ---
>
> Changes in v2:
> - Add 'Reviewed-by
On Tue, Dec 26, 2023 at 02:56:58PM -0800, Jessica Zhang wrote:
>
>
> On 12/23/2023 7:20 AM, Manuel Traut wrote:
> > From: Alexander Warnecke
> >
> > The BOE TH101MB31IG002-28A panel is a WXGA panel.
> > It is used in Pine64 Pinetab2 and PinetabV.
> >
> Hi Manuel,
Hi Jessica,
> Sorry, I resp
Hello dri maintainers/developers,
This is a 31-day syzbot report for the dri subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/dri
During the period, 4 new issues were detected and 0 were fixed.
In total, 18 issues are still open and 31 have been
The helper is generic, it doesn't use the opaque EDID type struct drm_edid
and is also used by drivers that only support non-probeable displays such
as fixed panels.
These drivers add a list of modes using drm_mode_probed_add() and then set
a preferred mode using the drm_set_preferred_mode() helpe
Jani Nikula writes:
Hello Jani,
> On Tue, 02 Jan 2024, Javier Martinez Canillas wrote:
>> The helper is generic and doesn't use the opaque EDID type struct drm_edid
>> and is also used by drivers that only support non-probeable displays, such
>> as fixed panels.
>>
>> These drivers add a list o
On 12/20/23 14:22, Thomas Zimmermann wrote:
Store the ROM's parent device in each STI struct, so we can associate
the STI framebuffer with a device.
The new field will eventually replace the fbdev subsystem's info field,
which the function fb_is_primary_device() currently requires to detect
the
On Sat, 16 Dec 2023 14:15:27 +, Simon Ser wrote:
> Bubble up any error to the caller.
>
>
Applied to drm/drm-misc (drm-misc-next).
Thanks!
Maxime
On Sat, 30 Dec 2023 21:49:10 -0800, Randy Dunlap wrote:
> Correct all kernel-doc notation on pvr_device.h so that there are no
> kernel-doc warnings remaining.
>
> pvr_device.h:292: warning: Excess struct member 'active' description in
> 'pvr_device'
> pvr_device.h:292: warning: Excess struct mem
On Sat, 30 Dec 2023 21:48:56 -0800, Randy Dunlap wrote:
> Update kernel-doc comments in to correct all
> kernel-doc warnings:
>
> drm_gpuvm.h:148: warning: Excess struct member 'addr' description in
> 'drm_gpuva'
> drm_gpuvm.h:148: warning: Excess struct member 'offset' description in
> 'drm_gp
On Tue, 02 Jan 2024, Javier Martinez Canillas wrote:
> The helper is generic and doesn't use the opaque EDID type struct drm_edid
> and is also used by drivers that only support non-probeable displays, such
> as fixed panels.
>
> These drivers add a list of modes using drm_mode_probed_add() and th
The helper is generic and doesn't use the opaque EDID type struct drm_edid
and is also used by drivers that only support non-probeable displays, such
as fixed panels.
These drivers add a list of modes using drm_mode_probed_add() and then set
a preferred mode using the drm_set_preferred_mode() help
On Tue, 2 Jan 2024 at 10:03, Maxime Ripard wrote:
>
> Hi,
>
> On Wed, Dec 27, 2023 at 04:19:19PM +0100, AL13N wrote:
> > I have a RPI4B with upstream kernel 6.1 64bit and there is no /dev/video10
> > present. I thought if I waited a bit more, it would appear in the kernel,
> > but that was folly o
Zack Rusin writes:
Hello Zack,
> Switch to a new plane state requires unreferencing of all held surfaces.
> In the work required for mob cursors the mapped surfaces started being
> cached but the variable indicating whether the surface is currently
> mapped was not being reset. This leads to cra
Hi,
On Wed, Dec 27, 2023 at 04:19:19PM +0100, AL13N wrote:
> I have a RPI4B with upstream kernel 6.1 64bit and there is no /dev/video10
> present. I thought if I waited a bit more, it would appear in the kernel,
> but that was folly on my part.
>
> Currently, watching a movie is painful since the
Allocate stifb's fb_info instance with framebuffer_alloc(). This is
the prefered way of creating fb_info with associated driver data in
struct fb_info.par. Requires some minor changes through out the driver's
code.
The intended side effect of this patch is that the new instance of
struct fb_info n
Update fb_is_primary device() on parisc to detect the primary display
device from the Linux device instance. Aligns the code with the other
architectures. A later patch will remove the fbdev dependency from the
function's interface.
Signed-off-by: Thomas Zimmermann
Tested-by: Helge Deller
Review
The info field in struct sti_struct was used to detect the default
display device. That test is now done with the respective Linux device
and the info field is unused. Remove it.
Signed-off-by: Thomas Zimmermann
Tested-by: Helge Deller
Reviewed-by: Helge Deller
---
drivers/video/fbdev/stifb.c
Store the ROM's parent device in each STI struct, so we can associate
the STI framebuffer with a device.
The new field will eventually replace the fbdev subsystem's info field,
which the function fb_is_primary_device() currently requires to detect
the firmware's output. By using the device instead
On parisc, change detection of the primary framebuffer to test for
the Linux device instead of fbdev's fb_info in fb_is_primary_device().
Makes the test independent from fbdev.
This patchset is part of a larger effort to clean up the low-level
display handling. There are various functions that att
From: Helen Koike
Add job that runs igt on top of vkms.
Signed-off-by: Vignesh Raman
Acked-by: Jessica Zhang
Tested-by: Jessica Zhang
Acked-by: Maxime Ripard
Signed-off-by: Helen Koike
---
v2:
- do not mv modules to /lib/modules in the job definition, leave it to
crosvm-runner.sh
v3:
-
There is a spelling mistake in a drm_info message. Fix it.
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/xe/xe_wait_user_fence.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/xe/xe_wait_user_fence.c
b/drivers/gpu/drm/xe/xe_wait_user_fence.c
index b0a789
Hi Sam
Am 19.12.23 um 23:03 schrieb Sam Ravnborg via B4 Relay:
From: Sam Ravnborg
The p9100 driver is only relevant for the Sparcbook 3 machine,
and with sun4m support removed this driver is no longer relevant.
Signed-off-by: Sam Ravnborg
Cc: "David S. Miller"
Cc: Arnd Bergmann
Cc: Andreas
Hi Helge
Am 30.12.23 um 09:35 schrieb Helge Deller:
Hi Thomas,
On 12/20/23 14:22, Thomas Zimmermann wrote:
Allocate stifb's instance of fb_info with framebuffer_alloc(). This
is the preferred way of creating fb_info with associated driver data
stored in struct fb_info.par. Requires several, bu
62 matches
Mail list logo
