On Fri, Mar 7, 2025 at 4:55 PM Jocelyn Falempe wrote:
>
> On 06/03/2025 16:52, Simona Vetter wrote:
> > On Thu, Mar 06, 2025 at 02:24:51PM +0100, Jocelyn Falempe wrote:
> >> On 06/03/2025 05:52, Matthew Wilcox wrote:
> >>> On Thu, Mar 06, 2025 at 12:25:53AM +0900, Ryosuke Yasuoka wrote:
> Som
From: Dmitry Baryshkov
HDMI standard defines recommended N and CTS values for Audio Clock
Regeneration. Currently each driver implements those, frequently in
somewhat unique way. Provide a generic helper for getting those values
to be used by the HDMI drivers.
The helper is added to drm_hdmi_hel
From: Dmitry Baryshkov
Use drm_hdmi_acr_get_n_cts() helper instead of calculating N and CTS
values in the DW-HDMI driver.
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 90 +++
1 file changed, 8 insertions(+), 82 deletions(-)
diff -
From: Shixiong Ou
Call device_remove_file() when driver remove.
Signed-off-by: Shixiong Ou
---
v1->v2:
add has_sysfs_attrs flag.
drivers/video/fbdev/fsl-diu-fb.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/video/fbdev/fsl-diu-fb.c b/drivers/video/fbdev/fsl-diu-fb
On Sat, Mar 08, 2025 at 02:48:39PM +, Qasim Ijaz wrote:
> _dpu_encoder_trigger_start dereferences "struct dpu_encoder_phys *phys"
> before the sanity checks which can lead to a NULL pointer dereference if
> phys is NULL.
>
> Fix this by reordering the dereference after the sanity checks.
>
HDMI standards define a recommended set of values to be used for Audio
Clock Regeneration. Nevertheless, each HDMI driver dealing with audio
implements its own way to determine those values. Implement a common
helper and use it for MSM HDMI (tested), VC4 and DW-HDMI (compile-tested
only) drivers.
_dpu_encoder_trigger_start dereferences "struct dpu_encoder_phys *phys"
before the sanity checks which can lead to a NULL pointer dereference if
phys is NULL.
Fix this by reordering the dereference after the sanity checks.
Fixes: 8144d17a81d9 ("drm/msm/dpu: Skip trigger flush and start for CWB"
The `firmware` field of the `module!` only accepts literal strings,
which is due to the fact that it is implemented as a proc macro.
Some drivers require a lot of firmware files (such as nova-core) and
hence benefit from more flexibility composing firmware path strings.
The `firmware::ModInfoBuil
Hello fbdev maintainers/developers,
This is a 31-day syzbot report for the fbdev subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/fbdev
During the period, 1 new issues were detected and 0 were fixed.
In total, 7 issues are still open and 25 have
On 3/9/25 05:10, Michael Kelley wrote:
From: Helge Deller Sent: Saturday, March 8, 2025 6:59 PM
On 2/19/25 00:01, mhkelle...@gmail.com wrote:
From: Michael Kelley
[snip]
Reported-by: Thomas Tai
Fixes: c25a19afb81c ("fbdev/hyperv_fb: Do not clear global screen_info")
Signed-off-by: Mich
On 09. 03. 25, 16:48, Kuan-Wei Chiu wrote:
Would this work for everyone?
+1 for /me.
--
js
suse labs
On Thu, Mar 06, 2025 at 11:23:26PM +0100, Danilo Krummrich wrote:
> This is the initial series for the nova-core stub driver.
Applied to nova-next, thanks!
This is the same patch as before just updated to latest fbdev
master and with better description. And hopefully sent intact this
time.
Zsolt Kajtar (2):
Refactoring the fbcon packed pixel drawing routines
Adding contact info for packed pixel drawing
MAINTAINERS |
The original version duplicated more or less the same algorithms for
both system and i/o memory.
In this version the drawing algorithms (copy/fill/blit) are separate
from the memory access (system and i/o). The two parts are getting
combined in the loadable module sources. This also makes it more
Hi Dave, Simona,
Pull for v6.15, as described below.
The following changes since commit 72d0af4accd965dc32f504440d74d0a4d18bf781:
drm/msm/dp: Add support for LTTPR handling (2025-02-25 18:34:14 +0200)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/msm.git tags/d
On Fri, Mar 07, 2025 at 12:07:02PM -0800, H. Peter Anvin wrote:
> On March 7, 2025 11:53:10 AM PST, David Laight
> wrote:
> >On Fri, 07 Mar 2025 11:30:35 -0800
> >"H. Peter Anvin" wrote:
> >
> >> On March 7, 2025 10:49:56 AM PST, Andrew Cooper
> >> wrote:
> >> >> (int)true most definitely is g
On March 9, 2025 8:48:26 AM PDT, Kuan-Wei Chiu wrote:
>On Fri, Mar 07, 2025 at 12:07:02PM -0800, H. Peter Anvin wrote:
>> On March 7, 2025 11:53:10 AM PST, David Laight
>> wrote:
>> >On Fri, 07 Mar 2025 11:30:35 -0800
>> >"H. Peter Anvin" wrote:
>> >
>> >> On March 7, 2025 10:49:56 AM PST, Andr
On Sun, Mar 09, 2025 at 09:55:25AM +, Qasim Ijaz wrote:
> _dpu_encoder_trigger_start dereferences "struct dpu_encoder_phys *phys"
> before the sanity checks which can lead to a NULL pointer dereference if
> phys is NULL.
>
> Fix this by reordering the dereference after the sanity checks.
>
On Sun, 9 Mar 2025 01:58:53 +
David Laight wrote:
> On Fri, 7 Mar 2025 18:58:08 +0900
> Vincent Mailhol wrote:
>
> > On 07/03/2025 at 04:23, David Laight wrote:
> > > On Thu, 06 Mar 2025 20:29:52 +0900
> > > Vincent Mailhol via B4 Relay
> > > wrote:
> > >
> > >> From: Vincent Mailh
From: Dmitry Baryshkov
Use drm_hdmi_acr_get_n_cts() helper instead of calculating N and CTS
values in the VC4 driver.
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/vc4/vc4_hdmi.c | 10 +++---
drivers/gpu/drm/vc4/vc4_hdmi.h | 7 +++
2 files changed, 10 insertions(+), 7 deletions(
From: Dmitry Baryshkov
Use new drm_hdmi_acr_get_n_cts() helper instead of hand-coding the
tables. Instead of storing the rate 'index', store the audio sample rate
in hdmi->audio.rate, removing the need for even more defines.
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/msm/hdmi/hdmi_aud
…
> Fix this by reordering the dereference after the sanity checks.
Another wording suggestion:
Thus move the assignment of the variable “dpu_enc” behind a null pointer check.
Would an other summary phrase be nicer?
Regards,
Markus
On 3/6/25 9:03 PM, Anusha Srivatsa wrote:
> On Thu, Mar 6, 2025 at 11:29 AM Dmitry Baryshkov <
> dmitry.barysh...@linaro.org> wrote:
>
>> On Thu, 6 Mar 2025 at 17:10, Anusha Srivatsa wrote:
>>>
>>>
>>>
>>> On Thu, Mar 6, 2025 at 4:31 AM Maxime Ripard wrote:
Hi Anusha,
On W
From: "Dr. David Alan Gilbert"
The pcf50633 was used as part of the OpenMoko devices but
the support for its main chip was recently removed in:
commit 61b7f8920b17 ("ARM: s3c: remove all s3c24xx support")
See https://lore.kernel.org/all/Z8z236h4B5A6Ki3D@gallifrey/
Remove it.
Signed-off-by: Dr.
From: "Dr. David Alan Gilbert"
The pcf50633 was used as part of the OpenMoko devices but
the support for its main chip was recently removed in:
commit 61b7f8920b17 ("ARM: s3c: remove all s3c24xx support")
See https://lore.kernel.org/all/Z8z236h4B5A6Ki3D@gallifrey/
Remove it.
Signed-off-by: Dr.
From: "Dr. David Alan Gilbert"
Remove the remaining parts of the 50633, the core, headers and glue.
The pcf50633 was used as part of the OpenMoko devices but
the support for its main chip was recently removed in:
commit 61b7f8920b17 ("ARM: s3c: remove all s3c24xx support")
See https://lore.kern
From: "Dr. David Alan Gilbert"
As part of the pcf50633 removal, take out it's irq code
(which includes one bit still called from the core, but it'll
go soon).
Signed-off-by: Dr. David Alan Gilbert
---
drivers/mfd/Makefile| 2 +-
drivers/mfd/pcf50633-core.c | 5 +-
drivers/mfd/pcf50
From: "Dr. David Alan Gilbert"
The pcf50633 was used as part of the OpenMoko devices but
the support for its main chip was recently removed in:
commit 61b7f8920b17 ("ARM: s3c: remove all s3c24xx support")
See https://lore.kernel.org/all/Z8z236h4B5A6Ki3D@gallifrey/
Remove it.
I've split this up
From: "Dr. David Alan Gilbert"
The pcf50633 was used as part of the OpenMoko devices but
the support for its main chip was recently removed in:
commit 61b7f8920b17 ("ARM: s3c: remove all s3c24xx support")
See https://lore.kernel.org/all/Z8z236h4B5A6Ki3D@gallifrey/
Remove it.
Signed-off-by: Dr.
From: "Dr. David Alan Gilbert"
The pcf50633 was used as part of the OpenMoko devices but
the support for its main chip was recently removed in:
commit 61b7f8920b17 ("ARM: s3c: remove all s3c24xx support")
See https://lore.kernel.org/all/Z8z236h4B5A6Ki3D@gallifrey/
Remove it.
Signed-off-by: Dr.
On 3/9/25 09:16, Shixiong Ou wrote:
From: Shixiong Ou
Call device_remove_file() when driver remove.
Signed-off-by: Shixiong Ou
---
v1->v2:
add has_sysfs_attrs flag.
drivers/video/fbdev/fsl-diu-fb.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/video/fbdev/fsl-d
Hi Charles,
On 05/03/25 07:21, Charles Han wrote:
Fix below inconsistent indenting smatch warning.
smatch warnings:
drivers/gpu/drm/vc4/vc4_plane.c:2083 vc6_plane_mode_set() warn: inconsistent
indenting
Signed-off-by: Charles Han
Applied to misc/kernel.git (drm-misc-next).
Best Regards,
-
On Mon, Mar 3, 2025 at 9:45 AM Alice Ryhl wrote:
>
> Rust has two different tools for generating function declarations to
> call across the FFI boundary:
>
> * bindgen. Generates Rust declarations from a C header.
> * cbindgen. Generates C headers from Rust declarations.
>
> However, we only use b
From: "Dr. David Alan Gilbert"
The pcf50633 was used as part of the OpenMoko devices but
the support for its main chip was recently removed in:
commit 61b7f8920b17 ("ARM: s3c: remove all s3c24xx support")
See https://lore.kernel.org/all/Z8z236h4B5A6Ki3D@gallifrey/
Remove it.
Signed-off-by: Dr.
> Wiadomość napisana przez Andy Yan w dniu 7 mar 2025, o
> godz. 01:48:
>
>
> Hi Piotr,
> 在 2025-03-06 22:28:08，"Piotr Oniszczuk" 写道：
>>
>>
>
> All dump information currently appears to be correct, so I'm temporarily
> unsure why
> there is no display on the monitor.
> Maybe try some pl
From: Baihan Li
To realize HPD feature, request irq for HPD , add its handler function.
We use pci_alloc_irq_vectors() to get our msi irq, because we have two
interrupts now.
Signed-off-by: Baihan Li
Signed-off-by: Yongbang Shi
Reviewed-by: Dmitry Baryshkov
---
ChangeLog:
v4 -> v5:
- remove
From: Baihan Li
Add registering drm_aux and use it to get connector edid with drm
functions. Add ddc channel in connector initialization to put drm_aux
in drm_connector.
Signed-off-by: Baihan Li
Signed-off-by: Yongbang Shi
Reviewed-by: Dmitry Baryshkov
---
ChangeLog:
v5 -> v6:
- move the de
From: Baihan Li
Add HPD interrupt enable functions in drm framework, and also add
detect_ctx functions. Because of the debouncing when HPD pulled out,
add 200 ms delay in detect_ctx(). Add link reset process to reset link
status when a new connector pulgged in.
Signed-off-by: Baihan Li
Signed-o
From: Baihan Li
Because the drm_aux of struct hibmc_dp_dev's member is not easy to get in
hibmc_drm_dp.c, move the drm_aux to struct hibmc_dp. Then there are some
adaptations and modifications to make this patch compile.
Signed-off-by: Baihan Li
Signed-off-by: Yongbang Shi
Reviewed-by: Dmitry
From: Baihan Li
Because the connected VGA connector would make driver can't get the
userspace call, adding detect_ctx in vga connector to make HPD active
userspace.
Signed-off-by: Baihan Li
Signed-off-by: Yongbang Shi
Reviewed-by: Dmitry Baryshkov
---
drivers/gpu/drm/hisilicon/hibmc/hibmc_dr
From: Baihan Li
To support DP HPD, edid printing, and colorbar display features based on
the Hisislcon DP devices.
---
ChangeLog:
v5 -> v6:
- fix the DP_SERDES_VOL2_PRE0 value after electrical test.
- move the detect_ctx() to the patch 7/9.
- add detect_ctx with 200ms delay, suggested by Dm
From: Baihan Li
Move the macros below their corresponding registers to make
them more obvious.
Signed-off-by: Baihan Li
Signed-off-by: Yongbang Shi
Reviewed-by: Dmitry Baryshkov
---
ChangeLog:
v2 -> v3:
- restructuring the header dp_reg.h, suggested by Dmitry Baryshkov.
---
drivers/gpu/drm
From: "Dr. David Alan Gilbert"
The pcf50633 was used as part of the OpenMoko devices but
the support for its main chip was recently removed in:
commit 61b7f8920b17 ("ARM: s3c: remove all s3c24xx support")
See https://lore.kernel.org/all/Z8z236h4B5A6Ki3D@gallifrey/
Remove it.
Signed-off-by: Dr.
Hi Dmitry,
kernel test robot noticed the following build errors:
[auto build test ERROR on 0a2f889128969dab41861b6e40111aa03dc57014]
url:
https://github.com/intel-lab-lkp/linux/commits/Dmitry-Baryshkov/drm-display-hdmi-provide-central-data-authority-for-ACR-params/20250309-161610
base
From: Dmitry Baryshkov
In case of ACTIVE CTLs, a single CTL is being used for flushing all INTF
blocks. Don't skip programming the CTL on those targets.
Tested-by: Neil Armstrong # on SM8550-QRD
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder_phys_vid.c | 3 ++-
Hi,
On 3/6/25 06:42, Balbir Singh wrote:
> When a zone device page is split (via huge pmd folio split). The
> driver callback for folio_split is invoked to let the device driver
> know that the folio size has been split into a smaller order.
>
> The HMM test driver has been updated to handle the s
Hi Dmitry,
kernel test robot noticed the following build errors:
[auto build test ERROR on 0a2f889128969dab41861b6e40111aa03dc57014]
url:
https://github.com/intel-lab-lkp/linux/commits/Dmitry-Baryshkov/drm-display-hdmi-provide-central-data-authority-for-ACR-params/20250309-161610
base
From: Shixiong Ou
Call device_remove_file() when driver remove.
Signed-off-by: Shixiong Ou
---
v1->v2:
add has_dev_attrs flag.
v2->v3:
drop those extra checks.
drivers/video/fbdev/fsl-diu-fb.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/video/fbdev/fsl-diu-fb.c
The description for CONFIG_LCD_TDO24M has redundant whitespace.
Trim it to keep the code tidy.
Signed-off-by: WangYuli
---
drivers/video/backlight/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/video/backlight/Kconfig b/drivers/video/backlight/Kconfig
index 3
On Mon, Feb 10, 2025 at 11:34:41AM -0800, mhkelle...@gmail.com wrote:
> From: Michael Kelley
>
> When a Hyper-V DRM device is probed, the driver allocates MMIO space for
> the vram, and maps it cacheable. If the device removed, or in the error
> path for device probing, the MMIO space is released
On Tue, Feb 18, 2025 at 03:01:30PM -0800, mhkelle...@gmail.com wrote:
> From: Michael Kelley
>
> Gen 2 Hyper-V VMs boot via EFI and have a standard EFI framebuffer
> device. When the kdump kernel runs in such a VM, loading the efifb
> driver may hang because of accessing the framebuffer at the wr
On Sun, Mar 09, 2025 at 03:20:04PM +0100, Helge Deller wrote:
> On 3/9/25 05:10, Michael Kelley wrote:
> > From: Helge Deller Sent: Saturday, March 8, 2025 6:59 PM
> > >
> > > On 2/19/25 00:01, mhkelle...@gmail.com wrote:
> > > > From: Michael Kelley
> > > >
> > [snip]
> >
> > > >
> > > > Rep
On Sat, Mar 01, 2025 at 08:16:29AM -0800, Saurabh Sengar wrote:
> This patch series addresses an issue in the unbind path of the hyperv_fb
> driver, which is resolved in the second patch of this series.
>
> While working on this fix, it was observed that hvfb_putmem() and its
> child functions cou
Hi Zsolt,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.14-rc5 next-20250307]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
From: "Dr. David Alan Gilbert"
The pcf50633 was used as part of the OpenMoko devices but
the support for its main chip was recently removed in:
commit 61b7f8920b17 ("ARM: s3c: remove all s3c24xx support")
See https://lore.kernel.org/all/Z8z236h4B5A6Ki3D@gallifrey/
Remove it.
Signed-off-by: Dr.
Hi Dave and Sima,
This is the inital PR for Nova (nova-core).
Besides the nova-core skeleton driver and the initial project documentation,
I picked up two firmware patches and one Rust patch (no conflicts expected) as
dependency of nova-core.
The following changes since commit 7eb172143d5508b4da
56 matches
Mail list logo
