From: Andy Yan
The helper functions drm_dp_link_power_up/down were moved to Tegra
DRM at 2019[0].
Now since more and more users are duplicating the same code in their
own drivers, it's time to make them as DRM DP common helpers again.
[0]https://patchwork.freedesktop.org/patch/336850/?series=68
From: Andy Yan
Use the common dp link power up/down helpers to avoid duplicating code.
Signed-off-by: Andy Yan
---
.../drm/bridge/cadence/cdns-mhdp8546-core.c | 74 +--
1 file changed, 2 insertions(+), 72 deletions(-)
diff --git a/drivers/gpu/drm/bridge/cadence/cdns-mhdp854
From: Andy Yan
Use the common dp link power up/down helpers to avoid duplicating code.
Signed-off-by: Andy Yan
---
.../drm/bridge/analogix/analogix-anx78xx.c| 30 +--
1 file changed, 1 insertion(+), 29 deletions(-)
diff --git a/drivers/gpu/drm/bridge/analogix/analogix-anx
From: Andy Yan
Use the common dp link power up/down helpers to avoid duplicating code.
Signed-off-by: Andy Yan
---
drivers/gpu/drm/bridge/ite-it6505.c | 46 +++--
1 file changed, 4 insertions(+), 42 deletions(-)
diff --git a/drivers/gpu/drm/bridge/ite-it6505.c
b/driv
From: Andy Yan
Use the common dp link power up/down helpers to avoid duplicating code.
Signed-off-by: Andy Yan
---
.../drm/bridge/analogix/analogix-anx6345.c| 30 +--
1 file changed, 1 insertion(+), 29 deletions(-)
diff --git a/drivers/gpu/drm/bridge/analogix/analogix-anx
> On 13 Mar 2025, at 4:49 PM, Aditya Garg wrote:
>
> From: Hector Martin
>
> %p4cc is designed for DRM/V4L2 FourCCs with their specific quirks, but
> it's useful to be able to print generic 4-character codes formatted as
> an integer. Extend it to add format specifiers for printing generic
>
On Fri, Mar 14, 2025 at 11:38:43AM +0800, Andy Yan wrote:
> From: Andy Yan
>
> Use the common dp link power up/down helpers to avoid duplicating code.
>
> Signed-off-by: Andy Yan
> ---
>
> .../drm/bridge/analogix/analogix-anx78xx.c| 30 +--
> 1 file changed, 1 insertion(+)
On Fri, Mar 14, 2025 at 11:38:44AM +0800, Andy Yan wrote:
> From: Andy Yan
>
> Use the common dp link power up/down helpers to avoid duplicating code.
>
> Signed-off-by: Andy Yan
> ---
>
> drivers/gpu/drm/bridge/ite-it6505.c | 46 +++--
> 1 file changed, 4 insertions(+
From: Dmitry Baryshkov
Switch drm_dp_helper.c to use new set of DPCD read / write helpers.
Reviewed-by: Lyude Paul
Acked-by: Jani Nikula
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/display/drm_dp_helper.c | 296 +---
1 file changed, 116 insertions(+), 180
From: Dmitry Baryshkov
Switch drm_dp_mst_topology.c to use new set of DPCD read / write helpers.
Reviewed-by: Lyude Paul
Acked-by: Jani Nikula
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/display/drm_dp_mst_topology.c | 105 +-
1 file changed, 51 insertions(+),
From: Dmitry Baryshkov
Existing DPCD access functions return an error code or the number of
bytes being read / write in case of partial access. However a lot of
drivers either (incorrectly) ignore partial access or mishandle error
codes. In other cases this results in a boilerplate code which com
From: Dmitry Baryshkov
Switch drm_dp_cec.c to use new set of DPCD read / write helpers.
Reviewed-by: Lyude Paul
Acked-by: Jani Nikula
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/display/drm_dp_cec.c | 37 ++--
1 file changed, 18 insertions(+), 19 delet
Existing DPCD access functions return an error code or the number of
bytes being read / write in case of partial access. However a lot of
drivers either (incorrectly) ignore partial access or mishandle error
codes. In other cases this results in a boilerplate code which compares
returned value with
From: Dmitry Baryshkov
Add display controller, two DSI hosts, two DSI PHYs and a single DP
controller. Link DP to the QMP Combo PHY.
Signed-off-by: Dmitry Baryshkov
---
arch/arm64/boot/dts/qcom/sar2130p.dtsi | 394 +
1 file changed, 394 insertions(+)
diff --git
From: Dmitry Baryshkov
Qualcomm SAR2130P requires slightly different setup for the DSI PHY. It
is a 5nm PHY (like SM8450), so supplies are the same, but the rest of
the configuration is the same as SM8550 DSI PHY.
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/msm/dsi/phy/dsi_phy.c |
From: Dmitry Baryshkov
drm_dp_dpcd_read_link_status() follows the "return error code or number
of bytes read" protocol, with the code returning less bytes than
requested in case of some errors. However most of the drivers
interpreted that as "return error code in case of any error". Switch
drm_dp
+Cc Stefan
Hi Krzysztof,
On 13/03/25 12:03, Krzysztof Kozlowski wrote:
On 13/03/2025 15:43, Maíra Canal wrote:
In order to enforce per-SoC register rules, add per-compatible
restrictions. V3D 3.3 (represented by brcm,7268-v3d) has a cache
controller (GCA), which is not present in other V3D gen
On Fri, Mar 14, 2025 at 08:50:29AM +0800, Andy Yan wrote:
>
> Hi Maxime and Simona,
>
>
> At 2025-03-13 19:55:33, "Maxime Ripard" wrote:
> >Hi,
> >
> >On Thu, Mar 13, 2025 at 04:09:54PM +0800, Andy Yan wrote:
> >> At 2025-03-05 19:55:19, "Andy Yan" wrote:
> >> >At 2025-03-04 19:10:47, "Maxime
From: Dmitry Baryshkov
Describe DPU controller present on Qualcomm SAR2130P platform.
Signed-off-by: Dmitry Baryshkov
Reviewed-by: Krzysztof Kozlowski
---
Documentation/devicetree/bindings/display/msm/qcom,sc7280-dpu.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devic
From: Dmitry Baryshkov
Describe the Mobile Display SubSystem (MDSS) device present on the
Qualcomm SAR2130P platform. It looks pretty close to SM8550 on the
system level. SAR2130P features two DSI hosts and single DisplayPort
controller.
Signed-off-by: Dmitry Baryshkov
Reviewed-by: Krzysztof Ko
Add support for the Mobile Display SubSystem (MDSS) device present on
the Qualcomm SAR2130P platform. The MDSS device is similar to SM8550, it
features two MIPI DSI controllers, two MIPI DSI PHYs and one DisplayPort
controller.
Note, due to the technical limitations DP controller wasn't completely
From: Dmitry Baryshkov
Add compatible and device configuration for the Qualcomm SAR2130P
platform.
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/msm/msm_mdss.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/gpu/drm/msm/msm_mdss.c b/drivers/gpu/drm/msm/msm_mdss.c
From: Dmitry Baryshkov
Describe MIPI DSI PHY present on Qualcomm SAR2130P platform.
Signed-off-by: Dmitry Baryshkov
Reviewed-by: Krzysztof Kozlowski
---
Documentation/devicetree/bindings/display/msm/dsi-phy-7nm.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/
From: Dmitry Baryshkov
Describe DisplayPort controller present on Qualcomm SAR2130P platform.
Signed-off-by: Dmitry Baryshkov
Reviewed-by: Krzysztof Kozlowski
---
Documentation/devicetree/bindings/display/msm/dp-controller.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation
From: Dmitry Baryshkov
Add DPU driver support for the Qualcomm SAR2130P platform. It is mostly
the same as SM8550, minor differences in the CDP configuration.
Signed-off-by: Dmitry Baryshkov
---
.../drm/msm/disp/dpu1/catalog/dpu_9_1_sar2130p.h | 434 +
drivers/gpu/drm/msm
From: Shixiong Ou
Using device_create_with_groups() to simplify creation and removal.
Same as commit 1083a7be4504 ("tty: Use static attribute groups for
sysfs entries").
Signed-off-by: Shixiong Ou
---
drivers/video/fbdev/core/fbcon.c | 69 +---
1 file changed, 19 in
From: Dmitry Baryshkov
Add the SAR2130P compatible to clients compatible list, the device
require identity domain.
Signed-off-by: Dmitry Baryshkov
---
drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
b/dr
On Thu, Mar 13, 2025 at 08:10:04PM -0500, Chenyuan Yang wrote:
> The function dpu_plane_virtual_atomic_check was dereferencing pointers
> returned by drm_atomic_get_plane_state without checking for errors. This
> could lead to undefined behavior if the function returns an error pointer.
>
> This c
Move away from using deprecated API and use _multi
variants if available. Use mipi_dsi_msleep()
and mipi_dsi_usleep_range() instead of msleep()
and usleep_range() respectively.
Used Coccinelle to find the _multi variant APIs,
replacing mpi_dsi_msleep() where necessary and for returning
dsi_ctx.acc
On Fri, Mar 14, 2025 at 11:38:41AM +0800, Andy Yan wrote:
> From: Andy Yan
>
> Use the common dp link power up/down helpers to avoid duplicating code.
>
> Signed-off-by: Andy Yan
> ---
>
> .../drm/bridge/cadence/cdns-mhdp8546-core.c | 74 +--
> 1 file changed, 2 insertions(+
On Fri, Mar 14, 2025 at 11:38:42AM +0800, Andy Yan wrote:
> From: Andy Yan
>
> Use the common dp link power up/down helpers to avoid duplicating code.
>
> Signed-off-by: Andy Yan
> ---
>
> .../drm/bridge/analogix/analogix-anx6345.c| 30 +--
> 1 file changed, 1 insertion(+)
From: Guenter Roeck
Add name of functions triggering warning backtraces to the __bug_table
object section to enable support for suppressing WARNING backtraces.
To limit image size impact, the pointer to the function name is only added
to the __bug_table section if both CONFIG_KUNIT_SUPPRESS_BACK
From: Guenter Roeck
Add name of functions triggering warning backtraces to the __bug_table
object section to enable support for suppressing WARNING backtraces.
To limit image size impact, the pointer to the function name is only added
to the __bug_table section if both CONFIG_KUNIT_SUPPRESS_BACK
From: Guenter Roeck
Add name of functions triggering warning backtraces to the __bug_table
object section to enable support for suppressing WARNING backtraces.
To limit image size impact, the pointer to the function name is only added
to the __bug_table section if both CONFIG_KUNIT_SUPPRESS_BACK
From: Guenter Roeck
Add name of functions triggering warning backtraces to the __bug_table
object section to enable support for suppressing WARNING backtraces.
To limit image size impact, the pointer to the function name is only added
to the __bug_table section if both CONFIG_KUNIT_SUPPRESS_BACK
From: Guenter Roeck
Add name of functions triggering warning backtraces to the __bug_table
object section to enable support for suppressing WARNING backtraces.
To limit image size impact, the pointer to the function name is only added
to the __bug_table section if both CONFIG_KUNIT_SUPPRESS_BACK
From: Guenter Roeck
The drm_test_rect_calc_hscale and drm_test_rect_calc_vscale unit tests
intentionally trigger warning backtraces by providing bad parameters to
the tested functions. What is tested is the return value, not the existence
of a warning backtrace. Suppress the backtraces to avoid c
From: Guenter Roeck
Document API functions for suppressing warning backtraces.
Tested-by: Linux Kernel Functional Testing
Acked-by: Dan Carpenter
Reviewed-by: Kees Cook
Signed-off-by: Guenter Roeck
Reviewed-by: David Gow
Signed-off-by: Alessandro Carminati
---
Documentation/dev-tools/kuni
On Thu, Mar 13, 2025 at 11:43:22AM +, Alessandro Carminati wrote:
> diff --git a/arch/arm64/include/asm/bug.h b/arch/arm64/include/asm/bug.h
> index 28be048db3f6..044c5e24a17d 100644
> --- a/arch/arm64/include/asm/bug.h
> +++ b/arch/arm64/include/asm/bug.h
> @@ -11,8 +11,14 @@
>
> #include
On Thu, Mar 13, 2025 at 08:53:28AM +, Aditya Garg wrote:
> > On 13 Mar 2025, at 2:19 PM, Andy Shevchenko
> > wrote:
> > On Thu, Mar 13, 2025 at 07:26:05AM +, Aditya Garg wrote:
> On 13 Mar 2025, at 12:58 AM, Andy Shevchenko
> wrote:
> >>> On Wed, Mar 12, 2025 at 07:14:36PM +00
From: Guenter Roeck
Add unit tests to verify that warning backtrace suppression works.
If backtrace suppression does _not_ work, the unit tests will likely
trigger unsuppressed backtraces, which should actually help to get
the affected architectures / platforms fixed.
Tested-by: Linux Kernel Fu
From: Guenter Roeck
Add name of functions triggering warning backtraces to the __bug_table
object section to enable support for suppressing WARNING backtraces.
To limit image size impact, the pointer to the function name is only added
to the __bug_table section if both CONFIG_KUNIT_SUPPRESS_BACK
From: Guenter Roeck
Declaring the defines needed for suppressing warning inside
'#ifdef CONFIG_DEBUG_BUGVERBOSE' results in a kerneldoc warning.
.../bug.h:29: warning: expecting prototype for _EMIT_BUG_ENTRY().
Prototype was for HAVE_BUG_FUNCTION() instead
Move the defines above the ker
The current bridge state is accessible from the drm_bridge structure,
but since it's fairly indirect it's not easy to figure out.
Provide a helper to retrieve it.
Reviewed-by: Dmitry Baryshkov
Signed-off-by: Maxime Ripard
---
include/drm/drm_bridge.h | 32
1 fi
The drm_bridge structure contains an encoder pointer that is widely used
by bridge drivers. This pattern is largely documented as deprecated in
other KMS entities for atomic drivers.
However, one of the main use of that pointer is done in attach to just
call drm_bridge_attach on the next bridge to
None of the drm_bridge function have kunit tests so far. Let's change
that, starting with drm_bridge_get_current_state().
Reviewed-by: Dmitry Baryshkov
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/Kconfig | 1 +
drivers/gpu/drm/tests/Makefile | 1 +
drivers/gpu/
Hi,
Here's a series of changes after to the KMS helpers and bridge API
following a bunch of reviews I did.
It's mostly centered across providing an easier time to deal with bridge
states, and a somewhat consistent with the other entities API.
It's build tested only, with arm64 allmodconfig.
Max
Hi Maintainers,
There are some flake test reported for mediatek driver testing in drm-ci.
# Board Name: mt8183-kukui-jacuzzi-juniper-sku16
# Failure Rate: 20
# IGT Version: 1.30-g04bedb923
# Linux Version: 6.14.0-rc4
kms_atomic_transition@plane-all-modeset-transition-internal-panels
11:34:51.89
Le 13/03/2025 à 11:45, Vignesh Raman a écrit :
Hi Maintainers,
Hi Vignesh,
Thanks for the report.
On my setup, this test passed, and the others are skipped.
I think the issue on this specific test may be due to performance (seems
to be a timing issue, I will try to slow down my VM). The
On 2025-03-13 07:29, Thadeu Lima de Souza Cascardo wrote:
On Wed, Feb 05, 2025 at 10:06:38AM -0300, Thadeu Lima de Souza Cascardo wrote:
ctx->dmub_srv will de NULL if the ASIC does not support DMUB, which is
tested in dm_dmub_sw_init.
However, it will be dereferenced in dmub_hw_lock_mgr_cmd
On 13/03/2025 15:43, Maíra Canal wrote:
> In order to enforce per-SoC register rules, add per-compatible
> restrictions. V3D 3.3 (represented by brcm,7268-v3d) has a cache
> controller (GCA), which is not present in other V3D generations.
> Declaring these differences helps ensure the DTB accuratel
Add a basic test for checking whether scheduler respects the configured
credit limit.
Signed-off-by: Tvrtko Ursulin
Cc: Christian König
Cc: Danilo Krummrich
Cc: Matthew Brost
Cc: Philipp Stanner
Acked-by: Christian König
---
drivers/gpu/drm/scheduler/tests/tests_basic.c | 60 +++
ret)
+ goto err_free;
+
ret = drm_dev_register(drm, 0);
if (ret)
goto err_unload;
---
base-commit: f9f087d946266bc5da7c3a17bd8fd9d01969e3cf
change-id: 20250313-mxsfb_probe-fix-rollback-on-error-3074b9080f34
Best regards,
--
Luca Ceresoli
Applied. Thanks.
Alex
On Thu, Mar 13, 2025 at 11:17 AM Leo Li wrote:
>
>
>
> On 2025-03-13 07:29, Thadeu Lima de Souza Cascardo wrote:
> > On Wed, Feb 05, 2025 at 10:06:38AM -0300, Thadeu Lima de Souza Cascardo
> > wrote:
> >> ctx->dmub_srv will de NULL if the ASIC does not support DMUB, which
…
> can only release 'pfp' field of 'gfx'. The release function of 'me' field
> should be gfx_v12_0_me_fini().
Do you care for an imperative wording in such a change description?
https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rs
On Thu, Mar 13, 2025 at 04:29:07PM +0800, Chen Ni wrote:
> clk_prepare_enable() already checked NULL clock parameter.
> Remove unneeded NULL check for clk here.
You're not saving anything here. If mdev->aclk is NULL you still end up
calling clk_prepare() and clk_enable() even if they return zero i
From: Guenter Roeck
Add name of functions triggering warning backtraces to the __bug_table
object section to enable support for suppressing WARNING backtraces.
To limit image size impact, the pointer to the function name is only added
to the __bug_table section if both CONFIG_KUNIT_SUPPRESS_BACK
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 a time, or alternatively
jobs can be configured with a time duration in
Add some basic tests for exercising entity priority handling.
Signed-off-by: Tvrtko Ursulin
Cc: Christian König
Cc: Danilo Krummrich
Cc: Matthew Brost
Cc: Philipp Stanner
Acked-by: Christian König
---
drivers/gpu/drm/scheduler/tests/tests_basic.c | 95 ++-
1 file changed, 94
Applied. Thanks!
Alex
On Wed, Mar 12, 2025 at 6:09 AM Wentao Liang wrote:
>
> In gfx_v12_0_cp_gfx_load_me_microcode_rs64(), gfx_v12_0_pfp_fini() is
> incorrectly used to free 'me' field of 'gfx', since gfx_v12_0_pfp_fini()
> can only release 'pfp' field of 'gfx'. The release function of 'me' fi
On Thu, 2025-03-13 at 13:57 +0100, Christian König wrote:
> Am 13.03.25 um 13:50 schrieb Thomas Hellström:
> > Hi, Christian
> >
> > On Thu, 2025-03-13 at 11:19 +0100, Christian König wrote:
> > > Am 12.03.25 um 22:03 schrieb Thomas Hellström:
> > > > This RFC implements and requests comments for
Hello,
I am a hobbyist developer who has been working on a project to create a new Rust
HID device driver and the needed core abstractions for writing more HID device
drivers in Rust. My goal is to support the USB Monitor Control Class needed for
functionality such as backlight control for monitor
This is a very basic "hello, world!" implementation to illustrate that the
probe and remove callbacks are working as expected. I chose an arbitrary
device I had on hand for populating in the HID device id table.
[ +0.012968] monitor_control: Probing HID device vendor: 2389 product: 29204
using
Move some options out into a new debug specific kconfig file in order to
make things a bit cleaner.
Signed-off-by: Tvrtko Ursulin
Cc: Christian König
Cc: Danilo Krummrich
Cc: Matthew Brost
Cc: Philipp Stanner
Acked-by: Christian König
---
drivers/gpu/drm/Kconfig | 109 ++--
> Wiadomość napisana przez Andy Yan w dniu 13 mar 2025, o
> godz. 01:23:
>
>
> Hi Piotr,
> 在 2025-03-12 22:23:15，"Piotr Oniszczuk" 写道：
>
> This series still based on Linux 6.14 rc4.
>
> Did you apply the three dependency patch mentioned in my cover letter?
Thx!
I noticed
https://lore.k
On Thu, Mar 13, 2025 at 11:06:54AM +, Aditya Garg wrote:
> > On 13 Mar 2025, at 4:18 PM, Petr Mladek wrote:
> > On Thu 2025-03-13 09:13:23, Aditya Garg wrote:
> >>> On 13 Mar 2025, at 2:27 PM, Andy Shevchenko
> >>> wrote:
> >>> On Thu, Mar 13, 2025 at 08:53:28AM +, Aditya Garg wrote:
> >
In addition to the standard reset controller, V3D 7.x requires configuring
the V3D_SMS registers for proper power on/off and reset. Add the new
registers to `v3d_regs.h` and ensure they are properly configured during
device probing, removal, and reset.
This change fixes GPU reset issues on the Ras
The V3D driver currently determines the GPU tech version (33, 41...)
by reading a register. This approach has worked so far since this
information wasn’t needed before powering on the GPU.
V3D 7.1 introduces new registers that must be written to power on the
GPU, requiring us to know the V3D versi
The V3D driver still relies on `drm_sched_increase_karma()` and
`drm_sched_resubmit_jobs()` for resubmissions when a timeout occurs.
The function `drm_sched_increase_karma()` marks the job as guilty, while
`drm_sched_resubmit_jobs()` sets an error (-ECANCELED) in the DMA fence of
that guilty job.
In order to enforce per-SoC register rules, add per-compatible
restrictions. V3D 3.3 (represented by brcm,7268-v3d) has a cache
controller (GCA), which is not present in other V3D generations.
Declaring these differences helps ensure the DTB accurately reflect
the hardware design.
While not ideal,
Similar to commit e4b5ccd392b9 ("drm/v3d: Ensure job pointer is set to
NULL after job completion"), ensure the job pointer is set to `NULL` when
a job's fence has an error. Failing to do so can trigger kernel warnings
in specific scenarios, such as:
1. v3d_csd_job_run() assigns `v3d->csd_job = job
Hi Anusha,
In addition to the feedback Luca already provided, I have a few comments
On Wed, Mar 12, 2025 at 08:54:42PM -0400, Anusha Srivatsa wrote:
> Introduce reference counted allocations for panels to avoid
> use-after-free. The patch adds the macro devm_drm_bridge_alloc()
> to allocate a new
ev_register(drm, 0);
if (ret)
---
base-commit: f9f087d946266bc5da7c3a17bd8fd9d01969e3cf
change-id: 20250313-mxsfb_probe-fix-rollback-on-error-3074b9080f34
Best regards,
--
Luca Ceresoli
On Thu, Mar 13, 2025 at 11:09:44AM +0100, Luca Ceresoli wrote:
> Hello Anusha,
>
> On Wed, 12 Mar 2025 20:54:42 -0400
> Anusha Srivatsa wrote:
>
> > Introduce reference counted allocations for panels to avoid
> > use-after-free. The patch adds the macro devm_drm_bridge_alloc()
> > to allocate a
Hi,
On Mon, Mar 10, 2025 at 11:12:59AM +0200, Pekka Paalanen wrote:
> On Fri, 7 Mar 2025 15:50:41 +0100
> Louis Chauvet wrote:
>
> > Le 07/03/2025 à 11:20, Maxime Ripard a écrit :
> > > On Wed, Feb 19, 2025 at 02:35:14PM +0100, Louis Chauvet wrote:
> > >>
> > >>
> > >> Le 19/02/2025 à 11:15, M
series looks ok to me. Who is pushing this to drm-misc-next? (I can if
nobody else does)
On Fri, Mar 07, 2025 at 10:55:57AM -0400, Jason Gunthorpe wrote:
> On Fri, Mar 07, 2025 at 02:09:12PM +0100, Simona Vetter wrote:
>
> > > A driver can do a health check immediately in remove() and make a
> > > decision if the device is alive or not to speed up removal in the
> > > hostile hot unpl
e call to the
top? No extra cleanup would be required then.
Best regards
Thomas
ret = drm_dev_register(drm, 0);
if (ret)
---
base-commit: f9f087d946266bc5da7c3a17bd8fd9d01969e3cf
change-id: 20250313-mxsfb_probe-fix-rollback-on-error-3074b9080f34
Best regards,
--
--
Thomas Zimmer
On Wed, Feb 05, 2025 at 10:06:38AM -0300, Thadeu Lima de Souza Cascardo wrote:
> ctx->dmub_srv will de NULL if the ASIC does not support DMUB, which is
> tested in dm_dmub_sw_init.
>
> However, it will be dereferenced in dmub_hw_lock_mgr_cmd if
> should_use_dmub_lock returns true.
>
> This has be
From: Guenter Roeck
Count suppressed warning backtraces to enable code which suppresses
warning backtraces to check if the expected backtrace(s) have been
observed.
Using atomics for the backtrace count resulted in build errors on some
architectures due to include file recursion, so use a plain
Hi Vinod, Thanks for the review comments.
On 3/11/2025 2:30 AM, Vinod Koul wrote:
On 12-02-25, 17:35, Jyothi Kumar Seerapu wrote:
GSI hardware generates an interrupt for each transfer completion.
For multiple messages within a single transfer, this results in
N interrupts for N messages, leadin
在 2025/3/13 00:47, Thomas Weißschuh 写道:
Hi,
On Tue, Mar 11, 2025 at 07:28:55PM +0800, oushixiong1...@163.com wrote:
From: Shixiong Ou
Use device_add_group() to simplify creation and removal.
Signed-off-by: Shixiong Ou
---
drivers/video/fbdev/core/fbcon.c | 48 +++
On 3/12/2025 5:18 PM, Krzysztof Kozlowski wrote:
> On Tue, Mar 11, 2025 at 05:54:42PM +0530, Ayushi Makhija wrote:
>> Add anx7625 DSI to DP bridge device nodes.
>>
>> Signed-off-by: Ayushi Makhija
>> ---
>> arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi | 208 -
>> 1 file changed,
Am 13.03.25 um 13:50 schrieb Thomas Hellström:
> Hi, Christian
>
> On Thu, 2025-03-13 at 11:19 +0100, Christian König wrote:
>> Am 12.03.25 um 22:03 schrieb Thomas Hellström:
>>> This RFC implements and requests comments for a way to handle SVM
>>> with multi-device,
>>> typically with fast interco
Some unit tests intentionally trigger warning backtraces by passing bad
parameters to kernel API functions. Such unit tests typically check the
return value from such calls, not the existence of the warning backtrace.
Such intentionally generated warning backtraces are neither desirable
nor useful
From: Guenter Roeck
Some unit tests intentionally trigger warning backtraces by passing
bad parameters to API functions. Such unit tests typically check the
return value from those calls, not the existence of the warning backtrace.
Such intentionally generated warning backtraces are neither desi
From: Guenter Roeck
Add name of functions triggering warning backtraces to the __bug_table
object section to enable support for suppressing WARNING backtraces.
To limit image size impact, the pointer to the function name is only added
to the __bug_table section if both CONFIG_KUNIT_SUPPRESS_BACK
Hi,
On Thu, Mar 13, 2025 at 04:09:54PM +0800, Andy Yan wrote:
> At 2025-03-05 19:55:19, "Andy Yan" wrote:
> >At 2025-03-04 19:10:47, "Maxime Ripard" wrote:
> >>With the bridges switching over to drm_bridge_connector, the direct
> >>association between a bridge driver and its connector was lost.
From: Shixiong Ou
Using device_create_with_groups() to simplify creation and removal.
Same as commit 1083a7be4504 ("tty: Use static attribute groups for
sysfs entries").
Signed-off-by: Shixiong Ou
---
drivers/video/fbdev/core/fbcon.c | 67 +---
1 file changed, 19 in
On 13/03/2025 15:43, Maíra Canal wrote:
> V3D 7.1 exposes a new register block, called V3D_SMS. As BCM2712 has a
> V3D 7.1 core, add a new register item to its compatible. Similar to the
> GCA, which is specific for V3D 3.3, SMS should only be added for V3D 7.1
> variants (such as brcm,2712-v3d).
>
As established in commit 89d04995f76c ("MAINTAINERS: Drop Emma Anholt
from all M lines."), Emma is no longer active in the Linux kernel and
dropped the V3D maintainership. Therefore, remove Emma as one of the DT
maintainers and add the current V3D driver maintainer.
Acked-by: Emma Anholt
Acked-by
On 03/13, Thadeu Lima de Souza Cascardo wrote:
> On Wed, Feb 05, 2025 at 10:06:38AM -0300, Thadeu Lima de Souza Cascardo wrote:
> > ctx->dmub_srv will de NULL if the ASIC does not support DMUB, which is
> > tested in dm_dmub_sw_init.
> >
> > However, it will be dereferenced in dmub_hw_lock_mgr_cmd
Hello Thomas,
On Thu, 13 Mar 2025 15:40:43 +0100
Thomas Zimmermann wrote:
> > @@ -365,9 +365,10 @@ static int mxsfb_probe(struct platform_device *pdev)
> > * located anywhere in RAM
> > */
> > ret = aperture_remove_all_conflicting_devices(mxsfb_driver.name);
> > - if (ret)
> > -
Hi,
[quick reply because I am completely under the water for the next 2
weeks]
On Mar 13 2025, Rahul Rameshbabu wrote:
> Hello,
>
> I am a hobbyist developer who has been working on a project to create a new
> Rust
> HID device driver and the needed core abstractions for writing more HID device
clk_prepare_enable() already checked NULL clock parameter.
Remove unneeded NULL check for clk here.
Signed-off-by: Chen Ni
---
drivers/gpu/drm/arm/display/komeda/komeda_dev.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/arm/display/komeda/komeda_dev.c
b/
Add a new field to the xe_pagefault struct, address_type, that tracks
the type of fault the pagefault incurred.
Signed-off-by: Jonathan Cavitt
---
drivers/gpu/drm/xe/xe_gt_pagefault.c | 3 +++
drivers/gpu/drm/xe/xe_gt_pagefault.h | 1 +
2 files changed, 4 insertions(+)
diff --git a/drivers/gpu/
Remove the xe embedded drm_pagemap, and instead allocate and
reference count.
This is a step towards adding drm_pagemaps on demand.
Signed-off-by: Thomas Hellström
---
drivers/gpu/drm/drm_pagemap.c| 58 +++-
drivers/gpu/drm/xe/xe_device_types.h | 2 +-
drivers/gp
Hi Dave and Sima,
Here goes xe fixes for this week.
It is worth mention that we are disabling D3Cold on BMG because
we found some bugs where depending on the combination of BMG
card and the host, the PCI upstream port link port re-training
might fail on D3Cold -> D0 blowing things up. But while w
> On 13 Mar 2025, at 2:19 PM, Andy Shevchenko
> wrote:
>
> On Thu, Mar 13, 2025 at 07:26:05AM +, Aditya Garg wrote:
On 13 Mar 2025, at 12:58 AM, Andy Shevchenko
wrote:
>>> On Wed, Mar 12, 2025 at 07:14:36PM +, Aditya Garg wrote:
> On 12 Mar 2025, at 9:05 PM, Sven Peter
Hello Will,
On Thu, Mar 13, 2025 at 1:25 PM Will Deacon wrote:
>
> On Thu, Mar 13, 2025 at 11:43:22AM +, Alessandro Carminati wrote:
> > diff --git a/arch/arm64/include/asm/bug.h b/arch/arm64/include/asm/bug.h
> > index 28be048db3f6..044c5e24a17d 100644
> > --- a/arch/arm64/include/asm/bug.h
1 - 100 of 220 matches
Mail list logo
