https://bugzilla.kernel.org/show_bug.cgi?id=51381
--- Comment #56 from Luca T. (luca.trom...@gmail.com) ---
(In reply to Alex Deucher from comment #32)
> Created attachment 138641 [details]
> testing patch
>
> Does this patch help? Note, this will probably break regular
> suspend/resume, so just
Hello Zhen,
There was a similar patch sent in last month, though which does not seem to
have been merged yet; see
https://lists.freedesktop.org/archives/nouveau/2021-April/038451.html.
Whether `ret` should be `-ENOSPC` or `-ENOMEM` is hard to say as
`nouveau_get_backlight_name()` could fail due t
The device lists are poorly ordered when the component device code is
used. This is because component_master_add_with_match() returns 0
regardless of component devices calling component_add() first. It can
really only fail if an allocation fails, in which case everything is
going bad and we're out
On 2021/5/8 14:09, Stephen Boyd wrote:
> Quoting Zhen Lei (2021-05-07 19:42:54)
>> Fix to return a negative error code from the error handling case instead
>> of 0, as done elsewhere in this function.
>>
>> Fixes: 070e64dc1bbc ("drm/msm/dpu: Convert to a chained irq chip")
>> Reported-by: Hulk R
Quoting Leizhen (ThunderTown) (2021-05-08 00:55:04)
>
>
> On 2021/5/8 14:09, Stephen Boyd wrote:
> > Quoting Zhen Lei (2021-05-07 19:42:54)
> >> Fix to return a negative error code from the error handling case instead
> >> of 0, as done elsewhere in this function.
> >>
> >> Fixes: 070e64dc1bbc ("dr
On 2021/5/8 15:58, Stephen Boyd wrote:
> Quoting Leizhen (ThunderTown) (2021-05-08 00:55:04)
>>
>>
>> On 2021/5/8 14:09, Stephen Boyd wrote:
>>> Quoting Zhen Lei (2021-05-07 19:42:54)
Fix to return a negative error code from the error handling case instead
of 0, as done elsewhere in th
On 2021/5/8 15:34, Pierre Moreau wrote:
> Hello Zhen,
>
> There was a similar patch sent in last month, though which does not seem to
> have been merged yet; see
> https://lists.freedesktop.org/archives/nouveau/2021-April/038451.html.
>
> Whether `ret` should be `-ENOSPC` or `-ENOMEM` is hard
Hi guys,
On Wed, 7 Apr 2021 at 11:27, Christian König
wrote:
> Am 07.04.21 um 09:47 schrieb Daniel Gomez:
> > On Tue, 6 Apr 2021 at 22:56, Alex Deucher wrote:
> >> On Mon, Mar 22, 2021 at 6:34 AM Christian König
> >> wrote:
> >>> Hi Daniel,
> >>>
> >>> Am 22.03.21 um 10:38 schrieb Daniel Gome
The semicolon immediately following '}' is unneeded.
Signed-off-by: Zhen Lei
---
drivers/gpu/drm/kmb/kmb_dsi.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/kmb/kmb_dsi.c b/drivers/gpu/drm/kmb/kmb_dsi.c
index 4b5d82af84b3014..231041b269f5395 10064
The Lenovo Ideapad D330 has 2 versions, one with a DMI_PRODUCT_NAME of
"81H3" and one with "81MD". Testing has shown that the "81MD" also has
a 90 degree mounted panel with a resolution of 1200x1920.
Drop the DMI_PRODUCT_NAME from the existing quirk so that the existing
quirk matches both versions
Hi Gustavo,
Your patch works! Thanks a lot! I tested it with my Freescale P5040
board and P.A.Semi Nemo board with a connected AMD Radeon HD6970 NI
graphics cards (Cayman
XT) today.
Have a nice day,
Christian
On 07 May 2021 at 08:43am, Christian Zigotzky wrote:
Hi Gustavo,
Great! I will t
https://bugzilla.kernel.org/show_bug.cgi?id=212957
Arvin (arvin.ke...@gmail.com) changed:
What|Removed |Added
CC||arvin.ke...@gmail.com
---
[ Daniel, please fix your broken email setup. You have this insane
"Reply-to" list that just duplicates all the participants. Very
broken, very annoying ]
On Fri, May 7, 2021 at 8:53 AM Daniel Vetter wrote:
>
> So personally I think the entire thing should just be thrown out, it's all
> levels of
https://bugzilla.kernel.org/show_bug.cgi?id=51381
--- Comment #57 from luminoso (lumin...@gmail.com) ---
For users still facing this issue, I workaround it with this:
https://github.com/aelveborn/vgaswitcheroo-systemd
Basically before suspending it restores the GPU powerstate and resumes it once
I have heard nothing about this, and it remains the only warning from
my allmodconfig build (I have another one for drm compiled with clang,
but there I at least heard back that a fix exists).
Since I am going to release rc1 tomorrow, and I don't want to release
it with an ugly compiler warning, I
https://bugzilla.kernel.org/show_bug.cgi?id=51381
--- Comment #58 from Luca T. (luca.trom...@gmail.com) ---
(In reply to luminoso from comment #57)
> For users still facing this issue, I workaround it with this:
> https://github.com/aelveborn/vgaswitcheroo-systemd
>
> Basically before suspending
From: Rob Clark
Someone on IRC once asked an innocent enough sounding question: Why
with xf86-video-modesetting is es2gears limited at 120fps.
So I broke out the perfetto tracing mesa MR and took a look. It turns
out the problem was drm_atomic_helper_dirtyfb(), which would end up
waiting for v
From: Rob Clark
drm_atomic_helper_dirtyfb() will end up stalling for vblank on "video
mode" type displays, which is pointless and unnecessary. Add an
optional helper vfunc to determine if a plane is attached to a CRTC
that actually needs dirtyfb, and skip over them.
Signed-off-by: Rob Clark
--
From: Rob Clark
Signed-off-by: Rob Clark
---
drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c
b/drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c
index 5a74f93e29da..868ee6136438 100644
--- a/drivers/gp
Hi,
Beginning with kernel 5.12 I started getting system hangs/freezes, particularly
when starting the Chrome browser. At least some of these are logged as a timeout.
My hardware is a NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev
a1). I tried to bisect the error, but the error
Add driver for TI SN65DSI83 Single-link DSI to Single-link LVDS bridge
and TI SN65DSI84 Single-link DSI to Dual-link or 2x Single-link LVDS
bridge. TI SN65DSI85 is unsupported due to lack of hardware to test on,
but easy to add.
The driver operates the chip via I2C bus. Currently the LVDS clock ar
Add DT binding document for TI SN65DSI83 and SN65DSI84 DSI to LVDS bridge.
Reviewed-by: Linus Walleij
Signed-off-by: Marek Vasut
Cc: Douglas Anderson
Cc: Jagan Teki
Cc: Laurent Pinchart
Cc: Linus Walleij
Cc: Rob Herring
Cc: Sam Ravnborg
Cc: Stephen Boyd
Cc: devicet...@vger.kernel.org
To:
On 5/7/21 2:48 PM, Dave Stevenson wrote:
[...]
+static void sn65dsi83_enable(struct drm_bridge *bridge)
+{
+ struct sn65dsi83 *ctx = bridge_to_sn65dsi83(bridge);
+ unsigned int pval;
+ u16 val;
+ int ret;
+
+ /* Clear reset, disable PLL */
+ regmap_write(ctx-
On 5/7/21 11:17 AM, Dave Stevenson wrote:
On Thu, 6 May 2021 at 21:51, Marek Vasut wrote:
On 5/6/21 6:03 PM, Frieder Schrempf wrote:
On 06.05.21 17:46, Marek Vasut wrote:
On 5/6/21 5:38 PM, Frieder Schrempf wrote:
[...]
Works on i.MX8MM with SN65DSI84 and a single link LVDS display (1024x60
If 'mipid_detect()' fails, we must free 'md' to avoid a memory leak.
While at it, modernize the function:
- remove a useless message in case of memory allocation failure
- change a '== NULL' into a '!'
Fixes: 66d2f99d0bb5 ("omapfb: add support for MIPI-DCS compatible LCDs")
Signed-off-by: C
https://bugzilla.kernel.org/show_bug.cgi?id=51381
--- Comment #59 from Luca T. (luca.trom...@gmail.com) ---
(In reply to luminoso from comment #57)
> For users still facing this issue, I workaround it with this:
> https://github.com/aelveborn/vgaswitcheroo-systemd
>
> Basically before suspending
26 matches
Mail list logo
