Hi,
> -Original Message-
> From: Andi Shyti
> Sent: Tuesday, July 16, 2024 3:44 AM
> To: Gote, Nitin R
> Cc: Vivi, Rodrigo ; Cavitt, Jonathan
> ; Wilson, Chris P ;
> tursu...@ursulin.net; intel-...@lists.freedesktop.org; dri-
> de...@lists.freedesktop.org; Das, Nirmoy ;
> janusz.krzyszto
I just research the udmabuf, Please correct me if I'm wrong.
在 2024/7/15 20:32, Christian König 写道:
Am 15.07.24 um 11:11 schrieb Daniel Vetter:
On Thu, Jul 11, 2024 at 11:00:02AM +0200, Christian König wrote:
Am 11.07.24 um 09:42 schrieb Huan Yang:
Some user may need load file into dma-buf, c
On Thursday, June 13, 2024 11:40:16 AM EDT Jocelyn Falempe wrote:
> The race condition between fbcon and drm_panic can only occurs if
> VT_CONSOLE is set. So update drm_panic dependency accordingly.
> This will make it easier for Linux distributions to enable drm_panic
> by disabling VT_CONSOLE, an
https://bugzilla.kernel.org/show_bug.cgi?id=201497
--- Comment #31 from gabriel barros (gabrielbarro...@gmail.com) ---
Created attachment 306574
--> https://bugzilla.kernel.org/attachment.cgi?id=306574&action=edit
6.9.9 kernel logs, rebooting with monitor connected.
--
You may reply to this em
https://bugzilla.kernel.org/show_bug.cgi?id=201497
--- Comment #30 from gabriel barros (gabrielbarro...@gmail.com) ---
Created attachment 306573
--> https://bugzilla.kernel.org/attachment.cgi?id=306573&action=edit
kernel logs, failure when attaching HDMI cable to long running system
Adding to C
https://bugzilla.kernel.org/show_bug.cgi?id=201497
gabriel barros (gabrielbarro...@gmail.com) changed:
What|Removed |Added
CC||gabrielbarro.
Hi Ian,
On 7/15/2024 12:32 PM, Ian Forbes wrote:
> Hi Doug,
>
> Can you try this patch with 6.10.
>
> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c
> b/drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c
> index c45b4724e414..e20f64b67b26 100644
> --- a/drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c
> +++ b
On 6/21/2024 5:46 PM, john.c.harri...@intel.com wrote:
From: John Harrison
There is a new part to an existing workaround, so enable that piece as
well.
v2: Extend even further.
v3: Drop DG2 as there are CI failures still to resolve. Also re-order
the parameters to a function to reduce excess
On 6/21/2024 5:46 PM, john.c.harri...@intel.com wrote:
From: John Harrison
The context switch out workaround also applies to ARL.
Signed-off-by: John Harrison
LGTM,
Reviewed-by: Vinay Belgaumkar
---
drivers/gpu/drm/i915/gt/uc/intel_guc.c | 2 +-
drivers/gpu/drm/i915/gt/uc/intel
Hi,
On Fri, Jul 12, 2024 at 03:25:23PM +0200, Gote, Nitin R wrote:
> > -Original Message-
> > From: Vivi, Rodrigo
> > Sent: Thursday, July 11, 2024 11:39 PM
> > To: Cavitt, Jonathan
> > Cc: Gote, Nitin R ; Wilson, Chris P
> > ; tursu...@ursulin.net; intel-
> > g...@lists.freedesktop.org;
On 7/12/24 1:45 PM, Abhishek Tamboli wrote:
Add detail description for the read_mpcc_state function in the
mpc_funcs struct to resolve the documentation warning.
A kernel-doc warning was addressed:
./drivers/gpu/drm/amd/display/dc/inc/hw/mpc.h:547: warning:
Function parameter or struct member
On Tue, 16 Jul 2024 01:39:52 +0530, Aradhya Bhatia wrote:
> The DSS in AM625 SoC has 2 OLDI TXes. Refer the OLDI schema to add the
> support for the OLDI TXes.
>
> The AM625 DSS VP1 (port@0) can connect and control 2 OLDI TXes, to use
> them in dual-link or cloned single-link OLDI modes. Add sup
Reviewed-by: Aurabindo Pillai
On 7/12/24 1:45 PM, Abhishek Tamboli wrote:
Add detail description for the read_mpcc_state function in the
mpc_funcs struct to resolve the documentation warning.
A kernel-doc warning was addressed:
./drivers/gpu/drm/amd/display/dc/inc/hw/mpc.h:547: warning:
Functi
On Thu, Jul 11, 2024 at 3:02 AM Vladimir Lypak wrote:
>
> Fine grain preemption (switching from/to points within submits)
> requires extra handling in command stream of those submits, especially
> when rendering with tiling (using GMEM). However this handling is
> missing at this point in mesa (an
Hi Steven, thanks for the review.
On 13.06.2024 16:28, Steven Price wrote:
> On 06/06/2024 01:49, Adrián Larumbe wrote:
> > This patch series enables userspace utilities like gputop and nvtop to
> > query a render context's fdinfo file and figure out rates of engine
> > and memory utilisation.
> >
The OLDI (transmitters) TXes do not have registers of their own, and are
dependent on the source video-ports from the DSS to provide
configuration data. This hardware doesn't directly sit on the internal
bus of the SoC, but does so via the DSS. Hence, the OLDI TXes are
supposed to be child nodes un
The AM62x and AM62Px SoCs feature 2 OLDI TXes each, which makes it
possible to connect them in dual-link or cloned single-link OLDI display
modes. The current OLDI support in tidss_dispc.c can only support for
a single OLDI TX, connected to a VP and doesn't really support
configuration of OLDIs in
Reduce tab size from 8 spaces to 4 spaces to make the bindings
consistent, and easy to expand.
Acked-by: Rob Herring (Arm)
Reviewed-by: Laurent Pinchart
Reviewed-by: Tomi Valkeinen
Signed-off-by: Aradhya Bhatia
---
.../bindings/display/ti/ti,am65x-dss.yaml | 54 +--
1 file
The DSS in AM625 SoC has 2 OLDI TXes. Refer the OLDI schema to add the
support for the OLDI TXes.
The AM625 DSS VP1 (port@0) can connect and control 2 OLDI TXes, to use
them in dual-link or cloned single-link OLDI modes. Add support for an
additional endpoint under the port@0 to accurately depict
Hello all,
This patch series add support for the dual OLDI TXes supported in Texas
Instruments' AM62x and AM62Px family of SoCs. The OLDI TXes support
single-lvds, lvds-clone, and dual-lvds modes. These have now been
represented through DRM bridges within TI-DSS.
- Some history and hardware desc
On Tue, Jul 09, 2024 at 12:45:29PM +0200, Konrad Dybcio wrote:
> On recent (SM8550+) Snapdragon platforms, the GPU speed bin data is
> abstracted through SMEM, instead of being directly available in a fuse.
>
> Add support for SMEM-based speed binning, which includes getting
> "feature code" and "
On Mon, Jul 1, 2024 at 12:43 PM Dmitry Baryshkov
wrote:
>
> On Fri, Jun 28, 2024 at 02:48:47PM GMT, Abhinav Kumar wrote:
> > There is no recovery mechanism in place yet to recover from mmu
> > faults for DPU. We can only prevent the faults by making sure there
> > is no misconfiguration.
> >
> > R
Hi Doug,
Can you try this patch with 6.10.
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c
b/drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c
index c45b4724e414..e20f64b67b26 100644
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c
@@ -92,7 +92,7 @@ static in
On Mon, Jul 15, 2024 at 4:05 AM Łukasz Bartosik wrote:
>
> On Sat, Jul 13, 2024 at 11:45 PM wrote:
> >
> > On Fri, Jul 12, 2024 at 9:44 AM Łukasz Bartosik wrote:
> > >
> > > On Wed, Jul 3, 2024 at 12:14 AM wrote:
> > > >
> > > > On Tue, Jul 2, 2024 at 4:01 PM Luis Chamberlain
> > > > wrote:
>
Hi Sima!
>
> Yeah I'm not sure a partially converted driver where the main driver is
> still C really works, that pretty much has to throw out all the type
> safety in the interfaces.
>
> What I think might work is if such partial drivers register as full rust
> drivers, and then largely delega
If we try to use printk-based drm_printer, like drm_dbg_printer(),
output from drm_buddy_print() will be split into several lines:
[drm] chunk_size: 1024KiB, total: 7MiB, free: 7MiB, clear_free: 0MiB
[drm] order- 2
[drm] free:4 MiB
[drm] , blocks: 1
[drm] order- 1
[drm] free:
Hi,
On Fri, Jun 21, 2024 at 1:46 PM Doug Anderson wrote:
>
> Hi,
>
> On Fri, Jun 21, 2024 at 1:45 PM Douglas Anderson
> wrote:
> >
> > At shutdown if you've got a _properly_ coded DRM modeset driver then
> > you'll get these two warnings at shutdown time:
> >
> > Skipping disable of already d
On 15/07/2024 16:40, Doug Anderson wrote:
Hi,
On Mon, Jul 15, 2024 at 6:57 AM wrote:
On 15/07/2024 15:51, Doug Anderson wrote:
Hi,
On Mon, Jul 15, 2024 at 6:02 AM Neil Armstrong
wrote:
On 15/07/2024 14:54, Stephan Gerhold wrote:
On Mon, Jul 15, 2024 at 02:42:12PM +0200, Neil Armstrong w
On Mon, 15 Jul 2024 at 17:42, Maxime Ripard wrote:
>
> On Mon, Jul 08, 2024 at 11:29:46PM GMT, Dmitry Baryshkov wrote:
> > On Mon, Jul 08, 2024 at 04:59:23PM GMT, Maxime Ripard wrote:
> > > On Mon, Jul 01, 2024 at 05:36:18PM GMT, Marc Gonzalez wrote:
> > > > On 01/07/2024 15:50, Maxime Ripard wrot
On Mon, 15 Jul 2024 at 18:28, Conor Dooley wrote:
>
> On Mon, Jul 15, 2024 at 04:26:12PM +0100, Conor Dooley wrote:
> > On Mon, Jul 15, 2024 at 02:21:16PM +0200, Marc Gonzalez wrote:
> > > Current driver already supports the msm8998 HDMI TX.
> > > We just need to add the compatible string.
> >
> >
On Mon, Jul 15, 2024 at 03:27:33PM +0530, Manikandan Muralidharan wrote:
> + clocks:
> +items:
> + - description:
> + Peripheral clock for the hardware block functionality
> + - description:
> + Generic clock to drive the D-PHY PLL block
What is "generic" about thi
>-Original Message-
>From: dri-devel On Behalf Of Dave
>Airlie
>Sent: Monday, July 15, 2024 4:36 AM
>To: dri-devel@lists.freedesktop.org
>Subject: [PATCH] drm/test: fix the gem shmem test to map the sg table.
>
>From: Dave Airlie
>
>The test here creates an sg table, but never maps it, wh
Hi
Am 15.07.24 um 17:16 schrieb José Expósito:
Building with Sparse enabled prints this warning for cpu_to_le16()
calls:
warning: incorrect type in assignment (different base types)
expected unsigned short [usertype]
got restricted __le16 [usertype]
And this warning for
On Mon, Jul 15, 2024 at 02:15:37PM +0200, Stephan Gerhold wrote:
> The Samsung ATNA45AF01 panel is an AMOLED eDP panel that has backlight
> control over the DP AUX channel. While it works almost correctly with the
> generic "edp-panel" compatible, the backlight needs special handling to
> work corr
On Mon, Jul 15, 2024 at 04:26:12PM +0100, Conor Dooley wrote:
> On Mon, Jul 15, 2024 at 02:21:16PM +0200, Marc Gonzalez wrote:
> > Current driver already supports the msm8998 HDMI TX.
> > We just need to add the compatible string.
>
> Why is this required when the driver change suggests that this
On Fri, May 17, 2024 at 06:00:11PM +0200, Louis Chauvet wrote:
> > > > Hi Louis,
> > > >
> > > > If you could share a RFC/WIP series it would be awesome!
>
> Hi all!
>
> I just uploaded my WIP series to github here [1]. Most of the work is
> extracted from the current ConfigFS series, I just sp
On Mon, Jul 15, 2024 at 02:21:16PM +0200, Marc Gonzalez wrote:
> Current driver already supports the msm8998 HDMI TX.
> We just need to add the compatible string.
Why is this required when the driver change suggests that this device is
compatible with the existing 8974?
>
> Signed-off-by: Marc G
On Sun, Jul 14, 2024 at 09:41:10PM +0200, Thomas Zimmermann wrote:
> Hi
>
> Am 12.07.24 um 18:16 schrieb José Expósito:
> > Building with Sparse enabled prints this warning for cpu_to_le16()
> > calls:
> >
> > warning: incorrect type in assignment (different base types)
> > expected
Building with Sparse enabled prints this warning for cpu_to_le16()
calls:
warning: incorrect type in assignment (different base types)
expected unsigned short [usertype]
got restricted __le16 [usertype]
And this warning for le16_to_cpu() calls:
warning: cast to restricted
On Mon, Jul 08, 2024 at 11:29:46PM GMT, Dmitry Baryshkov wrote:
> On Mon, Jul 08, 2024 at 04:59:23PM GMT, Maxime Ripard wrote:
> > On Mon, Jul 01, 2024 at 05:36:18PM GMT, Marc Gonzalez wrote:
> > > On 01/07/2024 15:50, Maxime Ripard wrote:
> > >
> > > > On Thu, Jun 27, 2024 at 01:13:03PM GMT, Marc
Hi,
On Mon, Jul 15, 2024 at 6:57 AM wrote:
>
> On 15/07/2024 15:51, Doug Anderson wrote:
> > Hi,
> >
> > On Mon, Jul 15, 2024 at 6:02 AM Neil Armstrong
> > wrote:
> >>
> >> On 15/07/2024 14:54, Stephan Gerhold wrote:
> >>> On Mon, Jul 15, 2024 at 02:42:12PM +0200, Neil Armstrong wrote:
> On
On Thu, Jul 04, 2024 at 07:04:41PM GMT, Marc Gonzalez wrote:
> On 01/07/2024 15:50, Maxime Ripard wrote:
>
> > The i2c register access (and the whole behaviour of the device) is
> > constrained on the I2C_EN pin status, and you can't read it from the
> > device, so it's also something we need to h
On Mon, Jul 15, 2024 at 02:21:17PM GMT, Marc Gonzalez wrote:
> From: Arnaud Vrac
>
> Add support for the HDMI PHY as present on the Qualcomm MSM8998 SoC.
> This code is mostly copy & paste of the vendor code from msm-4.4
> kernel.lnx.4.4.r38-rel.
>
> Signed-off-by: Arnaud Vrac
> Signed-off-by:
On Mon, Jul 15, 2024 at 02:21:16PM GMT, Marc Gonzalez wrote:
> Current driver already supports the msm8998 HDMI TX.
> We just need to add the compatible string.
>
> Signed-off-by: Marc Gonzalez
> ---
> drivers/gpu/drm/msm/hdmi/hdmi.c | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Dmitr
Hi,
On Mon, Jul 15, 2024 at 7:31 AM Conor Dooley wrote:
>
> On Mon, Jul 15, 2024 at 07:22:30AM -0700, Doug Anderson wrote:
> > Hi,
> >
> > On Mon, Jul 15, 2024 at 12:32 AM Zhaoxiong Lv
> > wrote:
> > >
> > > The Elan ekth6a12nay touch screen chip same as Elan eKTH6915 controller
> > > has a rese
Hi,
On Mon, Jul 15, 2024 at 7:22 AM Doug Anderson wrote:
>
> Hi,
>
> On Mon, Jul 15, 2024 at 12:32 AM Zhaoxiong Lv
> wrote:
> >
> > The Elan ekth6a12nay touch screen chip same as Elan eKTH6915 controller
> > has a reset gpio. The difference is that they have different
> > post_power_delay_ms.
>
On Mon, Jul 15, 2024 at 07:22:30AM -0700, Doug Anderson wrote:
> Hi,
>
> On Mon, Jul 15, 2024 at 12:32 AM Zhaoxiong Lv
> wrote:
> >
> > The Elan ekth6a12nay touch screen chip same as Elan eKTH6915 controller
> > has a reset gpio. The difference is that they have different
> > post_power_delay_ms.
Hi,
On Mon, Jul 15, 2024 at 12:32 AM Zhaoxiong Lv
wrote:
>
> The Elan ekth6a12nay touch screen chip same as Elan eKTH6915 controller
> has a reset gpio. The difference is that they have different
> post_power_delay_ms.
>
> Signed-off-by: Zhaoxiong Lv
> Acked-by: Conor Dooley
FWIW things have c
Hi,
On Sun, Jul 14, 2024 at 8:18 PM Zhaoxiong Lv
wrote:
>
> The current driver can only obtain the porch parameters
> of boe-th101mb31ig002. Modify it to obtain the porch
> parameters of the panel currently being used.
>
> Zhaoxiong Lv (1):
> drm/panel: boe-th101mb31ig002 : Fix the way to get p
On 15/07/2024 15:51, Doug Anderson wrote:
Hi,
On Mon, Jul 15, 2024 at 6:02 AM Neil Armstrong
wrote:
On 15/07/2024 14:54, Stephan Gerhold wrote:
On Mon, Jul 15, 2024 at 02:42:12PM +0200, Neil Armstrong wrote:
On 15/07/2024 14:15, Stephan Gerhold wrote:
This reverts commit 8ebb1fc2e69ab8b89a
Am 15.07.24 um 15:51 schrieb Danilo Krummrich:
In commit 50c1a36f594b ("drm/gpuvm: track/lock/validate external/evicted
objects") we started using drm_exec, but did not select DRM_EXEC in the
Kconfig for DRM_GPUVM, fix this.
Cc: Christian König
Cc: Boris Brezillon
Cc: Thomas Hellström
Fixes:
In commit 50c1a36f594b ("drm/gpuvm: track/lock/validate external/evicted
objects") we started using drm_exec, but did not select DRM_EXEC in the
Kconfig for DRM_GPUVM, fix this.
Cc: Christian König
Cc: Boris Brezillon
Cc: Thomas Hellström
Fixes: 50c1a36f594b ("drm/gpuvm: track/lock/validate ext
Hi,
On Mon, Jul 15, 2024 at 6:02 AM Neil Armstrong
wrote:
>
> On 15/07/2024 14:54, Stephan Gerhold wrote:
> > On Mon, Jul 15, 2024 at 02:42:12PM +0200, Neil Armstrong wrote:
> >> On 15/07/2024 14:15, Stephan Gerhold wrote:
> >>> This reverts commit 8ebb1fc2e69ab8b89a425e402c7bd85e053b7b01.
> >>>
Hi,
On 7/15/24 6:57 AM, Philip Mueller wrote:
> This adds a DMI orientation quirk for the OrangePi Neo Linux Gaming Handheld.
>
> Signed-off-by: Philip Mueller
Thanks, patch looks good to me:
Reviewed-by: Hans de Goede
I have pushed this to drm-misc-fixes now.
Regards,
Hans
> ---
> dri
Hi,
On Mon, Jul 15, 2024 at 5:16 AM Stephan Gerhold
wrote:
>
> This is needed for the display panel to work on the Qualcomm
> sc7180-trogdor-homestar and x1e80100-crd.
>
> Signed-off-by: Stephan Gerhold
> ---
> arch/arm64/configs/defconfig | 1 +
> 1 file changed, 1 insertion(+)
I'd assume tha
Hi,
Reviewed-by: Douglas Anderson
On Mon, Jul 15, 2024 at 5:16 AM Stephan Gerhold
wrote:
>
> The Samsung ATNA45AF01 panel is an AMOLED eDP panel that has backlight
> control over the DP AUX channel. While it works almost correctly with the
> generic "edp-panel" compatible, the backlight needs
On Mon, Jul 15, 2024 at 7:49 AM Markus Elfring wrote:
>
> From: Markus Elfring
> Date: Mon, 15 Jul 2024 13:36:54 +0200
>
> Single characters should be put into a sequence.
> Thus use the corresponding function “seq_putc” for one selected call.
>
> This issue was transformed by using the Coccinell
On Mon, Jul 15, 2024 at 03:01:57PM +0200, Neil Armstrong wrote:
> On 15/07/2024 14:54, Stephan Gerhold wrote:
> > On Mon, Jul 15, 2024 at 02:42:12PM +0200, Neil Armstrong wrote:
> > > On 15/07/2024 14:15, Stephan Gerhold wrote:
> > > > This reverts commit 8ebb1fc2e69ab8b89a425e402c7bd85e053b7b01.
>
On Mon, Jul 15, 2024 at 02:54:59PM +0200, Stephan Gerhold wrote:
> On Mon, Jul 15, 2024 at 02:42:12PM +0200, Neil Armstrong wrote:
> > How will we handle current/old crd DT with new kernels ?
>
> I think this is answered in the commit message:
>
> > > We have existing users of this panel through
On 15/07/2024 14:54, Stephan Gerhold wrote:
On Mon, Jul 15, 2024 at 02:42:12PM +0200, Neil Armstrong wrote:
On 15/07/2024 14:15, Stephan Gerhold wrote:
This reverts commit 8ebb1fc2e69ab8b89a425e402c7bd85e053b7b01.
The panel should be handled through the samsung-atna33xc20 driver for
correct po
On Mon, Jul 15, 2024 at 02:42:12PM +0200, Neil Armstrong wrote:
> On 15/07/2024 14:15, Stephan Gerhold wrote:
> > This reverts commit 8ebb1fc2e69ab8b89a425e402c7bd85e053b7b01.
> >
> > The panel should be handled through the samsung-atna33xc20 driver for
> > correct power up timings. Otherwise the
Hi,
On 15/07/2024 14:15, Stephan Gerhold wrote:
This reverts commit 8ebb1fc2e69ab8b89a425e402c7bd85e053b7b01.
The panel should be handled through the samsung-atna33xc20 driver for
correct power up timings. Otherwise the backlight does not work correctly.
We have existing users of this panel th
On 15/07/2024 14:15, Stephan Gerhold wrote:
The Samsung ATNA45AF01 panel is an AMOLED eDP panel that has backlight
control over the DP AUX channel. While it works almost correctly with the
generic "edp-panel" compatible, the backlight needs special handling to
work correctly. It is similar to the
On Mon, Jul 15, 2024 at 02:15:40PM +0200, Stephan Gerhold wrote:
> This is needed for the display panel to work on the Qualcomm
> sc7180-trogdor-homestar and x1e80100-crd.
>
> Signed-off-by: Stephan Gerhold
Reviewed-by: Johan Hovold
On Mon, Jul 15, 2024 at 02:15:39PM +0200, Stephan Gerhold wrote:
> The backlight does not work correctly with the current display panel
> configuration: It works after boot, but once the display gets disabled it
> is not possible to get it back on. It turns out that the ATNA45AF01 panel
> needs exa
Am 15.07.24 um 11:11 schrieb Daniel Vetter:
On Thu, Jul 11, 2024 at 11:00:02AM +0200, Christian König wrote:
Am 11.07.24 um 09:42 schrieb Huan Yang:
Some user may need load file into dma-buf, current
way is:
1. allocate a dma-buf, get dma-buf fd
2. mmap dma-buf fd into vaddr
3. read
On Mon, Jul 15, 2024 at 02:15:38PM +0200, Stephan Gerhold wrote:
> This reverts commit 8ebb1fc2e69ab8b89a425e402c7bd85e053b7b01.
>
> The panel should be handled through the samsung-atna33xc20 driver for
> correct power up timings. Otherwise the backlight does not work correctly.
>
> We have exist
HDMI PHY block embedded in the APQ8098.
Acked-by: Rob Herring (Arm)
Acked-by: Vinod Koul
Signed-off-by: Marc Gonzalez
---
Documentation/devicetree/bindings/phy/qcom,hdmi-phy-qmp.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/phy/qcom,hdmi-phy-qmp.yam
From: Arnaud Vrac
Port device nodes from vendor code.
Signed-off-by: Arnaud Vrac
Reviewed-by: Dmitry Baryshkov
Signed-off-by: Marc Gonzalez
---
arch/arm64/boot/dts/qcom/msm8998.dtsi | 100 +-
1 file changed, 99 insertions(+), 1 deletion(-)
diff --git a/arch/a
Current driver already supports the msm8998 HDMI TX.
We just need to add the compatible string.
Signed-off-by: Marc Gonzalez
---
drivers/gpu/drm/msm/hdmi/hdmi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/msm/hdmi/hdmi.c b/drivers/gpu/drm/msm/hdmi/hdmi.c
index 24abcb7254c
From: Arnaud Vrac
Add support for the HDMI PHY as present on the Qualcomm MSM8998 SoC.
This code is mostly copy & paste of the vendor code from msm-4.4
kernel.lnx.4.4.r38-rel.
Signed-off-by: Arnaud Vrac
Signed-off-by: Marc Gonzalez
---
drivers/gpu/drm/msm/Makefile | 1 +
d
HDMI TX block embedded in the APQ8098.
Reviewed-by: Rob Herring (Arm)
Reviewed-by: Conor Dooley
Signed-off-by: Marc Gonzalez
---
.../devicetree/bindings/display/msm/hdmi.yaml | 28 --
1 file changed, 26 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetr
MSM8998 GPIO pin controller reference design defines:
- CEC: pin 31
- DDC: pin 32,33
- HPD: pin 34
Downstream vendor code for reference:
https://git.codelinaro.org/clo/la/kernel/msm-4.4/-/blob/caf_migration/kernel.lnx.4.4.r38-rel/arch/arm/boot/dts/qcom/msm8998-pinctrl.dtsi#L2324-2400
mdss_hdmi_
DT bits required for HDMI TX support in qcom APQ8098 (MSM8998 cousin)
---
Changes in v6:
- Fold HDMI PHY driver submission into this series
=> [PATCH v2] drm/msm: add msm8998 hdmi phy/pll support
=> Link to v2:
https://lore.kernel.org/all/20240704-hdmi-phy-v2-1-a7f5af202...@freebox.fr/
-
This is needed for the display panel to work on the Qualcomm
sc7180-trogdor-homestar and x1e80100-crd.
Signed-off-by: Stephan Gerhold
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 7d32fca6499
The Samsung ATNA45AF01 panel is an AMOLED eDP panel that has backlight
control over the DP AUX channel. While it works almost correctly with the
generic "edp-panel" compatible, the backlight needs special handling to
work correctly. It is similar to the existing ATNA33XC20 panel, just with
a larger
The backlight does not work correctly with the current display panel
configuration: It works after boot, but once the display gets disabled it
is not possible to get it back on. It turns out that the ATNA45AF01 panel
needs exactly the same non-standard power sequence as implemented by the
panel-sam
This reverts commit 8ebb1fc2e69ab8b89a425e402c7bd85e053b7b01.
The panel should be handled through the samsung-atna33xc20 driver for
correct power up timings. Otherwise the backlight does not work correctly.
We have existing users of this panel through the generic "edp-panel"
compatible (e.g. the
The backlight of the Samsung ATNA45AF01 panel used in the Qualcomm X1E80100
CRD does not work correctly with the current display panel configuration
and drivers: It works after boot, but once the display gets disabled it is
not possible to get it back on. It turns out that the ATNA45AF01 panel
need
Hey,
Den 2024-07-15 kl. 06:21, skrev Golani, Mitulkumar Ajitkumar:
>
> On 15-07-2024 04:42, Stephen Rothwell wrote:
>> Hi all,
>>
>> On Wed, 12 Jun 2024 14:11:10 +1000 Stephen Rothwell
>> wrote:
>>> After merging the drm-intel tree, today's linux-next build (htmldocs)
>>> produced this warning:
From: Markus Elfring
Date: Mon, 15 Jul 2024 13:36:54 +0200
Single characters should be put into a sequence.
Thus use the corresponding function “seq_putc” for one selected call.
This issue was transformed by using the Coccinelle software.
Suggested-by: Christophe Jaillet
Signed-off-by: Markus
On Mon, 15 Jul 2024 at 06:19, Zhaoxiong Lv
wrote:
>
> The current driver can only obtain the porch parameters
> of boe-th101mb31ig002. Modify it to obtain the porch
> parameters of the panel currently being used.
>
> Fixes: 24179ff9a2e4524 ("drm/panel: boe-th101mb31ig002 : Make it compatible
> wi
From: Markus Elfring
Date: Mon, 15 Jul 2024 13:12:10 +0200
Single characters should be put into a sequence.
Thus use the corresponding function “seq_putc” for one selected call.
This issue was transformed by using the Coccinelle software.
Suggested-by: Christophe Jaillet
Signed-off-by: Markus
On Wed, Jul 10, 2024 at 02:40:04PM +0200, Christian König wrote:
> Am 10.07.24 um 13:58 schrieb Daniel Vetter:
> > On Wed, 10 Jul 2024 at 13:39, Christian König
> > wrote:
> > > Am 10.07.24 um 11:31 schrieb Daniel Vetter:
> > > > We already teach lockdep that dma_resv nests within drm_modeset_loc
On Sat, Jul 13, 2024 at 11:45 PM wrote:
>
> On Fri, Jul 12, 2024 at 9:44 AM Łukasz Bartosik wrote:
> >
> > On Wed, Jul 3, 2024 at 12:14 AM wrote:
> > >
> > > On Tue, Jul 2, 2024 at 4:01 PM Luis Chamberlain wrote:
> > > >
> > > > On Tue, Jul 02, 2024 at 03:56:50PM -0600, Jim Cromie wrote:
> > >
Hi Tomi,
Thank you for reviewing the patches!
On 27/06/24 18:41, Tomi Valkeinen wrote:
> On 11/05/2024 22:30, Aradhya Bhatia wrote:
>> Up till now, the OLDI support in tidss was integrated within the tidss
>> dispc.
>> This was fine till the OLDI was one-to-mapped with the DSS video-port
>> (VP).
Enable the Microchip's DSI controller wrapper driver that uses
the Synopsys DesignWare MIPI DSI host controller bridge.
Signed-off-by: Manikandan Muralidharan
---
arch/arm/configs/at91_dt_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/at91_dt_defconfig
b/arch/arm
Add the Microchip's DSI controller wrapper driver that uses the
Synopsys DesignWare MIPI DSI host controller bridge for the SAM9X7
SoC series to the MAINTAINERS entry.
Signed-off-by: Manikandan Muralidharan
---
changes in v3:
- Drop T: section
---
MAINTAINERS | 7 +++
1 file changed, 7 inse
Add the Microchip's DSI controller wrapper driver that uses
the Synopsys DesignWare MIPI DSI host controller bridge.
Signed-off-by: Manikandan Muralidharan
---
changes in v2:
- use static const with global variables
- replace dev_err with dev_err_probe
- move clk_prepare_enable to simplify the er
Add the 'sam9x75-mipi-dsi' compatible binding, which describes the
Microchip's specific wrapper for the Synopsys DesignWare MIPI DSI HOST
Controller for the sam9x75 series System-on-Chip (SoC) devices.
Signed-off-by: Manikandan Muralidharan
---
changes in v2:
- List the clocks with description
-
This patch series adds support for the Microchip's MIPI DSI Controller
wrapper driver that uses the Synopsys DesignWare MIPI DSI host controller
bridge for SAM9X75 SoC series.
Changelogs are available in respective patches.
Manikandan Muralidharan (4):
dt-bindings: display: bridge: add sam9x75-
Ast's BMC connector tracks the status of an underlying physical
connector and set BMC status accordingly. This functionality has
been moved into probe helpers. The BMC is always connected and the
helpers compute the correct status. Hence, remove the driver's
dedicated code.
Signed-off-by: Thomas Z
Call drm_probe_helper_prioritize_connectors() to set connector
priorities. Guarantees that only a single output is connected at a
time.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/mgag200/mgag200_g200eh.c | 2 ++
drivers/gpu/drm/mgag200/mgag200_g200eh3.c | 2 ++
drivers/gpu/drm/mgag200
Mgag200's BMC connector tracks the status of an underlying physical
connector and set BMC status accordingly. This functionality has
been moved into probe helpers. The BMC is always connected and the
helpers compute the correct status. Hence, remove the driver's
dedicated code.
Signed-off-by: Thom
AST2600 can host VGA and DisplayPort outputs. Support both on the
same device. As userspace can often only support a single output per
CRTC, connectors are prioritized against each other by the probe
helpers.
Reported-by: Shixiong Ou
Closes:
https://lore.kernel.org/dri-devel/20240711090102.35221
Call drm_probe_helper_prioritize_connectors() to set connector
priorities. Guarantees that only a single output is connected at a
time.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/ast/ast_mode.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/ast/ast_mode.c b/driv
Move the logic to call the connector's detect helper into a single
internal function. Reduces code dupliction.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/drm_probe_helper.c | 33 +++---
1 file changed, 17 insertions(+), 16 deletions(-)
diff --git a/drivers/gpu/
For CRTCs with multiple outputs (i.e., encoders plus connectors),
only report at most a single connected output to userspace. Make
this configurable via CONFIG_DRM_REPORT_SINGLE_CONNECTED_CRTC_OUTPUT.
Having multiple connected outputs on the same CRTC complicates
display-mode and format selection,
Old or simple hardware only supports a single CRTC with multiple
conenctoed outputs. This breaks most userspace compositors, which
only support a single output per CRTC. This currently happens with
ast and mgag200 drivers. The drivers contain a work around that
dynamically disables all but one conn
Applied to drm-misc-next
On 09.07.2024 13:54, Alexander F. Lent wrote:
> Modules that load firmware from various paths at runtime must declare
> those paths at compile time, via the MODULE_FIRMWARE macro, so that the
> firmware paths are included in the module's metadata.
>
> The accel/ivpu drive
1 - 100 of 125 matches
Mail list logo
