'status = "okay";' doesn't make a difference.
What do I miss here?
As mentioned by Stefan in the last version, in Raspberry Pi OS, there is
a systemd script which is trying to check for the V3D driver (/usr/lib
/systemd/scripts/gldriver_test.sh). Within the first check, "raspi
Hi Phil,
Am 14.04.24 um 20:43 schrieb Phil Elwell:
Hello all,
On Fri, 12 Apr 2024 at 18:17, Stefan Wahren wrote:
Hi Maíra,
[add Phil & Dave]
Am 12.04.24 um 15:25 schrieb Maíra Canal:
RPi 0-3 is packed with a GPU that provides 3D rendering capabilities to
the RPi. Currently, the downst
Hi Maíra,
[add Phil & Dave]
Am 12.04.24 um 15:25 schrieb Maíra Canal:
RPi 0-3 is packed with a GPU that provides 3D rendering capabilities to
the RPi. Currently, the downstream kernel uses an overlay to enable the
GPU and use GPU hardware acceleration. When deploying a mainline kernel
to the
anged, 1 deletion(-)
Reviewed-by: Stefan Hajnoczi
signature.asc
Description: PGP signature
t; 1 file changed, 1 deletion(-)
Reviewed-by: Stefan Hajnoczi
signature.asc
Description: PGP signature
sock/virtio_transport.c | 1 -
> 1 file changed, 1 deletion(-)
Reviewed-by: Stefan Hajnoczi
signature.asc
Description: PGP signature
t; 1 file changed, 1 deletion(-)
Reviewed-by: Stefan Hajnoczi
signature.asc
Description: PGP signature
d KMS support for Raspberry Pi.")
Signed-off-by: Dom Cobley
Signed-off-by: Stefan Wahren
---
drivers/gpu/drm/vc4/vc4_drv.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/vc4/vc4_drv.c b/drivers/gpu/drm/vc4/vc4_drv.c
index c133e96b8aca..4f17840df9d3 100644
--- a/drive
vhost and VIRTIO-related parts:
Reviewed-by: Stefan Hajnoczi
On Wed, 22 Nov 2023 at 07:50, Christian Brauner wrote:
>
> Ever since the evenfd type was introduced back in 2007 in commit
> e1ad7468c77d ("signal/timer/event: eventfd core") the eventfd_signal()
> funct
Hi Jordan
On Sat, Jan 20, 2024 at 01:47:58AM -0800, Jordan Justen wrote:
> On 2024-01-19 12:24:24, Stefan Dirsch wrote:
> > Hi Jordan
> >
> > Thanks for digging into this!
> >
> > On Fri, Jan 19, 2024 at 12:10:37PM -0800, Jordan Justen wrote:
> > > O
Hi Jordan
Thanks for digging into this!
On Fri, Jan 19, 2024 at 12:10:37PM -0800, Jordan Justen wrote:
> On 2024-01-18 04:37:52, Stefan Dirsch wrote:
> > Hi
> >
> > I noticed that with version 23.3.x Mesa no longer can be built with python
> > 2.6. It st
On Thu, Jan 18, 2024 at 01:37:52PM +0100, Stefan Dirsch wrote:
> Hi
>
> I noticed that with version 23.3.x Mesa no longer can be built with python
> 2.6. It still worked with Mesa 23.2.1.
Of course I've meant python 3.6. Sorry for the confusion!
> It fails with
>
> [
On Fri, Jan 19, 2024 at 12:35:58PM -0500, Matt Turner wrote:
> On Thu, Jan 18, 2024 at 10:22 AM Stefan Dirsch wrote:
> > I noticed that with version 23.3.x Mesa no longer can be built with python
> > 2.6. It still worked with Mesa 23.2.1.
>
> For anyone who got this f
On Thu, Jan 18, 2024 at 01:37:52PM +0100, Stefan Dirsch wrote:
> Hi
>
> I noticed that with version 23.3.x Mesa no longer can be built with python
> 2.6. It still worked with Mesa 23.2.1.
I've meant python 3.6 of course!
CU,
Stefan
Public K
typing.OrderedDict
have already been used in 23.2.1 (although it was in gen_sort_tags.py and
now has been moved to new intel_genxml.py). So not sure why this fails now
or was working before ...
Any help here would be appreciated. SUSE is definitely interested in shipping
the latest Mesa with our
Hi Neil,
Am 09.01.24 um 12:19 schrieb neil.armstr...@linaro.org:
Hi,
On 09/01/2024 08:09, Shengyang Chen wrote:
This patchset adds waveshare 7inch touchscreen panel support
for the StarFive JH7110 SoC.
Could you precise which SKU you're referring to ? is it 19885 =>
CR0: 80050033
CR2: 0028 CR3: 000104006004 CR4: 003706f0
Signed-off-by: Zack Rusin
Fixes: 485d98d472d5 ("drm/vmwgfx: Add support for CursorMob and
CursorBypass 4")
Reported-by: Stefan Hoffmeister
Closes: https://gitlab.freedesktop.org/drm/misc/
ns, to be honest.
Many thanks for any input
Stefan
Resending with all MAINTAINTERS cc'ed because no ACK.
Quoting Stefan Hoffmeister :
Previously reported at
https://gitlab.freedesktop.org/drm/misc/-/issues/34 and
https://bugs.kde.org/show_bug.cgi?id=478308
vmwgfx runs into kernel oops related to atomic cursors with KDE
Plasma 6. I am
Previously reported at
https://gitlab.freedesktop.org/drm/misc/-/issues/34 and
https://bugs.kde.org/show_bug.cgi?id=478308
vmwgfx runs into kernel oops related to atomic cursors with KDE Plasma
6. I am able to reproduce this with
* VMware Workstation 17.5 (on Windows 11 Professional)
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 new compatible for the raspberrypi panel driver and its dt-binding.
Patch 2 add new display mode and new
Hi Iago,
Am 30.10.23 um 11:18 schrieb Iago Toral:
El lun, 30-10-2023 a las 10:57 +0100, Stefan Wahren escribió:
Hi Iago,
Am 30.10.23 um 09:28 schrieb Iago Toral Quiroga:
BCM2712, Raspberry Pi 5's SoC, contains a V3D core. So add its
specific
compatible to the bindings.
v2: new, requested
Hi Iago,
Am 30.10.23 um 09:28 schrieb Iago Toral Quiroga:
BCM2712, Raspberry Pi 5's SoC, contains a V3D core. So add its specific
compatible to the bindings.
v2: new, requested by Stefan Wahren.
Thanks for sending this but the line above belongs below --- since it's
not relevant after
Hi Iago,
Am 30.10.23 um 09:28 schrieb Iago Toral Quiroga:
This patch updates a number of register addresses that have
been changed in Raspberry Pi 5 (V3D 7.1) and updates the
code to use the corresponding registers and addresses based
on the actual V3D version.
v2:
- added s-o-b and commit
Hi Iago,
Am 30.10.23 um 11:14 schrieb Iago Toral:
Hi Stefan,
El lun, 30-10-2023 a las 10:58 +0100, Stefan Wahren escribió:
Hi Iago,
Am 30.10.23 um 09:28 schrieb Iago Toral Quiroga:
This patch updates a number of register addresses that have
been changed in Raspberry Pi 5 (V3D 7.1
Hi Iago,
Am 30.10.23 um 09:28 schrieb Iago Toral Quiroga:
This is required to get the V3D module to load with Raspberry Pi 5.
v2:
- added s-o-b and commit message. (Maíra)
- keep order of compatible strings. (Stefan Wahren)
as in the other patch, please move the changelog below
Hi Iago,
additional to Maria's comments:
Please keep the order of the compatible strings.
Also you need to update the device tree binding before this patch:
Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml
Also make sure that the series is send to the maintainers, not just
dri-devel by
On 9/7/23 01:29, David Lechner wrote:
On 9/6/23 11:22 AM, Stefan x Nilsson wrote:
Add a new driver for the Sitronix st7735s display controller
together with a 0.96" 80x160 color TFT display by Winstar.
The driver is very similar to the st7735r driver, but uses a
different pipe_enable seq
igned-off-by: Stefan x Nilsson
---
Stefan x Nilsson (2):
dt-bindings: display: Add st7735s driver
drm: tiny: Add st7735s driver
.../bindings/display/sitronix,st7735s.yaml | 81 +++
MAINTAINERS| 7 +
drivers/gpu/drm/tiny/Kc
igned-off-by: Stefan x Nilsson
---
MAINTAINERS| 1 +
drivers/gpu/drm/tiny/Kconfig | 14 +++
drivers/gpu/drm/tiny/Makefile | 1 +
drivers/gpu/drm/tiny/st7735s.c | 264 +
4 files changed, 280 insertions(+)
diff --git a/MAINTAIN
Add bindings for a driver for Sitronix st7735s display controller, as
well as for a Winstar wf0096atyaa3dnn0 0.96" 80x160 TFT panel.
Signed-off-by: Stefan x Nilsson
---
.../bindings/display/sitronix,st7735s.yaml | 81 ++
MAINTA
On Fri, Feb 24, 2023 at 03:37:51PM +0100, David Heidelberg wrote:
> From: Stefan Hajnoczi
>
> Make it possible to boot directly from a virtiofs file system with tag
> 'myfs' using the following kernel parameters:
>
> rootfstype=virtiofs root=myfs rw
>
> Booting dire
]
[ 825.617586] ---[ end trace ]---
Therefore, deal with the deadlock as suggested by [1], using the
function drm_modeset_backoff().
[1] https://docs.kernel.org/gpu/drm-kms.html?highlight=kms#kms-locking
Fixes: 6bed2ea3cb38 ("drm/vc4: hdmi: Reset link on hotplug")
Reported-
Hi Maíra,
Am 28.12.22 um 20:49 schrieb Maíra Canal:
Hi Stefan,
I was able to reproduce this error on drm-misc-next. I bisected,
and I got into commit 6bed2ea3cb38. I noticed that the crtc->mutex is
being locked twice, and this might be causing the problem. I wrote a
patch to try to
Hi,
Am 21.12.22 um 20:46 schrieb Stefan Wahren:
Hi,
if i enable PROVE_LOCKING on the Raspberry Pi 3 B+
(arm/multi_v7_defconfig) using v6.1 (didn't test older versions) i'm
getting the following warning:
[ 204.043396] WARNING: CPU: 2 PID: 42 at
drivers/gpu/drm/drm_modeset_lock.c:276
Hi,
if i enable PROVE_LOCKING on the Raspberry Pi 3 B+
(arm/multi_v7_defconfig) using v6.1 (didn't test older versions) i'm
getting the following warning:
[ 204.043396] WARNING: CPU: 2 PID: 42 at
drivers/gpu/drm/drm_modeset_lock.c:276 drm_modeset_drop_locks+0x6c/0x70
[ 204.043426] Modules
block braces unnecessary. Remove that as well.
>
> Issue identified using platform_get_irq.cocci coccicheck script.
>
> Signed-off-by: Deepak R Varma
Reviewed-by: Stefan Agner
--
Stefan
> ---
> drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 4 +---
> 1 file changed, 1 inser
Am 11.11.22 um 22:08 schrieb Stefan Wahren:
Hi Maxime,
Am 29.09.22 um 11:21 schrieb Maxime Ripard:
This is a revert of commit fd5894fa2413 ("drm/vc4: hdmi: Remove clock
rate initialization"), with the code slightly moved around.
It turns out that we can't downright remove that
Hi Maxime,
Am 29.09.22 um 11:21 schrieb Maxime Ripard:
This is a revert of commit fd5894fa2413 ("drm/vc4: hdmi: Remove clock
rate initialization"), with the code slightly moved around.
It turns out that we can't downright remove that code from the driver,
since the Pi0-3 and Pi4 are in
Hi Maxime,
Am 20.09.22 um 14:50 schrieb Maxime Ripard:
The firmware allows to query for its clocks the operating range of a
given clock. We'll need this for some drivers (KMS, in particular) to
infer the state of some configuration options, so let's create a
function to do so.
Signed-off-by:
Am 10.10.22 um 10:50 schrieb Maxime Ripard:
Hi Mark, Stefan,
On Thu, Sep 29, 2022 at 11:21:16AM +0200, Maxime Ripard wrote:
Here's a series addressing the current bug that has been reported for the
RaspberryPi3, where booting without an HDMI monitor attached and with vc4
compiled as a module
Am 29.09.22 um 11:35 schrieb Maxime Ripard:
On Tue, Sep 27, 2022 at 03:15:17PM +0200, Maxime Ripard wrote:
On Tue, Sep 27, 2022 at 02:25:12PM +0200, Maxime Ripard wrote:
On Tue, Sep 27, 2022 at 01:42:40PM +0200, Maxime Ripard wrote:
On Tue, Sep 27, 2022 at 01:12:35PM +0200, Stefan Wahren
Hi Maxime,
Am 27.09.22 um 15:15 schrieb Maxime Ripard:
On Tue, Sep 27, 2022 at 02:25:12PM +0200, Maxime Ripard wrote:
On Tue, Sep 27, 2022 at 01:42:40PM +0200, Maxime Ripard wrote:
On Tue, Sep 27, 2022 at 01:12:35PM +0200, Stefan Wahren wrote:
Am 27.09.22 um 11:42 schrieb Maxime Ripard
Am 27.09.22 um 11:42 schrieb Maxime Ripard:
On Tue, Sep 27, 2022 at 09:25:54AM +0200, Maxime Ripard wrote:
Hi Stefan,
On Mon, Sep 26, 2022 at 08:50:12PM +0200, Stefan Wahren wrote:
Am 26.09.22 um 14:47 schrieb Maxime Ripard:
On Mon, Sep 26, 2022 at 02:40:48PM +0200, Marc Kleine-Budde wrote
Hi Maxime,
Am 27.09.22 um 09:25 schrieb Maxime Ripard:
Hi Stefan,
On Mon, Sep 26, 2022 at 08:50:12PM +0200, Stefan Wahren wrote:
Am 26.09.22 um 14:47 schrieb Maxime Ripard:
On Mon, Sep 26, 2022 at 02:40:48PM +0200, Marc Kleine-Budde wrote:
On 26.09.2022 14:08:04, Stefan Wahren wrote:
Hi
Hi Maxime,
Am 26.09.22 um 14:47 schrieb Maxime Ripard:
On Mon, Sep 26, 2022 at 02:40:48PM +0200, Marc Kleine-Budde wrote:
On 26.09.2022 14:08:04, Stefan Wahren wrote:
Hi Marc,
Am 26.09.22 um 12:21 schrieb Marc Kleine-Budde:
On 22.09.2022 17:06:00, Maxime Ripard wrote:
I'm on a Raspberry Pi
Hi Marc,
Am 26.09.22 um 12:21 schrieb Marc Kleine-Budde:
On 22.09.2022 17:06:00, Maxime Ripard wrote:
I'm on a Raspberry Pi 3 Model B+ running current Debian testing ARM64,
using Debian's v5.19 kernel (Debian's v5.18 was working flawless).
| [0.00] Booting Linux on physical CPU
Hi Marc,
Am 22.09.22 um 16:54 schrieb Marc Kleine-Budde:
Hello,
I'm on a Raspberry Pi 3 Model B+ running current Debian testing ARM64,
using Debian's v5.19 kernel (Debian's v5.18 was working flawless).
| [0.00] Booting Linux on physical CPU 0x00 [0x410fd034]
| [0.00]
Hi Maxime,
Am 20.09.22 um 14:50 schrieb Maxime Ripard:
We'll need the clock IDs in more drivers than just the clock driver from
now on, so let's move them in the firmware header.
recently as i reviewed the clk-raspberrypi i noticed this, too. But from
my point of view the clock ids should go
Hi Maxime,
Am 15.09.22 um 09:54 schrieb Maxime Ripard:
On Wed, Sep 14, 2022 at 08:26:55PM +0200, Stefan Wahren wrote:
Am 14.09.22 um 20:14 schrieb Stephen Boyd:
Quoting Stefan Wahren (2022-09-14 11:09:04)
Am 14.09.22 um 20:05 schrieb Stephen Boyd:
Quoting Stefan Wahren (2022-09-14 10:45:48
Hi Stephen,
Am 14.09.22 um 20:20 schrieb Stephen Boyd:
Quoting Stefan Wahren (2022-09-14 11:09:04)
Am 14.09.22 um 20:05 schrieb Stephen Boyd:
Quoting Stefan Wahren (2022-09-14 10:45:48)
Am 14.09.22 um 17:50 schrieb Stephen Boyd:
Furthermore, I wonder if even that part needs
Am 14.09.22 um 20:14 schrieb Stephen Boyd:
Quoting Stefan Wahren (2022-09-14 11:09:04)
Am 14.09.22 um 20:05 schrieb Stephen Boyd:
Quoting Stefan Wahren (2022-09-14 10:45:48)
Am 14.09.22 um 17:50 schrieb Stephen Boyd:
Furthermore, I wonder if even that part needs to be implemented. Why
Am 14.09.22 um 20:05 schrieb Stephen Boyd:
Quoting Stefan Wahren (2022-09-14 10:45:48)
Am 14.09.22 um 17:50 schrieb Stephen Boyd:
Furthermore, I wonder if even that part needs to be implemented. Why
not make a direct call to rpi_firmware_property() and get the max rate?
All of that can live
Hi,
Am 14.09.22 um 17:50 schrieb Stephen Boyd:
Quoting Maxime Ripard (2022-08-15 08:31:24)
@@ -254,6 +255,33 @@ static int raspberrypi_fw_dumb_determine_rate(struct
clk_hw *hw,
return 0;
}
+unsigned long rpi_firmware_clk_get_max_rate(struct clk *clk)
+{
+ const struct
Hi Maxime,
Am 05.09.22 um 16:57 schrieb Maxime Ripard:
On Fri, Sep 02, 2022 at 01:28:16PM +0200, Noralf Trønnes wrote:
Den 01.09.2022 21.35, skrev Noralf Trønnes:
I have finally found a workaround for my kernel hangs.
Dom had a look at my kernel and found that the VideoCore was fine, and
Product_id, customer_id and eco_id should not be zero. The different versions
of model 0x7000, revision 0x6203 can differ in stream_count, minor_feature5 and
minor_features7.
{
.model = 0x7000,
.revision = 0x6203,
f-by: Dave Stevenson
Signed-off-by: Maxime Ripard
After seeing the same warning as Stefan reported in the link below,
but on the Raspberry Pi 4B:
https://www.spinics.net/lists/dri-devel/msg354170.html
a separate bisection effort led me to this commit, before is fine,
after produces 4 warni
ime Ripard
After seeing the same warning as Stefan reported in the link below,
but on the Raspberry Pi 4B:
https://www.spinics.net/lists/dri-devel/msg354170.html
a separate bisection effort led me to this commit, before is fine,
after produces 4 warnings during boot, see attached log.
Which con
Hi Naresh,
thanks for your report.
Am 30.06.22 um 18:11 schrieb Naresh Kamboju:
The following kernel warning found on Rpi4 while booting linux next-20220630.
Boot log details [1] & [2].
i think this is related to this:
https://lists.freedesktop.org/archives/dri-devel/2022-June/362244.html
Hi Maxime,
Am 30.06.22 um 09:37 schrieb Maxime Ripard:
Hi Stefan,
On Wed, Jun 29, 2022 at 10:50:21PM +0200, Stefan Wahren wrote:
Hi Maxime,
i tested todays drm-misc-next 9db35bb349 with Raspberry Pi 3 B Plus
(arm/multi_v7_defconfig, mainline DTB) and get the following warning in the
kernel
Hi Maxime,
i tested todays drm-misc-next 9db35bb349 with Raspberry Pi 3 B Plus
(arm/multi_v7_defconfig, mainline DTB) and get the following warning in
the kernel logs:
[ 25.698459] vc4-drm soc:gpu: bound 3f40.hvs (ops vc4_hvs_ops [vc4])
[ 25.698657] [ cut here
Hi,
Am 09.06.22 um 23:33 schrieb Stefan Wahren:
Hi Peter,
Am 09.06.22 um 13:52 schrieb Peter Robinson:
As of Linux 5.18.0, module vc4 apparently isn't working on
Raspberry Pi
3B any more.
If a monitor is attached to the device, the boot messages show up as
usual, but right when KMS starts
Hi Peter,
Am 09.06.22 um 13:52 schrieb Peter Robinson:
As of Linux 5.18.0, module vc4 apparently isn't working on Raspberry Pi
3B any more.
If a monitor is attached to the device, the boot messages show up as
usual, but right when KMS starts, the screen turns black. Similarly, the
screen also
Hi,
Am 08.06.22 um 16:36 schrieb Maxime Ripard:
Hi Peter(s)
On Wed, Jun 08, 2022 at 02:10:19PM +0100, Peter Robinson wrote:
Hi Peter,
Adding Stefan and Maxime
As of Linux 5.18.0, module vc4 apparently isn't working on Raspberry Pi
3B any more.
If a monitor is attached to the device
Hi Melissa,
Am 08.06.22 um 14:51 schrieb Melissa Wen:
On 06/03, Peter Robinson wrote:
This is a follow up from my v4 patchset. The power management pieces have
been split out to a separate independent set of patches by Stefan [1]. This
version 5 of the DRM patches are independent and given
Hi Peter,
i didn't subscribe to dri-devel, but i noticed your bug report.
Could you please provide more information:
Which kernel config do you use (is it a defconfig)?
Do you use the mainline device tree blob or the Raspberry Pi DTB?
Please provide the version/date of the GPU firmware?
Do you
Am 01.06.22 um 13:02 schrieb Peter Robinson:
From: Nicolas Saenz Julienne
BCM2711, the SoC used on the Raspberry Pi 4 has a different GPU than its
predecessors. Enable it.
Signed-off-by: Nicolas Saenz Julienne
Signed-off-by: Peter Robinson
Reviewed-by: Stefan Wahren
compatible = "brcm,bcm2711-v3d";
unfortunately this doesn't match with patch #3 anymore. Except of this
everything looks good here.
Stefan
+ reg = <0x0 0x7ec0 0x4000>,
+ <0x0 0x7ec04000 0x4000>;
+
[add Melissa]
Am 01.06.22 um 13:02 schrieb Peter Robinson:
Add compatible string and Kconfig options for bcm2711.
Signed-off-by: Nicolas Saenz Julienne
Signed-off-by: Peter Robinson
Reviewed-by: Stefan Wahren
---
Changes since v5:
- Change compatible to align downstream and othee HW
Am 01.06.22 um 13:02 schrieb Peter Robinson:
BCM2711, Raspberry Pi 4's SoC, contains a V3D core. So add its specific
compatible to the bindings.
Signed-off-by: Nicolas Saenz Julienne
Signed-off-by: Peter Robinson
Reviewed-by: Stefan Wahren
Am 01.06.22 um 13:02 schrieb Peter Robinson:
BCM2711, the SoC used on the Raspberry Pi 4 has a different 3D
render GPU IP than its predecessors. Enable it it on multi v7
and bcm2835 configs.
Signed-off-by: Nicolas Saenz Julienne
Signed-off-by: Peter Robinson
Reviewed-by: Stefan Wahren
Hi,
Am 11.04.22 um 13:00 schrieb Stefan Wahren:
Hi Maxime,
Am 11.04.22 um 09:35 schrieb Maxime Ripard:
Hi Stefan,
On Sun, Apr 10, 2022 at 02:32:02AM +0200, Stefan Wahren wrote:
Am 09.04.22 um 21:25 schrieb Stefan Wahren:
Hi,
today i tested Linux 5.18-rc1 on my Raspberry Pi 400 connected
ed-off-by: Marek Vasut
> Cc: Alexander Stein
> Cc: Laurent Pinchart
> Cc: Lucas Stach
> Cc: Peng Fan
> Cc: Robby Cai
> Cc: Sam Ravnborg
> Cc: Stefan Agner
> ---
> V2: Check crtc for non-NULL before dereferencing it in
> mxsfb_crtc_set_crc_source
> ---
> d
ier in probe.
Fixes: 2f733d6194bd ("drm/panel: Add support for the Raspberry Pi 7"
Touchscreen.")
Signed-off-by: Dave Stevenson
Signed-off-by: Stefan Wahren
---
drivers/gpu/drm/panel/panel-raspberrypi-touchscreen.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/
This small patch series tries to upstream 2 minor issues which has been
fixed in the vendor tree by Dave Stevenson.
Dave Stevenson (2):
drm/panel/raspberrypi-touchscreen: Avoid NULL deref if not initialised
drm/panel/raspberrypi-touchscreen: Initialise the bridge in prepare
berry Pi 7"
Touchscreen.")
Signed-off-by: Dave Stevenson
Signed-off-by: Stefan Wahren
---
drivers/gpu/drm/panel/panel-raspberrypi-touchscreen.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/panel/panel-raspberrypi-touchscreen.c
b/
Hi Maxime,
Am 11.04.22 um 09:35 schrieb Maxime Ripard:
Hi Stefan,
On Sun, Apr 10, 2022 at 02:32:02AM +0200, Stefan Wahren wrote:
Am 09.04.22 um 21:25 schrieb Stefan Wahren:
Hi,
today i tested Linux 5.18-rc1 on my Raspberry Pi 400 connected to my
HDMI display (multi_v7_defconfig
Am 09.04.22 um 21:25 schrieb Stefan Wahren:
Hi,
today i tested Linux 5.18-rc1 on my Raspberry Pi 400 connected to my
HDMI display (multi_v7_defconfig + CONFIG_ARM_LPAE, firmware:
2021-01-08T14:31:16) and i'm getting these strange errors from
raspberrypi-firmware driver / vc4 during boot
Hi Phil,
Am 09.04.22 um 22:03 schrieb Phil Elwell:
You know the drill, Stefan - what's in your config.txt?
sure. Everything commented out.
Regards
Phil
On Sat, 9 Apr 2022, 20:26 Stefan Wahren, wrote:
Hi,
today i tested Linux 5.18-rc1 on my Raspberry Pi 400 connected to my
Hi,
today i tested Linux 5.18-rc1 on my Raspberry Pi 400 connected to my
HDMI display (multi_v7_defconfig + CONFIG_ARM_LPAE, firmware:
2021-01-08T14:31:16) and i'm getting these strange errors from
raspberrypi-firmware driver / vc4 during boot:
[ 13.094733] fb0: switching to vc4 from
t; Cc: Robby Cai
> Cc: Sam Ravnborg
> Cc: Stefan Agner
> ---
> drivers/gpu/drm/mxsfb/Kconfig | 16 +
> drivers/gpu/drm/mxsfb/Makefile | 2 +
> drivers/gpu/drm/mxsfb/lcdif_drv.c | 367 +
> drivers/gpu/drm/mxsfb/lcd
Hi Maxime,
i applied your patch on top of Linux 5.17-rc4 and it fixes the tones of
warnings after boot (see below). So you can have my
Tested-by: Stefan Wahren
[ 8.341814] [ cut here ]
[ 8.341820] WARNING: CPU: 1 PID: 7 at
drivers/gpu/drm/vc4/vc4_hdmi_regs.h:417
+---
drivers/net/ieee802154/mrf24j40.c | 4 +---
[...]
For the ieee802154 drivers:
Acked-by: Stefan Schmidt
regards
Stefan Schmidt
why we do this.
Signed-off-by: Christian König
Tested-by: Stefan Fritsch
Please also add a cc for linux-stable, so that this is fixed in 5.15.x
Cheers,
Stefan
---
drivers/gpu/drm/nouveau/nouveau_fence.c | 28 +
1 file changed, 15 insertions(+), 13 deletions(-)
diff --git
bool must_wait = true;
With that it works and I don't see the flickering in a short test. I
will do more testing, but maybe Dan can test, too.
Cheers,
Stefan
After fixing the typo the patch is working for me, also. dmesg is also
clean. I will continue running the patched kernel. If I see any
issues, I
ee the flickering in a short test. I
will do more testing, but maybe Dan can test, too.
Cheers,
Stefan
On 07.12.21 20:01, Dan Moulding wrote:
Please test if that patch changes anything.
Looks like the driver is not functional after applying that patch. As
soon as the display manager is sup
Reviewed-by: Daniel Vetter
Link:
https://patchwork.freedesktop.org/patch/msgid/20210702111642.17259-4-christian.koe...@amd.com
This sounds like performance is impacted severely by that commit. Can
this be fixed somehow? A partial dmesg is below.
Cheers,
Stefan
dmesg |grep -i -e drm
| 2 +-
> drivers/virtio/virtio_mem.c| 2 +-
> fs/fuse/virtio_fs.c| 4 ++--
> include/linux/virtio.h | 1 +
> net/9p/trans_virtio.c | 2 +-
> net/vmw_vsock/virtio_transport.c | 4 ++--
> sound/virtio/virti
.
>
> Reported-by: Martin Kepplinger
> Signed-off-by: Guido Günther
> Reviewed-by: Lucas Stach
Acked-by: Stefan Agner
> ---
> drivers/gpu/drm/mxsfb/mxsfb_kms.c | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/gpu/drm/mxsfb/mxsfb_kms.c
>
On 2021-10-11 15:41, Guido Günther wrote:
> media-bus-formats.h has them in hexadecimal as well so matching with
> that file saves one conversion when debugging.
>
> Signed-off-by: Guido Günther
> Reviewed-by: Lucas Stach
> Reviewed-by: Robert Foss
Acked-by: Stefan Agner
On 2021-10-05 14:35, Matthias Schiffer wrote:
> On Thu, 2021-09-16 at 14:50 +0200, Matthias Schiffer wrote:
>> On Fri, 2020-08-21 at 15:41 +0200, Stefan Agner wrote:
>> > Hi Matthias,
>> >
>> > On 2020-08-20 12:58, Matthias Schiffer wrote:
>> > &g
Hi,
Am 15.07.21 um 18:35 schrieb Stefan Wahren:
> Hi guys,
>
> starting with Linux 5.14-rc1 the framebuffer console on Raspberry Pi 3/4
> (no U-Boot, multi_v7_defconfig) isn't available anymore. The display
> shows the rainbow screen from the bootloader and than the HDMI scre
tected!
I compared the changes to the config (based on multi_v7_defconfig) with
and without this patch and it shows a lot of changes. Is this intended?
Best regards
Stefan
Hi Maxime,
Am 07.07.21 um 15:11 schrieb Maxime Ripard:
> On Tue, Jul 06, 2021 at 05:45:27PM +0200, Stefan Wahren wrote:
>> Hi Maxime,
>>
>> Am 06.07.21 um 15:21 schrieb Maxime Ripard:
>>> Hi Stefan,
>>>
>>> On Tue, Jul 06, 2021 at 12:48:05PM +0200
Hi Maxime,
Am 06.07.21 um 15:21 schrieb Maxime Ripard:
> Hi Stefan,
>
> On Tue, Jul 06, 2021 at 12:48:05PM +0200, Stefan Wahren wrote:
>> Am 06.07.21 um 11:58 schrieb Maxime Ripard:
>>> Hi,
>>>
>>> On Mon, Jul 05, 2021 at 11:36:34PM +0200, Stefan Wahren
Hi,
Am 06.07.21 um 11:58 schrieb Maxime Ripard:
> Hi,
>
> On Mon, Jul 05, 2021 at 11:36:34PM +0200, Stefan Wahren wrote:
>> Commit "drm/vc4: hdmi: Convert to gpiod" changes the behavior of
>> vc4_hdmi_connector_detect() which results into CPU hangs in case there
: hdmi: Convert to gpiod")
Signed-off-by: Stefan Wahren
---
drivers/gpu/drm/vc4/vc4_hdmi.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/vc4/vc4_hdmi.c b/drivers/gpu/drm/vc4/vc4_hdmi.c
index aab1b36..cf8339c 100644
--- a/drivers/gpu/drm/vc4/vc4_hdmi
Am 28.06.21 um 14:28 schrieb Maxime Ripard:
> On Thu, Jun 17, 2021 at 07:41:09PM +0200, Stefan Wahren wrote:
>> Hi Maxime,
>>
>> Am 17.06.21 um 17:25 schrieb Maxime Ripard:
>>> Hi Stefan,
>>>
>>> On Sat, Jun 12, 2021 at 12:04:08PM +0200, Stefan Wah
The connector_type for following two EDT displays is missing:
- EDT ETM0430G0DH6
- EDT ETM0700G0BDH6
Both are parallel displays thus add the corresponding connector_type.
Signed-off-by: Stefan Riedmueller
---
drivers/gpu/drm/panel/panel-simple.c | 2 ++
1 file changed, 2 insertions(+)
diff
Add corresponding bus_format and bus_flags for the EDT ETM0430G0DH6
display.
Signed-off-by: Stefan Riedmueller
---
drivers/gpu/drm/panel/panel-simple.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/panel/panel-simple.c
b/drivers/gpu/drm/panel/panel-simple.c
index
1 - 100 of 924 matches
Mail list logo
