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, 6 issues are still open and 25 have
On Wed, Feb 05, 2025 at 11:10:54PM +0100, Sasha Finkelstein via B4 Relay wrote:
> From: Sasha Finkelstein
>
> Add the MAINTAINERS entries for the driver
>
> Acked-by: Sven Peter
> Signed-off-by: Sasha Finkelstein
> ---
> MAINTAINERS | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git
On Thu, Feb 06, 2025 at 10:24:43AM +0100, Sasha Finkelstein wrote:
> On Thu, 6 Feb 2025 at 10:17, Maxime Ripard wrote:
> > Sorry to figure it out that late, but how do you plan on maintaining it?
> > Where will the patches go through, and who will you send PR to?
>
> Downstream development is don
Hi,
I want to second what Jocelyn said.
Am 05.02.25 um 23:28 schrieb Gwenael Georgeault:
- Added the new device ID
- Added new pll algorithm
Co-authored-by: Mamadou Insa Diop
---
drivers/gpu/drm/mgag200/Makefile | 1 +
drivers/gpu/drm/mgag200/mgag200_drv.c | 4 +
drivers/gp
On Tue, 04 Feb 2025 14:40:03 +0200, Cristian Ciocaltea wrote:
> VOP2 support for RK3588 SoC is currently not capable to handle the full
> range of display modes advertised by the connected screens, e.g. it
> doesn't cope well with non-integer refresh rates like 59.94, 29.97,
> 23.98, etc.
>
> Th
> The filemap_lock_folio() function doesn't return NULL, it returns error
> pointers.
>
> Fixes: 25dd342f0cc8 ("drm/i915/gem: convert __shmem_writeback() to folios")
> Signed-off-by: Dan Carpenter
...
> struct folio *folio;
>
> folio = filemap_lock_folio(mapping, i
On Mon, 2025-02-03 at 15:30 +, Tvrtko Ursulin wrote:
> Implement a mock scheduler backend and add some basic test to
> exercise the
> core scheduler code paths.
>
> Mock backend (kind of like a very simple mock GPU) can either process
> jobs
> by tests manually advancing the "timeline" job at
On Thu, 6 Feb 2025 at 10:17, Maxime Ripard wrote:
> Sorry to figure it out that late, but how do you plan on maintaining it?
> Where will the patches go through, and who will you send PR to?
Downstream development is done via the https://github.com/AsahiLinux/linux/
repo, then send patches to ml.
On 2025/02/06 5:36, Dave Airlie wrote:
> On Thu, 6 Feb 2025 at 04:52, Simona Vetter wrote:
>>
>> On Tue, Feb 04, 2025 at 03:46:14AM +0900, Hector Martin wrote:
>>> Adding Linus
>>>
>>> My 2c: If Linus doesn't pipe up with an authoritative answer to this
>>> thread, Miguel and the other Rust folks
On Mon, 2025-02-03 at 15:30 +, Tvrtko Ursulin wrote:
> There has repeatedly been quite a bit of apprehension when any change
> to the DRM
> scheduler is proposed, with two main reasons being code base is
> considered
> fragile, not well understood and not very well documented, and
> secondly th
On Thu, 06 Feb 2025 11:03:28 +0800, Damon Ding wrote:
> Picked from:
> https://patchwork.kernel.org/project/linux-rockchip/list/?series=927102
>
> The hdptxphy is a combo transmit-PHY for HDMI2.1 TMDS Link, FRL Link, DP
> and eDP Link. Therefore, it is better to name it hdptxphy0 other than
> hd
On 2025/2/4 18:45, Simona Vetter wrote:
On Mon, Jan 20, 2025 at 05:54:10PM +0800, Huang, Honglei1 wrote:
On 2024/12/27 10:02, Huang, Honglei1 wrote:
On 2024/12/22 9:59, Demi Marie Obenour wrote:
On 12/20/24 10:35 AM, Simona Vetter wrote:
On Fri, Dec 20, 2024 at 06:04:09PM +0800, Honglei Huang
On Thu, 06 Feb 2025 11:03:28 +0800, Damon Ding wrote:
> Picked from:
> https://patchwork.kernel.org/project/linux-rockchip/list/?series=927102
>
> The hdptxphy is a combo transmit-PHY for HDMI2.1 TMDS Link, FRL Link, DP
> and eDP Link. Therefore, it is better to name it hdptxphy0 other than
> hd
Thanks a lot for this rework.
When sending a new version of your patch, you can use "git send-email
-v2" to show that it's the second version of this patch.
On 05/02/2025 23:28, Gwenael Georgeault wrote:
- Added the new device ID
- Added new pll algorithm
Co-authored-by: Mamadou Insa Diop
On Fri, 10 Jan 2025 14:31:10 +0100, amerg...@baylibre.com wrote:
> The purpose of this series is to add the display support for the mt8365-evk.
>
> This is the list of HWs / IPs support added:
> - Connectors (HW):
> - HDMI
> - MIPI DSI (Mobile Industry Processor Interface Display Serial Interf
On Tue, 04 Feb 2025 14:40:03 +0200, Cristian Ciocaltea wrote:
> VOP2 support for RK3588 SoC is currently not capable to handle the full
> range of display modes advertised by the connected screens, e.g. it
> doesn't cope well with non-integer refresh rates like 59.94, 29.97,
> 23.98, etc.
>
> Th
The filemap_lock_folio() function doesn't return NULL, it returns error
pointers.
Fixes: 25dd342f0cc8 ("drm/i915/gem: convert __shmem_writeback() to folios")
Signed-off-by: Dan Carpenter
---
drivers/gpu/drm/i915/gem/i915_gem_shmem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --g
In J721s2 EVM, DP0 HPD is not connected to correct HPD pin on SOC
which results in HPD detect as always connnected, so when display
is not connected driver continuously retries to read EDID and DPCD
registers.
To handle such cases add support for no hpd configuration in
cdns-mhdp driver.
Changelo
From: Rahul T R
In J721S2 EVMs DP0 hpd is not connected to correct hpd pin on SOC, to
handle such cases, Add support for "no-hpd" property in the device
tree node to disable hpd.
Also change the log level for dpcd read failuers to debug, since
framework retries 32 times for each read.
Adding
Dear Community,
> Dear Community,
>
> > This patch provides the DT Schema description of:
> > - powertip,st7272 320 x 240 LCD display
> > - powertip,hx8238a 320 x 240 LCD display
> >
> > Used with the different HW revisions of btt3 devices.
> >
>
> Gentle ping on this window... I hope that
From: Yicong Yang
DP stuffs of hibmc are using DRM DP helpers, select the Kconfig for
dependency. Otherwise with below configuration:
CONFIG_DRM_DISPLAY_HELPER=m
CONFIG_DRM_HISI_HIBMC=y
Below link error is met:
ld: Unexpected GOT/PLT entries detected!
ld: Unexpected run-time procedure linkages d
- Added the new device ID
- Added new pll algorithm
Co-authored-by: Mamadou Insa Diop
---
drivers/gpu/drm/mgag200/Makefile | 1 +
drivers/gpu/drm/mgag200/mgag200_drv.c | 4 +
drivers/gpu/drm/mgag200/mgag200_drv.h | 3 +
drivers/gpu/drm/mgag200/mgag200_g200eh5.c | 202
From: Rahul T R
The mhdp bridge can work without its HPD pin hooked up to the connector,
but the current bridge driver throws an error when hpd line is not
connected to the connector. For such cases, we need an indication for
no-hpd, using which we can bypass the hpd detection and instead use the
Hi,
I got the compile error as below.
My GCC is: gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
kernel: v6.14-rc1
--- compile error log ---
CC drivers/gpu/drm/i915/display/intel_dp.o
In file included from :0:0:
In function ‘intel_dp_dsc_compute_pipe_bpp_limits.isra.77’,
inlined from ‘intel_d
Hi,
I'm using the 6.1 kernel for the imx8mm board in combination with the
lt8912 driver to have hdmi output available. When plugged full-hd monitor
image is displayed but when plugged an older monitor with max
resolution 1024x768 there is no image displayed on it. I have no clue
where to start loo
Add Matthew Auld and Matthew Brost as TTM reviewers
Cc: Matthew Auld
Cc: Matthew Brost
Cc: Christian König
Cc: Dave Airlie
Cc: Simona Vetter
Cc: dri-devel@lists.freedesktop.org
Cc: linux-ker...@vger.kernel.org
Signed-off-by: Thomas Hellström
Reviewed-by: Christian König
---
MAINTAINERS | 2
On 2025/2/3 16:25, Akihiko Odaki wrote:
On 2024/12/20 19:04, Honglei Huang wrote:
From: Honglei Huang
Add a new resource for blob resource, called userptr, used for let
host access guest user space memory, to acquire a simple SVM features
in virtio GPU.
- The capset VIRTIO_GPU_CAPSET_HSAKMT u
On 06/02/2025 09:51, Philipp Stanner wrote:
On Mon, 2025-02-03 at 15:30 +, Tvrtko Ursulin wrote:
Implement a mock scheduler backend and add some basic test to
exercise the
core scheduler code paths.
Mock backend (kind of like a very simple mock GPU) can either process
jobs
by tests manual
Virtio gpu supports the drm_panic module, which displays a message to
the screen when a kernel panic occurs. It is supported where it has
vmapped shmem BO.
Signed-off-by: Jocelyn Falempe
Signed-off-by: Ryosuke Yasuoka
---
v7:
- Reject no vmapped shmem BO. Also, insert comment and commit log abou
On 2025/1/31 8:33, Demi Marie Obenour wrote:
On Wed, Jan 29, 2025 at 03:54:59PM -0500, Demi Marie Obenour wrote:
On 1/8/25 12:05 PM, Simona Vetter wrote:
On Fri, Dec 27, 2024 at 10:24:29AM +0800, Huang, Honglei1 wrote:
On 2024/12/22 9:59, Demi Marie Obenour wrote:
On 12/20/24 10:35 AM, Simon
On 06/02/2025 06:45, Matthew Brost wrote:
On Wed, Feb 05, 2025 at 01:44:48PM +0100, Christian König wrote:
Am 05.02.25 um 12:14 schrieb Tvrtko Ursulin:
Christian suggests scheduler should not use the term TDR because it only
can do basic timeout detection on it's own, not the full blown timeo
https://bugzilla.kernel.org/show_bug.cgi?id=219754
Bug ID: 219754
Summary: When screen blanks and resumes there will be an error:
kernel: amdgpu :0b:00.0: [drm] REG_WAIT timeout
1us * 100 tries - dcn32_program_compbuf_size line:138
On 06/02/2025 10:35, Thomas Hellström wrote:
Add Matthew Auld and Matthew Brost as TTM reviewers
Cc: Matthew Auld
Cc: Matthew Brost
Cc: Christian König
Cc: Dave Airlie
Cc: Simona Vetter
Cc: dri-devel@lists.freedesktop.org
Cc: linux-ker...@vger.kernel.org
Signed-off-by: Thomas Hellström
Rev
Use %ptTs instead of open-coded variant to print contents of time64_t type
in human readable form.
Signed-off-by: Andy Shevchenko
---
v2: fixed the parameters to be the pointers
drivers/accel/habanalabs/common/device.c | 25 +++-
1 file changed, 3 insertions(+), 22 deletion
Hi,
On Thu, Feb 6, 2025 at 10:13 AM Conor Dooley wrote:
>
> On Thu, Feb 06, 2025 at 09:12:45AM -0800, Doug Anderson wrote:
> > Hi,
> >
> > On Thu, Feb 6, 2025 at 5:13 AM Langyan Ye
> > wrote:
> > >
> > > Add "csot" to the Devicetree Vendor Prefix Registry.
> > >
> > > Signed-off-by: Langyan Ye
From: Michael Kelley
>
> From: Thomas Tai Sent: Thursday, January 30, 2025
> 12:44 PM
> >
> > > -Original Message-
> > > From: Michael Kelley Sent: Thursday, January 30,
> > > 2025 3:20 PM
> > >
> > > From: Thomas Tai Sent: Thursday, January 30,
> > > 2025 10:50 AM
> > > >
> > > > So
Use mipi_dsi_dcs_write_seq_multi() instead of
mipi_dsi_dcs_write_seq()
Used Coccinelle to do this change. SmPl patch:
@rule_1@
identifier dsi_var;
expression dsi_device;
expression list es;
@@
struct mipi_dsi_device *dsi_var = dsi_device;
+struct mipi_dsi_multi_context dsi_ctx = { .dsi = dsi_var }
Use mipi_dsi_generic_write_seq_multi() instead of
mipi_dsi_generic_write_seq()
Used Coccinelle to do this change. SmPl patch:
@rule_2@
expression dsi_var;
expression list es;
identifier jdi;
@@
static int jdi_write_dcdc_registers(struct jdi_panel *jdi)
{
+struct mipi_dsi_multi_context dsi_ctx1 =
5 files changed, 1244 insertions(+), 1291 deletions(-)
---
base-commit: 92514ef226f511f2ca1fb1b8752966097518edc0
change-id: 20250206-mipi-cocci-8c356b1ae765
Best regards,
--
Anusha Srivatsa
Use mipi_dsi_dcs_write_seq_multi() instead of
mipi_dsi_dcs_write_seq()
Used Coccinelle to do this change. SmPl patch:
@rule_1@
identifier dsi_var;
expression dsi_device;
expression list es;
@@
struct mipi_dsi_device *dsi_var = dsi_device;
+struct mipi_dsi_multi_context dsi_ctx = { .dsi = dsi_var }
Use mipi_dsi_dcs_write_seq_multi() instead of
mipi_dsi_dcs_write_seq()
Used Coccinelle to do this change. SmPl patch:
@rule_1@
identifier dsi_var;
expression dsi_device;
expression list es;
@@
struct mipi_dsi_device *dsi_var = dsi_device;
+struct mipi_dsi_multi_context dsi_ctx = { .dsi = dsi_var }
Use mipi_dsi_dcs_write_seq_multi() instead of
mipi_dsi_dcs_write_seq()
While at it, also change mipi_dsi_dual_dcs_write_seq()
accordingly.
Used Coccinelle to do this change. SmPl patch:
@rule_1@
identifier dsi_var;
expression dsi_device;
expression list es;
@@
struct mipi_dsi_device *dsi_var = ds
With transition to newer functions, remove
older ones that are no longer used.
Signed-off-by: Anusha Srivatsa
---
drivers/gpu/drm/drm_mipi_dsi.c | 56 --
include/drm/drm_mipi_dsi.h | 47 ---
2 files changed, 103 deletion
Use mipi_dsi_dcs_write_seq_multi() instead of
mipi_dsi_dcs_write_seq()
Used Coccinelle to do this change. SmPl patch:
@rule_1@
identifier dsi_var;
expression dsi_device;
expression list es;
@@
struct mipi_dsi_device *dsi_var = dsi_device;
+struct mipi_dsi_multi_context dsi_ctx = { .dsi = dsi_var }
TODO addressed
Cc: Douglas Anderson
Signed-off-by: Anusha Srivatsa
---
Documentation/gpu/todo.rst | 19 ---
1 file changed, 19 deletions(-)
diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst
index
256d0d1cb2164bd94f9b610a751b907834d96a21..16231355b3bd31e50c9b
Use mipi_dsi_dcs_write_seq_multi() instead of
mipi_dsi_dcs_write_seq()
Used Coccinelle to do this change. SmPl patch:
@rule_1@
identifier dsi_var;
expression dsi_device;
expression list es;
@@
struct mipi_dsi_device *dsi_var = dsi_device;
+struct mipi_dsi_multi_context dsi_ctx = { .dsi = dsi_var }
Use mipi_dsi_dcs_write_seq_multi() instead of
mipi_dsi_dcs_write_seq()
Used Coccinelle to do this change. SmPl patch:
@rule_1@
identifier dsi_var;
expression dsi_device;
expression list es;
@@
struct mipi_dsi_device *dsi_var = dsi_device;
+struct mipi_dsi_multi_context dsi_ctx = { .dsi = dsi_var }
Use mipi_dsi_dcs_write_seq_multi() instead of
mipi_dsi_dcs_write_seq()
Used Coccinelle patch to do this change:
@rule_1@
identifier dsi_var;
expression dsi_device;
expression list es;
@@
struct mipi_dsi_device *dsi_var = dsi_device;
+struct mipi_dsi_multi_context dsi_ctx = { .dsi = dsi_var };
<+..
Use mipi_dsi_dcs_write_seq_multi() instead of
mipi_dsi_dcs_write_seq()
Used Coccinelle to do this change. SmPl patch:
@rule_1@
identifier dsi_var;
expression dsi_device;
expression list es;
@@
struct mipi_dsi_device *dsi_var = dsi_device;
+struct mipi_dsi_multi_context dsi_ctx = { .dsi = dsi_var }
Use mipi_dsi_dcs_write_seq_multi() instead of
mipi_dsi_dcs_write_seq()
Used Coccinelle to make the change. SmPl patch:
@rule_1@
identifier dsi_var;
expression dsi_device;
expression list es;
@@
struct mipi_dsi_device *dsi_var = dsi_device;
+struct mipi_dsi_multi_context dsi_ctx = { .dsi = dsi_var
Use mipi_dsi_dcs_write_seq_multi() instead of
mipi_dsi_dcs_write_seq()
Used Coccinelle to do this change. SmPl patch:
@rule_1@
identifier dsi_var;
expression dsi_device;
expression list es;
@@
struct mipi_dsi_device *dsi_var = dsi_device;
+struct mipi_dsi_multi_context dsi_ctx = { .dsi = dsi_var }
Reviewed-by: Lyude Paul
On Thu, 2025-02-06 at 18:38 +0100, Greg Kroah-Hartman wrote:
> The vgem driver does not need to create a platform device, as there is
> no real platform resources associated it, it only did so because it was
> simple to do that in order to get a device to use for resource
Lol, I wrote up a patch for this last night but it looks like you got here
first :P
On Thu, 2025-02-06 at 18:38 +0100, Greg Kroah-Hartman wrote:
> The vkms driver does not need to create a platform device, as there is
> no real platform resources associated it, it only did so because it was
> sim
Convert most mutex_(un)lock calls to use (scoped_)guard instead. This
generally reduces line count and prevents bugs like forgetting to unlock
the mutex. I've left traditional calls in a few places where scoped
helpers would be more verbose. This mostly happens where
debugfs_file_put needs to be ca
From: Bart Van Assche
Instead of attempting the same mutex twice, lock and unlock it.
This bug has been detected by the Clang thread-safety analyzer.
Cc: Sean Anderson
Cc: Tomi Valkeinen
Fixes: 28edaacb821c ("drm: zynqmp_dp: Add debugfs interface for compliance
testing")
Signed-off-by: Bart
On Thu, Feb 06, 2025 at 06:19:42PM +0900, Hector Martin wrote:
>
> If shaming on social media does not work, then tell me what does,
Most importantly be *consistent* with good technical arguments, calmly focus on
your actual matter rather than escalating any surrounding details.
Accept that some
Widebus allows the DP controller to operate in 2 pixel per clock mode.
The mode validation logic validates the mode->clock against the max
DP pixel clock. However the max DP pixel clock limit assumes widebus
is already enabled. Adjust the mode validation logic to only compare
the adjusted pixel clo
Hi Tomi,
On 1/15/25 04:03, Tomi Valkeinen wrote:
> Fix "mapping sg segment longer than device claims to support" warning by
> setting the max segment size.
>
> Fixes: d76271d22694 ("drm: xlnx: DRM/KMS driver for Xilinx ZynqMP DisplayPort
> Subsystem")
> Reviewed-by: Sean Anderson
> Tested-by: S
Fix a mutex bug and convert most of the explicit mutex_(un)locks to
guards.
Bart Van Assche (1):
drm: zynqmp_dp: Fix a deadlock in zynqmp_dp_ignore_hpd_set()
Sean Anderson (1):
drm: zynqmp_dp: Use scope-based mutex helpers
drivers/gpu/drm/xlnx/zynqmp_dp.c | 151
On 2025/02/07 4:37, Danilo Krummrich wrote:
> On Thu, Feb 06, 2025 at 06:19:42PM +0900, Hector Martin wrote:
>>
>> If shaming on social media does not work, then tell me what does,
>
> Most importantly be *consistent* with good technical arguments, calmly focus
> on
> your actual matter rather
Le mercredi 05 février 2025 à 10:13 +0100, Krzysztof Kozlowski a écrit :
> On 03/02/2025 16:31, Florent Tomasin wrote:
> > Hi Krzysztof
> >
> > On 30/01/2025 13:25, Krzysztof Kozlowski wrote:
> > > On 30/01/2025 14:08, Florent Tomasin wrote:
> > > > Allow mali-valhall-csf driver to retrieve a prot
On Thu, Feb 6, 2025 at 2:57 AM Thomas Zimmermann
wrote:
> Hi
>
>
> Am 05.02.25 um 21:08 schrieb Anusha Srivatsa:
> > Update the Documentation to be more precise.
> >
> > v2: Update for clarity
> >
> > Cc: Thomas Zimmermann
> > Signed-off-by: Anusha Srivatsa
> > ---
> > Documentation/gpu/todo.
Hi Krzysztof,
On Thu, Jan 30, 2025 at 09:19:31AM +, Krzysztof Karas wrote:
> There is an error path in igt_ppgtt_alloc(), which leads
> to ww object being passed down to i915_gem_ww_ctx_fini() without
> initialization. Correct that by only putting ppgtt->vm and
> returning early.
>
> Fixes: 4
Am 30.01.25 um 11:13 schrieb Thomas Hellström:
Use fault-injection to test partial TTM swapout and interrupted swapin.
Return -EINTR for swapin to test the callers ability to handle and
restart the swapin, and on swapout perform a partial swapout to test that
the swapin and release_shrunken funct
Hi Danilo,
Here are few comments - or maybe I should say nits, as they are really
minor. Note that all my experience in Rust is from user-space, so feel
free to ignore anything that does not make sense in the context of the
kernel or is too pedantic.
On Wed Feb 5, 2025 at 4:03 AM JST, Danilo Krum
From: Sasha Finkelstein
This is the display panel used for the touchbar on laptops that have it.
Co-developed-by: Nick Chan
Signed-off-by: Nick Chan
Reviewed-by: Dmitry Baryshkov
Reviewed-by: Neil Armstrong
Signed-off-by: Sasha Finkelstein
---
drivers/gpu/drm/panel/Kconfig| 9 +++
On 04.02.25 14:58, Alex Deucher wrote:
On Tue, Feb 4, 2025 at 8:37 AM Christian König wrote:
Hi Friedrich,
adding Alex.
Am 04.02.25 um 13:32 schrieb Friedrich Vock:
Hi,
Bumping this again - it's been quite a while, what became of that KFD
bugfix and the userqueue stuff? It'd be nice
The vkms driver does not need to create a platform device, as there is
no real platform resources associated it, it only did so because it was
simple to do that in order to get a device to use for resource
management of drm resources. Change the driver to use the faux device
instead as this is NO
The vgem driver does not need to create a platform device, as there is
no real platform resources associated it, it only did so because it was
simple to do that in order to get a device to use for resource
management of drm resources. Change the driver to use the faux device
instead as this is NO
On Sun, Feb 02, 2025 at 12:08:46AM -0500, Demi Marie Obenour wrote:
> Cc:
> Bcc:
> Subject: Xen requirements for GPU virtualization via virtio-GPU
> Reply-To:
> X-Mutt-Fcc: =INBOX,=xen-devel,=Sent
> X-Mutt-PGP: S
>
> Recently, AMD submitted patches to the dri-devel mailing list to support
> usi
On Thu, 2025-02-06 at 10:42 +, Tvrtko Ursulin wrote:
>
> On 06/02/2025 09:51, Philipp Stanner wrote:
> > On Mon, 2025-02-03 at 15:30 +, Tvrtko Ursulin wrote:
> > > Implement a mock scheduler backend and add some basic test to
> > > exercise the
> > > core scheduler code paths.
> > >
> > >
Hi,
Am Montag, 3. Februar 2025, 17:16:06 CET schrieb Herve Codina:
> In some cases observed during ESD tests, the TI SN65DSI83 cannot recover
> from errors by itself. A full restart of the bridge is needed in those
> cases to have the bridge output LVDS signals again.
>
> Also, during tests, case
Acked-by: Maarten Lankhorst
for both
On 2025-02-06 07:45, Kandpal, Suraj wrote:
-Original Message-
From: Murthy, Arun R
Sent: Thursday, February 6, 2025 12:13 PM
To: Kandpal, Suraj ; intel...@lists.freedesktop.org;
intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org
Cc
On Thu, 6 Feb 2025 15:17:13 +0800, oushixiong1...@163.com wrote:
> From: Shixiong Ou
>
> convert to use devm_platform_ioremap_resource().
>
> Signed-off-by: Shixiong Ou
>
> [ ... ]
Reviewed-by: Maxime Ripard
Thanks!
Maxime
Hi Alexandre,
On Thu, Feb 06, 2025 at 11:05:37PM +0900, Alexandre Courbot wrote:
> > +
> > +/// Enum representation of the GPU chipset.
> > +#[derive(fmt::Debug)]
>
> I suspect you will eventually want to also derive Copy and Clone, as
> well as PartialEq and Eq (so the assigned values can be use
On Thu, 6 Feb 2025 at 01:19, Hector Martin wrote:
>
> If shaming on social media does not work, then tell me what does,
> because I'm out of ideas.
How about you accept the fact that maybe the problem is you.
You think you know better. But the current process works.
It has problems, but problem
https://bugzilla.kernel.org/show_bug.cgi?id=219754
Artem S. Tashkinov (a...@gmx.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
We return immediately from i915_driver_register() if drm_dev_register()
fails, skipping remaining registration steps. However, the _unregister()
counterpart called at device remove knows nothing about that skip and
executes reverts for all those steps. For that to work correctly, those
revert fun
We return immediately from i915_driver_register() if drm_dev_register()
fails, skipping remaining registration steps. However, the _unregister()
counterpart called at device remove knows nothing about that skip and
executes reverts for all those steps. For that to work correctly, those
revert fun
We return immediately from i915_driver_register() if drm_dev_register()
fails, skipping remaining registration steps. However, the _unregister()
counterpart called at device remove knows nothing about that skip and
executes reverts for all those steps. For that to work correctly, those
revert fun
This comment is misleading as it refers to one of the inner if() branches
only, not the whole outer if(). Move it to the branch it refers to.
Signed-off-by: Luca Ceresoli
---
This patch was added in v6.
---
drivers/gpu/drm/drm_of.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --
Hello,
this series aims at supporting Linux devices with a DRM pipeline whose
final components can be hot-plugged and hot-unplugged, including one or
more bridges.
Use case and overall description
If you don't know the topic, see cover letter for v5:
https://lore
On Thu, Feb 06, 2025 at 09:12:45AM -0800, Doug Anderson wrote:
> Hi,
>
> On Thu, Feb 6, 2025 at 5:13 AM Langyan Ye
> wrote:
> >
> > Add "csot" to the Devicetree Vendor Prefix Registry.
> >
> > Signed-off-by: Langyan Ye
> > ---
> > Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
>
On Thu, Feb 06, 2025 at 09:12:59PM +0800, Langyan Ye wrote:
> Add a new compatible for the panel CSOT PNA957QT1-1. This panel uses
> HX83102 IC, so add the compatible to the hx83102 binding files.
>
> Signed-off-by: Langyan Ye
Acked-by: Conor Dooley
signature.asc
Description: PGP signature
In preparation to let panels always create a panel bridge, we need the
drm_panel.c code to call bridge/panel.c code. However this would create a
cyclic dependency between .c files and between modules (drm ->
drm_kms_helper -> drm), indeed now the two components would depend on each
other.
In the s
Having an DRM_MODE_CONNECTOR_Unknown connector type is consuidered bad, and
drm_panel_bridge_add_typed() and derivatives are deprecated for this.
drm_panel_init() won't prevent initializing a panel with a
DRM_MODE_CONNECTOR_Unknown connector type. Luckily there are no in-tree
users doing it, so ta
drm_panel_bridge_remove() reads bridge->funcs to find out whether this is a
panel bridge or another kind of bridge. drm_bridge_is_panel() is made
exactly for that, so use it.
Signed-off-by: Luca Ceresoli
---
This patch was added in v6.
---
drivers/gpu/drm/bridge/panel.c | 2 +-
1 file changed,
Document in detail the new refcounted bridges as well as the "legacy"
bridges.
Signed-off-by: Luca Ceresoli
---
Changes in v6:
- update to the new devm_drm_bridge_alloc() API
- rewrite and improve various sentences for clarity
- fix typos (Randy Dunlap)
This patch was added in v5.
---
Docu
Between drm_bridge_add() and drm_bridge_remove() bridges "published" to the
DRM core via the global bridge_list and visible in
/sys/kernel/debug/dri/bridges. However between drm_bridge_remove() and the
last drm_bridge_put(), a refcounted bridge memory is still allocated even
though the bridge is no
The usefulness of /sys/kernel/debug/dri/bridges is limited as it only shows
bridges betweeb drm_bridge_add() and drm_bridge_remove(). However
refcounted bridges can stay allocated for way longer, and a memory leak due
to a missing drm_bridge_put() would not be visible in this debugfs file.
Add rem
Add a devm/drmm action to these functions so the bridge reference is
dropped automatically when the caller is removed.
Signed-off-by: Luca Ceresoli
---
This patch was added in v6.
---
drivers/gpu/drm/drm_bridge.c | 39 +++
1 file changed, 39 insertions(+)
d
DRM bridges are currently considered as a fixed element of a DRM card, and
thus their lifetime is assumed to extend for as long as the card
exists. New use cases, such as hot-pluggable hardware with video bridges,
require DRM bridges to be added and removed to a DRM card without tearing
the card do
Bridges obtained via devm_drm_of_get_bridge() will be put when the
requesting device is removed. However drivers which obtained them may need
to put the obtained reference way before being destroyed, especially in
case of hot-unplug of the bridge they hold a reference to.
Add devm_drm_put_bridge()
of_drm_find_bridge() returns a pointer to a bridge, so it has to get a
reference and the caller will be in charge of putting it.
Callers of of_drm_find_bridge() are:
1. drm_of_panel_bridge_remove()
2. of_drm_find_bridge_by_endpoint()
3. drm_of_find_panel_or_bridge()
4. various DRM drivers
Ad
Add a basic KUnit test for the newly introduced drm_bridge_alloc().
Signed-off-by: Luca Ceresoli
---
Changed in v6:
- update to new drm_bridge_alloc() API
- remove drm_test_drm_bridge_put test, not straightforward to write with
the new API and the current notification mechanism
- do not a
In preparation for allowing bridges to be added to and removed from a DRM
card without destroying the whole card, add a new DRM bridge function
called on addition and removal of bridges.
Signed-off-by: Luca Ceresoli
---
Changed in v6:
- rebased fixing conflicts
Changed in v5:
- fixed kerneld
Adding a panel does currently not add a panel_bridge wrapping it. Usually
the panel_bridge creation happens when some other driver (e.g. the previous
bridge or the encoder) calls *_of_get_bridge() and the following element in
the pipeline is a panel.
This has some drawbacks:
* the panel_bridge i
This function is for panel_bridge instances only. The silent return when
invoked on other bridges might hide actual errors, so avoid them to go
unnoticed.
Signed-off-by: Luca Ceresoli
---
This patch was added in v6.
---
drivers/gpu/drm/bridge/panel.c | 4 +++-
1 file changed, 3 insertions(+),
The global bridges_list holding all the bridges between drm_bridge_add()
and drm_bridge_remove() cannot be inspected via debugfs. Add a file showing
it.
To avoid code duplication, move the code printing a bridge info to a common
function.
Note: this change requires exporting bridge_list and the m
devm_drm_of_get_bridge() and drmm_of_get_bridge() do not have anything to
do with struct drm_panel anymore, they just manage bridges. So move them
from bridge/panel.c to drm_bridge.c.
Move also of_drm_find_bridge_by_endpoint() which is used only by
devm_drm_of_get_bridge() and drmm_of_get_bridge()
1 - 100 of 240 matches
Mail list logo
