Hi Christian,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-xe/drm-xe-next]
[also build test WARNING on drm/drm-next drm-exynos/exynos-drm-next
linus/master drm-intel/for-linux-next drm-intel/for-linux-next-fixes
drm-misc/drm-misc-next drm-tip/drm-tip v
Hi Arnd,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-exynos/exynos-drm-next]
[also build test ERROR on next-20241115]
[cannot apply to linus/master v6.12-rc7]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch,
Hi Pierre-Eric,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-xe/drm-xe-next]
[also build test ERROR on next-20241115]
[cannot apply to linus/master drm-misc/drm-misc-next v6.12-rc7]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And
Hi Pierre-Eric,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-xe/drm-xe-next]
[also build test ERROR on next-20241115]
[cannot apply to linus/master drm-misc/drm-misc-next v6.12-rc7]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And
Hi Jonas,
On 11/16/24 9:12 PM, Jonas Karlman wrote:
> Hi Cristian,
>
> On 2024-11-16 19:22, Cristian Ciocaltea wrote:
>> The RK3588 specific implementation is currently quite limited in terms
>> of handling the full range of display modes supported by the connected
>> screens, e.g. 2560x1440@75Hz
The pull request you sent on Sun, 17 Nov 2024 08:17:17 +1000:
> https://gitlab.freedesktop.org/drm/kernel.git tags/drm-fixes-2024-11-17
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e06bc45bef9aca52c6bdcb56aa6d392d99516ac3
Thank you!
--
Deet-doot-dot, I am a bot.
h
From: Luan Arcanjo
All dce command_table_helper's shares a copy-pasted collection
of copy-pasted functions, which are: phy_id_to_atom,
clock_source_id_to_atom_phy_clk_src_id, and engine_bp_to_atom.
This patch removes the multiple copy-pasted by creating a
common command table and make the comman
Hi Linus,
Alex sent on a last minute revert for a regression found with swsmu
patch for final,
Regards,
Dave.
drm-fixes-2024-11-17:
drm/amdgpu regression fix for 6.12-rc8
amdgpu:
- revert patch to fix swsmu regression
The following changes since commit 21c1c6c7d732c2f6f4c5ffc77e103aa3ae8bff1d:
Hi Cristian,
On 2024-11-16 19:22, Cristian Ciocaltea wrote:
> The RK3588 specific implementation is currently quite limited in terms
> of handling the full range of display modes supported by the connected
> screens, e.g. 2560x1440@75Hz, 2048x1152@60Hz, 1024x768@60Hz are just a
> few of them.
>
>
+ dri-devel
On 16.11.2024 03:12, Tomasz Lis wrote:
> Benefits of drm_mm_for_each_node_safe and drm_mm_for_each_node_in_range
> squished together into one macro.
>
> Signed-off-by: Tomasz Lis
> ---
> include/drm/drm_mm.h | 19 +++
> 1 file changed, 19 insertions(+)
>
> diff --gi
VOP2 on RK3588 is able to use the HDMI PHY PLL as an alternative and
more accurate pixel clock source to improve handling of display modes up
to 4K@60Hz on video ports 0, 1 and 2.
For now only HDMI0 output is supported, hence add the related PLL clock.
Signed-off-by: Cristian Ciocaltea
---
arch
The if_pixclk_rate variable is not being used outside of the if-block in
rk3588_calc_cru_cfg(), hence move the superfluous assignment from the
first branch to the inner comment-block.
Signed-off-by: Cristian Ciocaltea
---
drivers/gpu/drm/rockchip/rockchip_drm_vop2.c | 2 +-
1 file changed, 1 ins
kchip/rockchip_drm_vop2.c | 36 +-
3 files changed, 44 insertions(+), 3 deletions(-)
---
base-commit: 744cf71b8bdfcdd77aaf58395e068b7457634b2c
change-id: 20241116-vop2-hdmi0-disp-modes-b39e3619768f
On RK3588, HDMI PHY PLL can be used as an alternative and more accurate
pixel clock source for VOP2 video ports 0, 1 and 2.
Document the optional PLL clock properties corresponding to the two HDMI
PHYs available on the SoC.
Signed-off-by: Cristian Ciocaltea
---
Documentation/devicetree/bindings
Since commit c4b09c562086 ("phy: phy-rockchip-samsung-hdptx: Add clock
provider support"), the HDMI PHY PLL can be used as an alternative and
more accurate pixel clock source for VOP2 to improve display modes
handling on RK3588 SoC.
Add the missing #clock-cells property to allow using the clock pr
The RK3588 specific implementation is currently quite limited in terms
of handling the full range of display modes supported by the connected
screens, e.g. 2560x1440@75Hz, 2048x1152@60Hz, 1024x768@60Hz are just a
few of them.
Additionally, it doesn't cope well with non-integer refresh rates like
5
Hi Biju,
Thank you for the patch.
On Sat, Nov 16, 2024 at 12:54:10PM +, Biju Das wrote:
> The host_node pointer was assigned and freed in adv7533_parse_dt(), and
> later, adv7533_attach_dsi() used the same. Fix this use-after-free issue
> with the below changes:
>
> 1. Drop host_node from s
Hi Dave, Simona,
One last minute patch to fix a regression.
The following changes since commit 7013a8268d311fded6c7a6528fc1de82668e75f6:
drm/amd: Fix initialization mistake for NBIO 7.7.0 (2024-11-12 17:37:39 -0500)
are available in the Git repository at:
https://gitlab.freedesktop.org/agd
It turns out that the fixup from vlv_fixup_mipi_sequences() is necessary
for some DSI panel's with version 2 mipi-sequences too.
Specifically the Acer Iconia One 8 A1-840 (not to be confused with the
A1-840FHD which is different) has the following sequences:
BDB block 53 (1284 bytes) - MIPI seque
As per [1] and [2], ADV7535/7533 supports only 2-, 3-, or 4-lane. Drop
unsupported 1-lane.
[1]
https://www.analog.com/media/en/technical-documentation/data-sheets/ADV7535.pdf
[2]
https://www.analog.com/media/en/technical-documentation/data-sheets/ADV7533.pdf
Fixes: 1e4d58cd7f88 ("drm/bridge: ad
The host_node pointer was assigned and freed in adv7533_parse_dt(), and
later, adv7533_attach_dsi() used the same. Fix this use-after-free issue
with the below changes:
1. Drop host_node from struct adv7511 and instead use a local pointer in
adv7511_probe().
2. Update adv7533_parse_dt() to r
As per [1] and [2], ADV7535/7533 supports only 2-, 3-, or 4-lane. Drop
unsupported 1-lane from bindings.
[1]
https://www.analog.com/media/en/technical-documentation/data-sheets/ADV7535.pdf
[2]
https://www.analog.com/media/en/technical-documentation/data-sheets/ADV7533.pdf
Fixes: 1e4d58cd7f88 ("
This patch series aims to fix 2 bugs in the ADV7535 driver
1) use-after-free bug in adv7533_attach_dsi()
2) Drop unsupported single lane.
Changes in v4:
- Updated commit description for patch#1.
- Dropped host_node from struct adv7511 and instead used a local pointer
in probe(). Also freeing
Hi Stefan Ekenberg ,
> -Original Message-
> From: dri-devel On Behalf Of Stefan
> Ekenberg
> Sent: 15 November 2024 09:02
> Subject: Re: [PATCH] drm/bridge: adv7533: Reset DSI receiver logic
>
> On 11/15/24 09:10, Dmitry Baryshkov wrote:
> > On Wed, Nov 13, 2024 at 08:40:15AM +0100, Ste
Hi Stefan Ekenberg ,
> -Original Message-
> From: dri-devel On Behalf Of Stefan
> Ekenberg
> Sent: 15 November 2024 12:57
> Subject: [PATCH v2] drm/bridge: adv7511_audio: Update Audio InfoFrame properly
>
> AUDIO_UPDATE bit (Bit 5 of MAIN register 0x4A) needs to be set to 1 while
> upd
Sent from my iPhone
> On 16 Nov 2024, at 05:40, Dan Carpenter wrote:
>
> On Sat, Nov 16, 2024 at 11:06:55AM +0100, Christophe Leroy wrote:
>>> diff --git a/arch/powerpc/platforms/pseries/papr_scm.c
>>> b/arch/powerpc/platforms/pseries/papr_scm.c
>>> index
>>> 9e297f88adc5d97d4dc7b267b0bfebd
Why is a change description missing here?
…
> +++ b/scripts/coccinelle/misc/secs_to_jiffies.cocci
> @@ -0,0 +1,21 @@
…
> +/// Find usages of:
> +/// - msecs_to_jiffies(value*1000)
> +/// - msecs_to_jiffies(value*MSEC_PER_SEC)
I suggest to take another look at corresponding development documentat
On Sat, Nov 16, 2024 at 11:06:55AM +0100, Christophe Leroy wrote:
> > diff --git a/arch/powerpc/platforms/pseries/papr_scm.c
> > b/arch/powerpc/platforms/pseries/papr_scm.c
> > index
> > 9e297f88adc5d97d4dc7b267b0bfebd58e5cf193..9e8086ec66e0f0e555ac27933854c06cfcf91a04
> > 100644
> > --- a/arch/
Le 15/11/2024 à 22:26, Easwar Hariharan a écrit :
[Vous ne recevez pas souvent de courriers de eahar...@linux.microsoft.com.
Découvrez pourquoi ceci est important à
https://aka.ms/LearnAboutSenderIdentification ]
Changes made with the following Coccinelle rules:
@@ constant C; @@
- msecs_
Le 15/11/2024 à 22:26, Easwar Hariharan a écrit :
> [Vous ne recevez pas souvent de courriers de eahar...@linux.microsoft.com.
> Découvrez pourquoi ceci est important à
> https://aka.ms/LearnAboutSenderIdentification ]
>
> This is a series that follows up on my previous series to introduce
> se
Le 15/11/2024 à 22:26, Easwar Hariharan a écrit :
[Vous ne recevez pas souvent de courriers de eahar...@linux.microsoft.com.
Découvrez pourquoi ceci est important à
https://aka.ms/LearnAboutSenderIdentification ]
This is a series that follows up on my previous series to introduce
secs_to_ji
Le 15/11/2024 à 22:26, Easwar Hariharan a écrit :
[Vous ne recevez pas souvent de courriers de eahar...@linux.microsoft.com.
Découvrez pourquoi ceci est important à
https://aka.ms/LearnAboutSenderIdentification ]
As you plan to get those merged independant in each tree, I guess it
should be
Le 15/11/2024 à 22:26, Easwar Hariharan a écrit :
[Vous ne recevez pas souvent de courriers de eahar...@linux.microsoft.com.
Découvrez pourquoi ceci est important à
https://aka.ms/LearnAboutSenderIdentification ]
Changes made with the following Coccinelle rules:
@@ constant C; @@
- msecs_
Le 15/11/2024 à 22:26, Easwar Hariharan a écrit :
[Vous ne recevez pas souvent de courriers de eahar...@linux.microsoft.com.
Découvrez pourquoi ceci est important à
https://aka.ms/LearnAboutSenderIdentification ]
Changes made with the following Coccinelle rules:
@@ constant C; @@
- msecs_
Le 15/11/2024 à 22:26, Easwar Hariharan a écrit :
[Vous ne recevez pas souvent de courriers de eahar...@linux.microsoft.com.
Découvrez pourquoi ceci est important à
https://aka.ms/LearnAboutSenderIdentification ]
There should be some explaination in the commit message, what the script
do
On several HP models (tested on HP 3125 and HP Probook 455 G2),
spurious unplug events are emitted upon login on Chrome OS.
This is likely due to the way Chrome OS restarts graphics
upon login, so it's possible it's an issue on other
distributions but not as common, though I haven't
reproduced the
There is a spelling mistake, Please fix it.
Signed-off-by: Zhu Jun
---
drivers/gpu/drm/msm/registers/adreno/adreno_pm4.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/msm/registers/adreno/adreno_pm4.xml
b/drivers/gpu/drm/msm/registers/adreno/adreno_pm4.xm
On 11/15/24 09:10, Dmitry Baryshkov wrote:
On Wed, Nov 13, 2024 at 08:40:15AM +0100, Stefan Ekenberg wrote:
Reset DSI receiver logic during power on. The need for this change was
discovered when investigating issue with ADV7535. The symptom of the
problem was that ADV7535 continuously outputs a
On 11/15/24 09:16, Dmitry Baryshkov wrote:
On Wed, Nov 13, 2024 at 08:38:11AM +0100, Stefan Ekenberg wrote:
AUDIO_UPDATE bit (Bit 5 of MAIN register 0x4A) needs to be set to 1
while updating Audio InfoFrame information and then set to 0 when done.
Otherwise partially updated Audio InfoFrames cou
AUDIO_UPDATE bit (Bit 5 of MAIN register 0x4A) needs to be set to 1
while updating Audio InfoFrame information and then set to 0 when done.
Otherwise partially updated Audio InfoFrames could be sent out. Two
cases where this rule were not followed are fixed:
- In adv7511_hdmi_hw_params() make sure
Le 15/11/2024 à 22:26, Easwar Hariharan a écrit :
[Vous ne recevez pas souvent de courriers de eahar...@linux.microsoft.com.
Découvrez pourquoi ceci est important à
https://aka.ms/LearnAboutSenderIdentification ]
None of the higher order definitions are used anymore, so remove
definitions f
Le 15/11/2024 à 22:29, Easwar Hariharan a écrit :
[Vous ne recevez pas souvent de courriers de eahar...@linux.microsoft.com.
Découvrez pourquoi ceci est important à
https://aka.ms/LearnAboutSenderIdentification ]
On 11/15/2024 1:26 PM, Easwar Hariharan wrote:
This is a series that follows
42 matches
Mail list logo
