On Fri, Jul 18, 2025 at 12:44:11PM -0500, Mario Limonciello wrote:
> On 7/18/2025 12:36 PM, Bjorn Helgaas wrote:
> > On Fri, Jul 18, 2025 at 12:29:05PM -0500, Mario Limonciello wrote:
> > > On 7/18/2025 12:25 PM, Bjorn Helgaas wrote:
> > > > In addition to Mani's question about whether /sys/bus/pci
Hi Chia-I,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on next-20250718]
[cannot apply to linus/master v6.16-rc6]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting pa
Hi Chia-I,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on next-20250718]
[cannot apply to linus/master v6.16-rc6]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting pa
Hi Chia-I,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on v6.16-rc6 next-20250718]
[cannot apply to linus/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting pa
On Sat, Jul 19, 2025 at 5:41 PM Daniel Almeida
wrote:
>
> Hi Chia-I Wu :)
>
> > On 19 Jul 2025, at 21:01, Chia-I Wu wrote:
> >
> > This series adds devcoredump support to panthor.
> >
> > This is written from scratch and is not based on the prior work[1]. The
> > main differences are
>
> I wonder
Hi Chia-I Wu :)
> On 19 Jul 2025, at 21:01, Chia-I Wu wrote:
>
> This series adds devcoredump support to panthor.
>
> This is written from scratch and is not based on the prior work[1]. The
> main differences are
I wonder why this was started from scratch? IIRC, that work stopped, among
other
On Thu, 17 Jul 2025 16:28:42 -0700, Jessica Zhang wrote:
> On some MSM chipsets, the display port controller is capable of supporting
> up to 4 streams.
>
> To drive these additional streams, the pixel clocks for the corresponding
> stream needs to be enabled.
>
> Fixup the documentation of som
When the flag is set, bo data is captured for devcoredump.
Signed-off-by: Chia-I Wu
---
drivers/gpu/drm/panthor/panthor_coredump.c | 36 ++
drivers/gpu/drm/panthor/panthor_drv.c | 3 +-
drivers/gpu/drm/panthor/panthor_mmu.c | 7 +++--
include/uapi/drm/panthor_drm.
Fail early from panthor_vm_bind_prepare_op_ctx instead of late from
ops->map_pages.
Signed-off-by: Chia-I Wu
---
drivers/gpu/drm/panthor/panthor_mmu.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/panthor/panthor_mmu.c
b/drivers/gpu/drm/panthor/panthor_
Capture interesting MMU_AS_CONTROL regs for devcoredump.
Signed-off-by: Chia-I Wu
---
drivers/gpu/drm/panthor/panthor_coredump.c | 33 ++
drivers/gpu/drm/panthor/panthor_coredump.h | 11
drivers/gpu/drm/panthor/panthor_sched.c| 5
drivers/gpu/drm/panthor/pa
Capture interesting panthor_vma fields for devcoredump.
Because bo->label can change at anytime, we cap it to 32 chars to
simplify size estimation.
Signed-off-by: Chia-I Wu
---
drivers/gpu/drm/panthor/panthor_coredump.c | 78 --
drivers/gpu/drm/panthor/panthor_coredump.h | 1
Capture interesting panthor_fw_csg_iface fields for devcoredump.
Signed-off-by: Chia-I Wu
---
drivers/gpu/drm/panthor/panthor_coredump.c | 58 ++
drivers/gpu/drm/panthor/panthor_coredump.h | 23 +
drivers/gpu/drm/panthor/panthor_sched.c| 13 +
3 files changed,
Capture interesting panthor_fw_cs_iface, panthor_fw_ringbuf_input_iface,
and panthor_fw_ringbuf_output_iface fields for devcoredump.
Signed-off-by: Chia-I Wu
---
drivers/gpu/drm/panthor/panthor_coredump.c | 79 ++
drivers/gpu/drm/panthor/panthor_coredump.h | 32 +
dri
Capture interesting panthor_fw_global_iface fields for devcoredump.
Signed-off-by: Chia-I Wu
---
drivers/gpu/drm/panthor/panthor_coredump.c | 33 ++
drivers/gpu/drm/panthor/panthor_coredump.h | 13 +
2 files changed, 46 insertions(+)
diff --git a/drivers/gpu/drm/pant
Capture interesting GPU_CONTROL regs for devcoredump.
Signed-off-by: Chia-I Wu
---
drivers/gpu/drm/panthor/panthor_coredump.c | 85 ++
drivers/gpu/drm/panthor/panthor_coredump.h | 16
drivers/gpu/drm/panthor/panthor_regs.h | 6 ++
drivers/gpu/drm/panthor/panthor_sch
Create a devcoredump on any faulty or fatal event. The coredump data is
in YAML format for readability and flexibility.
Only panthor_group state is captured for now.
Signed-off-by: Chia-I Wu
---
drivers/gpu/drm/panthor/Makefile | 2 +
drivers/gpu/drm/panthor/panthor_coredump.c | 225
This series adds devcoredump support to panthor.
This is written from scratch and is not based on the prior work[1]. The
main differences are
- coredump triggers on all faulty/fatal/timeout events
- state capture and state process are two separated steps, with
GFP_NOWAIT being used for state
Prepare for `core::ffi::CStr` taking the place of `kernel::str::CStr` by
avoid methods that only exist on the latter.
Link: https://github.com/Rust-for-Linux/linux/issues/1075
Acked-by: Greg Kroah-Hartman
Reviewed-by: Alice Ryhl
Reviewed-by: Benno Lossin
Acked-by: Danilo Krummrich
Signed-off-b
Prepare for `core::ffi::CStr` taking the place of `kernel::str::CStr` by
avoid methods that only exist on the latter.
Link: https://github.com/Rust-for-Linux/linux/issues/1075
Acked-by: Greg Kroah-Hartman
Reviewed-by: Alice Ryhl
Reviewed-by: Benno Lossin
Acked-by: Danilo Krummrich
Signed-off-b
Prepare for `core::ffi::CStr` taking the place of `kernel::str::CStr` by
avoid methods that only exist on the latter.
Link: https://github.com/Rust-for-Linux/linux/issues/1075
Acked-by: Greg Kroah-Hartman
Reviewed-by: Alice Ryhl
Reviewed-by: Benno Lossin
Acked-by: Danilo Krummrich
Signed-off-b
Prepare for `core::ffi::CStr` taking the place of `kernel::str::CStr` by
avoid methods that only exist on the latter.
Link: https://github.com/Rust-for-Linux/linux/issues/1075
Acked-by: Greg Kroah-Hartman
Reviewed-by: Alice Ryhl
Reviewed-by: Benno Lossin
Acked-by: Danilo Krummrich
Signed-off-b
Prepare for `core::ffi::CStr` taking the place of `kernel::str::CStr` by
avoid methods that only exist on the latter.
Link: https://github.com/Rust-for-Linux/linux/issues/1075
Acked-by: Greg Kroah-Hartman
Reviewed-by: Alice Ryhl
Reviewed-by: Benno Lossin
Acked-by: Danilo Krummrich
Signed-off-b
Prepare for `core::ffi::CStr` taking the place of `kernel::str::CStr` by
avoid methods that only exist on the latter.
Link: https://github.com/Rust-for-Linux/linux/issues/1075
Acked-by: Greg Kroah-Hartman
Reviewed-by: Alice Ryhl
Reviewed-by: Benno Lossin
Acked-by: Danilo Krummrich
Signed-off-b
Prepare for `core::ffi::CStr` taking the place of `kernel::str::CStr` by
avoid methods that only exist on the latter.
Also avoid `Deref for CStr` as that impl doesn't exist on
`core::ffi::CStr`.
Link: https://github.com/Rust-for-Linux/linux/issues/1075
Acked-by: Greg Kroah-Hartman
Reviewed-by: A
Prepare for `core::ffi::CStr` taking the place of `kernel::str::CStr` by
avoid methods that only exist on the latter.
Link: https://github.com/Rust-for-Linux/linux/issues/1075
Acked-by: Greg Kroah-Hartman
Reviewed-by: Alice Ryhl
Reviewed-by: Benno Lossin
Acked-by: Danilo Krummrich
Signed-off-b
Prepare for `core::ffi::CStr` taking the place of `kernel::str::CStr` by
avoid methods that only exist on the latter.
Link: https://github.com/Rust-for-Linux/linux/issues/1075
Acked-by: Greg Kroah-Hartman
Reviewed-by: Alice Ryhl
Reviewed-by: Benno Lossin
Acked-by: Danilo Krummrich
Signed-off-b
Prepare for `core::ffi::CStr` taking the place of `kernel::str::CStr` by
avoid methods that only exist on the latter.
Link: https://github.com/Rust-for-Linux/linux/issues/1075
Acked-by: Greg Kroah-Hartman
Reviewed-by: Alice Ryhl
Reviewed-by: Benno Lossin
Acked-by: Danilo Krummrich
Signed-off-b
This is series 2b/5 of the migration to `core::ffi::CStr`[0].
20250704-core-cstr-prepare-v1-0-a91524037...@gmail.com.
This series depends on the prior series[0] and is intended to go through
the rust tree to reduce the number of release cycles required to
complete the work.
Subsystem maintainers:
Reduce coupling to implementation details of the formatting machinery by
avoiding direct use for `core`'s formatting traits and macros.
Acked-by: Greg Kroah-Hartman
Reviewed-by: Alice Ryhl
Reviewed-by: Benno Lossin
Acked-by: Danilo Krummrich
Signed-off-by: Tamir Duberstein
---
rust/kernel/sy
Reduce coupling to implementation details of the formatting machinery by
avoiding direct use for `core`'s formatting traits and macros.
Acked-by: Greg Kroah-Hartman
Reviewed-by: Alice Ryhl
Reviewed-by: Benno Lossin
Acked-by: Danilo Krummrich
Signed-off-by: Tamir Duberstein
---
rust/kernel/ku
Reduce coupling to implementation details of the formatting machinery by
avoiding direct use for `core`'s formatting traits and macros.
Acked-by: Greg Kroah-Hartman
Reviewed-by: Alice Ryhl
Reviewed-by: Benno Lossin
Acked-by: Danilo Krummrich
Signed-off-by: Tamir Duberstein
---
rust/kernel/fs
Reduce coupling to implementation details of the formatting machinery by
avoiding direct use for `core`'s formatting traits and macros.
Acked-by: Greg Kroah-Hartman
Reviewed-by: Alice Ryhl
Reviewed-by: Benno Lossin
Acked-by: Danilo Krummrich
Signed-off-by: Tamir Duberstein
---
rust/kernel/de
Reduce coupling to implementation details of the formatting machinery by
avoiding direct use for `core`'s formatting traits and macros.
Acked-by: Greg Kroah-Hartman
Reviewed-by: Alice Ryhl
Reviewed-by: Benno Lossin
Acked-by: Danilo Krummrich
Signed-off-by: Tamir Duberstein
---
rust/kernel/se
Reduce coupling to implementation details of the formatting machinery by
avoiding direct use for `core`'s formatting traits and macros.
Suggested-by: Alice Ryhl
Link:
https://rust-for-linux.zulipchat.com/#narrow/channel/288089-General/topic/Custom.20formatting/with/516476467
Acked-by: Greg Kroah
Reduce coupling to implementation details of the formatting machinery by
avoiding direct use for `core`'s formatting traits and macros.
Acked-by: Greg Kroah-Hartman
Reviewed-by: Alice Ryhl
Reviewed-by: Benno Lossin
Acked-by: Danilo Krummrich
Signed-off-by: Tamir Duberstein
---
rust/kernel/al
Reduce coupling to implementation details of the formatting machinery by
avoiding direct use for `core`'s formatting traits and macros.
Acked-by: Greg Kroah-Hartman
Reviewed-by: Alice Ryhl
Reviewed-by: Benno Lossin
Acked-by: Danilo Krummrich
Signed-off-by: Tamir Duberstein
---
drivers/gpu/no
This is series 2a/5 of the migration to `core::ffi::CStr`[0].
20250704-core-cstr-prepare-v1-0-a91524037...@gmail.com.
This series depends on the prior series[0] and is intended to go through
the rust tree to reduce the number of release cycles required to
complete the work.
Subsystem maintainers:
On Sat, Jul 19, 2025 at 09:23:04PM +0300, Ville Syrjälä wrote:
> On Wed, Jun 18, 2025 at 11:31:21AM +0200, Jocelyn Falempe wrote:
> > drm_panic draws in linear framebuffer, so it's easier to re-use the
> > current framebuffer, and disable tiling in the panic handler, to show
> > the panic screen.
>
On Wed, Jun 18, 2025 at 11:31:21AM +0200, Jocelyn Falempe wrote:
> drm_panic draws in linear framebuffer, so it's easier to re-use the
> current framebuffer, and disable tiling in the panic handler, to show
> the panic screen.
> This assumes that the alignment restriction is always smaller in
> lin
On Sat, 19 Jul 2025 13:58:13 +0300
Dmitry Baryshkov wrote:
> The bridge used in drm_bridge_connector_init() for CEC init does not
> correctly point to the required HDMI CEC bridge, which can lead to
> errors during CEC initialization.
>
> Fixes: 65a2575a68e4 ("drm/display: bridge-connector: hook
On 7/19/25 12:02 PM, Felix Richter wrote:
On 7/19/25 14:23, Mario Limonciello wrote:
On 7/19/25 5:10 AM, Felix Richter wrote:
Thanks for the reply.
I am aware that i can read and `edid` via sysfs from the drm device.
I did not know about `drm_info` but from a quick look at it I don't
thi
On Sat, 2025-07-19 at 18:44 +0200, Thomas Zimmermann wrote:
> Hi
>
> Am 17.07.25 um 17:02 schrieb Ruben Wauters:
> > Hello
> >
> > I was taking a look at the code for the gud driver. I am aware this
> > driver was recently orphaned and I wish to get up to speed on it,
> > and
> > maybe with enoug
On 7/18/25 5:11 PM, Doug Anderson wrote:
Hi,
On Thu, Jul 17, 2025 at 9:41 AM Brigham Campbell
wrote:
static int jdi_panel_prepare(struct drm_panel *panel)
{
struct jdi_panel *jdi = to_panel_jdi(panel);
+ struct mipi_dsi_multi_context dsi_ctx = { .accum_err = 0 };
nit:
On 7/19/25 14:23, Mario Limonciello wrote:
On 7/19/25 5:10 AM, Felix Richter wrote:
Thanks for the reply.
I am aware that i can read and `edid` via sysfs from the drm device.
I did not know about `drm_info` but from a quick look at it I don't
think it provides the information I need.
The p
Hi
Am 17.07.25 um 17:02 schrieb Ruben Wauters:
Hello
I was taking a look at the code for the gud driver. I am aware this
driver was recently orphaned and I wish to get up to speed on it, and
maybe with enough learning and work I can take over maintainance of it
in the future.
That's fantastic
On Sat, Jul 19, 2025 at 02:16:22AM +0200, Xaver Hugl wrote:
> Am Do., 10. Juli 2025 um 22:21 Uhr schrieb Ville Syrjälä
> :
> >
> > On Mon, Jul 07, 2025 at 03:41:20PM +, Naveen Kumar wrote:
> > > Allow asynchronous page flips on planes that either lack a framebuffer or
> > > retain the same fram
The per-fd reset counter tracks GPU resets caused by jobs submitted
through a specific file descriptor. However, there's a race condition
where the file descriptor can be closed while jobs are still running,
leading to potential access to freed memory when updating the reset
counter.
Ensure that t
CPU jobs and CACHE CLEAN jobs execute synchronously once the DRM
scheduler starts running them. Therefore, there is no fence to wait on,
neither are those jobs able to timeout.
Hence, remove the `timedout_job` hook from the CPU and CACHE CLEAN
scheduler ops.
Signed-off-by: Maíra Canal
---
drive
When the file descriptor is closed while a job is still running,
there's a race condition between the job completion callback and the
file descriptor cleanup. This can lead to accessing freed memory when
updating per-fd GPU stats, such as the following example:
[56120.512903] Unable to handle kern
Each V3D queue works independently and all the dependencies between the
jobs are handled through the DRM scheduler. Therefore, there is no need
to use one single lock for all queues. Using it, creates unnecessary
contention between different queues that can operate independently.
Replace the globa
Instead of storing the queue's active job in four different variables,
store the active job inside the queue's state. This way, it's possible
to access all active jobs using an index based in `enum v3d_queue`.
Signed-off-by: Maíra Canal
---
drivers/gpu/drm/v3d/v3d_drv.h | 8 ++
drivers/gp
Instead of storing a pointer to the DRM file data, store a pointer
directly to the private V3D file struct.
Signed-off-by: Maíra Canal
---
drivers/gpu/drm/v3d/v3d_drv.h| 4 ++--
drivers/gpu/drm/v3d/v3d_sched.c | 10 +-
drivers/gpu/drm/v3d/v3d_submit.c | 2 +-
3 files changed, 8 in
This patch series was initially motivated by a race condition (exposed
in PATCH 4/6) where we lacked synchronization for `job->file` access.
This led to use-after-free issues when a file descriptor was closed
while a job was still running.
However, beyond fixing this specific race, the series intr
], [4294967295, 13]]
is too long
from schema $id:
http://devicetree.org/schemas/display/sprd/sprd,sharkl3-dpu.yaml#
doc reference errors (make refcheckdocs):
See
https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20250719-ums9230-drm-v1-1-e4344a05e...@abscue.de
The base
On Thu, 10 Jul 2025 00:21:43 +0200, Sasha Finkelstein wrote:
> This patch series adds the DT bindings and tree entries for the GPU
> present in Apple M-series SoCs. The driver itself is in Rust and
> upstream is currently missing several prerequisite bindings, so will
> be sent later.
>
> The kern
On 7/19/25 5:10 AM, Felix Richter wrote:
Thanks for the reply.
I am aware that i can read and `edid` via sysfs from the drm device. I
did not know about `drm_info` but from a quick look at it I don't think
it provides the information I need.
The problem is not that I need more information
/sprd_dsi.h| 17 +-
11 files changed, 247 insertions(+), 105 deletions(-)
---
base-commit: d086c886ceb9f59dea6c3a9dae7eb89e780a20c9
change-id: 20250719-ums9230-drm-eb271289bfcd
Best regards,
--
Otto Pflüger
Set up the internal fbdev client in the Unisoc DRM driver. This is
needed to make the framebuffer console work.
Signed-off-by: Otto Pflüger
---
drivers/gpu/drm/sprd/sprd_drm.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/gpu/drm/sprd/sprd_drm.c b/drivers/gpu/drm/sprd/sprd_drm
Newer DPU revisions such as the one used in UMS9230 (version 5) do not
have internal MMU registers and also require different defaults for the
display interface configuration.
Check the DPU version register to account for these configuration
differences.
Signed-off-by: Otto Pflüger
---
drivers/
The drm_of_component_probe function is intended to bind all devices in
an OF graph given a set of ports linked using the "ports" property on a
main device node. This means that it should also bind the components
providing these ports, not just the components of other ports connected
to them. In ord
If a panel needs to send DSI commands during initialization, it sets the
prepare_prev_first flag, which allows the DSI host to initialize itself
before the panel's prepare function is called. To support this, the DSI
host must register a bridge and perform the necessary initialization
steps in its
Add a DSI output port and include common DSI controller bindings in the
bindings for the Unisoc DSI controller.
Signed-off-by: Otto Pflüger
---
.../display/sprd/sprd,sharkl3-dsi-host.yaml| 27 --
1 file changed, 20 insertions(+), 7 deletions(-)
diff --git
a/Document
When compile-testing this driver with all other drivers disabled,
sprd_dsi.c fails to compile due to a missing definition of struct
regmap_bus. Ensure that this does not happen by declaring the
compile-time dependency on regmap in Kconfig.
Signed-off-by: Otto Pflüger
---
drivers/gpu/drm/sprd/Kco
Enable the DPU and DSI gate clocks specified in the device tree.
Disable the DSI clock when it is not needed.
Signed-off-by: Otto Pflüger
---
drivers/gpu/drm/sprd/sprd_dpu.c | 7 +++
drivers/gpu/drm/sprd/sprd_dpu.h | 1 +
drivers/gpu/drm/sprd/sprd_dsi.c | 10 ++
drivers/gpu/drm/spr
Move platform-specific PLL parameters to the device tree match data and
add the parameters for UMS9230.
Signed-off-by: Otto Pflüger
---
drivers/gpu/drm/sprd/megacores_pll.c | 21 -
drivers/gpu/drm/sprd/sprd_dsi.c | 21 -
drivers/gpu/drm/sprd/sprd_dsi.
These callbacks are now required to be NULL and trigger a runtime
warning if they are present.
Signed-off-by: Otto Pflüger
---
drivers/gpu/drm/sprd/sprd_dpu.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpu/drm/sprd/sprd_dpu.c b/drivers/gpu/drm/sprd/sprd_dpu.c
index
a3447622a33
When the Unisoc DRM driver is initialized for the first time to display
an image on the screen, reinitialize the display properly instead of
relying on the bootloader.
Signed-off-by: Otto Pflüger
---
drivers/gpu/drm/sprd/sprd_dpu.c | 8
drivers/gpu/drm/sprd/sprd_dsi.c | 1 -
2 files cha
Add the compatible strings for the display controller found in the
UMS9230 SoC and bindings for a gate clock. Add IOMMU-related bindings
to the display-subsystem node.
Signed-off-by: Otto Pflüger
---
.../bindings/display/sprd/sprd,display-subsystem.yaml | 11 +++
.../bindings/display/sp
Correct the initialization code to treat the hs_rate and lp_rate values
as hertz instead of kilohertz. While at it, fix a bit operation bug in
the PLL initialization code which caused a PLL register to be set to
zero instead of the desired value.
Signed-off-by: Otto Pflüger
---
drivers/gpu/drm/s
On Wed, Jul 09, 2025 at 04:08:36PM +0200, Loic Poulain wrote:
> To configure and enable the DSI PHY PLL clocks, the MDSS AHB clock must
> be active for MMIO operations. Typically, this AHB clock is enabled as
> part of the DSI PHY interface enabling (dsi_phy_enable_resource).
>
> However, since th
The bridge used in drm_bridge_connector_init() for CEC init does not
correctly point to the required HDMI CEC bridge, which can lead to
errors during CEC initialization.
Fixes: 65a2575a68e4 ("drm/display: bridge-connector: hook in CEC notifier
support")
Fixes: a74288c8ded7 ("drm/display: bridge-c
On Fri, Jul 18, 2025 at 02:26:17PM +0800, Chaoyi Chen wrote:
> From: Chaoyi Chen
>
> This patch add support for get PHY lane info and handle HPD state
> without help of extcon.
>
> There is no extcon needed if the Type-C controller is present. In this
> case, cdn_dp_hpd_notify() will handle HPD
On Fri, Jul 18, 2025 at 02:26:19PM +0800, Chaoyi Chen wrote:
> From: Chaoyi Chen
>
> The RK3399 EVB IND board has a Type-C interface DisplayPort.
> It use fusb302 chip as Type-C controller.
>
> fusb302 chip ---> USB/DP PHY0 <> CDN-DP controller
>
> Signed-off-by: Chaoyi Chen
> ---
>
> Cha
On Sat, Jul 19, 2025 at 02:26:35AM -0600, Brigham Campbell wrote:
> Create mipi_dsi_dual, mipi_dsi_dual_dcs_write_seq_multi, and
> mipi_dsi_dual_generic_write_seq_multi macros for panels which are driven
> by two parallel serial interfaces. This allows for the reduction of code
> duplication in dri
On Mon, Jul 07, 2025 at 02:18:05PM +0800, Jun Nie wrote:
> Currently, SSPPs are assigned to a maximum of two pipes. However,
> quad-pipe usage scenarios require four pipes and involve configuring
> two stages. In quad-pipe case, the first two pipes share a set of
> mixer configurations and enable m
Thanks for the reply.
I am aware that i can read and `edid` via sysfs from the drm device. I
did not know about `drm_info` but from a quick look at it I don't think
it provides the information I need.
The problem is not that I need more information about the attached
display. The problem is
On Mon, Jul 07, 2025 at 09:58:30PM +0530, Jyothi Kumar Seerapu wrote:
>
>
> On 7/4/2025 1:11 AM, Dmitry Baryshkov wrote:
> > On Thu, 3 Jul 2025 at 15:51, Jyothi Kumar Seerapu
> > wrote:
> > >
> > >
> > >
> > > On 6/19/2025 9:46 PM, Jyothi Kumar Seerapu wrote:
> > > >
> > > >
> > > > On 6/18
On Wed, Jul 09, 2025 at 11:13:49AM +0530, Ekansh Gupta wrote:
>
>
> On 6/12/2025 3:54 PM, Dmitry Baryshkov wrote:
> > On Thu, Jun 12, 2025 at 03:02:52PM +0530, Ekansh Gupta wrote:
> >>
> >> On 6/12/2025 1:35 PM, Dmitry Baryshkov wrote:
> >>> On Thu, Jun 12, 2025 at 10:50:10AM +0530, Ekansh Gupta
On Wed, Jul 09, 2025 at 05:16:02PM +0800, Xiangxu Yin wrote:
>
>
> On 5/28/2025 4:49 AM, Konrad Dybcio wrote:
> > On 12/3/24 3:07 PM, Dmitry Baryshkov wrote:
> >> On Tue, Dec 03, 2024 at 04:13:22PM +0800, Xiangxu Yin wrote:
> >>>
> >>>
> >>> On 11/29/2024 9:53 PM, Dmitry Baryshkov wrote:
> O
On Qualcomm SA8775P and X1E80100 the DP controller might be driving
either a DisplayPort or a eDP sink (depending on the PHY that is tied to
the controller). Reflect that in the schema.
Signed-off-by: Dmitry Baryshkov
---
Jessica, your X1E8 patch also triggers warnings for several X1E8-based
l
Fix bug in unprepare() which causes the function's return value to be
that of the last mipi "enter sleep mode" command.
Update driver to use the "multi" variant of MIPI functions in order to
facilitate improved error handling and remove the panel's dependency on
deprecated MIPI functions.
Use the
On Fri, Jul 18, 2025 at 05:16:56PM -0700, Jessica Zhang wrote:
>
>
> On 7/18/2025 2:13 AM, Dmitry Baryshkov wrote:
> > On Thu, Jul 17, 2025 at 04:28:43PM -0700, Jessica Zhang wrote:
> > > From: Abhinav Kumar
> >
> > Please fix the patch subject.
>
> Hi Dmitry,
>
> Ack.
>
> >
> > >
> > > Ad
From: Zhang Enpei
Use ERR_CAST() since the macro clearly indicates that this is a pointer
to an error value and a type conversion was performed.
Signed-off-by: Zhang Enpei
---
drivers/gpu/drm/bridge/panel.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/bri
Update TODO item from drm documentation to contain more applicable
information regarding the removal of deprecated MIPI DSI functions and
no longer reference functions which have already been removed from the
kernel.
Reviewed-by: Douglas Anderson
Signed-off-by: Brigham Campbell
---
Documentatio
Remove the deprecated mipi_dsi_generic_write_seq() and
mipi_dsi_generic_write_chatty() functions now that they are no longer
used.
Reviewed-by: Douglas Anderson
Signed-off-by: Brigham Campbell
---
drivers/gpu/drm/drm_mipi_dsi.c | 34 +++---
include/drm/drm_mipi_dsi.h
This series removes the unintuitive mipi_dsi_generic_write_seq() macro
and related mipi_dsi_generic_write_chatty() method from the drm
subsystem. This is in accordance with a TODO item from Douglas Anderson
in the drm subsystem documentation. Tejas Vipin (among others) has
largely spearheaded this
Create mipi_dsi_dual, mipi_dsi_dual_dcs_write_seq_multi, and
mipi_dsi_dual_generic_write_seq_multi macros for panels which are driven
by two parallel serial interfaces. This allows for the reduction of code
duplication in drivers for these panels.
Signed-off-by: Brigham Campbell
---
mipi_dsi_dua
hy-Support-mode-switch/20250718-142814
base: next-20250717
patch link:https://lore.kernel.org/r/20250718062619.99-3-kernel%40airkyi.com
patch subject: [PATCH v2 2/5] phy: rockchip: phy-rockchip-typec: Add
typec_mux/typec_switch support
config: arm64-randconfig-004-20250719
(https://download.0
-base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Luiz-Otavio-Mello/drm-i915-move-struct_mutex-from-drm_device-to-drm_i915_private/20250719-035710
base: linus/master
patch link:
https://lore.
89 matches
Mail list logo
