> 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
> Wiadomość napisana przez Andy Yan w dniu 12 mar 2025, o
> godz. 11:42:
>
> From: Andy Yan
>
> The DW DP TX Controller is compliant with the DisplayPort Specification
> Version 1.4 with the following features:
>
> * DisplayPort 1.4a
> * Main Link: 1/2/4 lanes
> * Main Link Support 1.62Gbp
> Wiadomość napisana przez Andy Yan w dniu 12 mar 2025, o
> godz. 07:42:
>
> copy-paste error, which affects DP1 usage
Andy,
Great finding.
Now i see nice screen on rock5itx on dpi1 out :-)
With this: my users are politely asking: when we wili have audio (and cec)
support on dpi1?
> Wiadomość napisana przez Andy Yan w dniu 7 mar 2025, o
> godz. 01:48:
>
>
> Hi Piotr,
> 在 2025-03-06 22:28:08，"Piotr Oniszczuk" 写道：
>>
>>
>
> All dump information currently appears to be correct, so I'm temporarily
> unsure why
> Wiadomość napisana przez Andy Yan w dniu 6 mar 2025, o
> godz. 01:59:
>
>
>
>
> Both of the two config options should be enabled.
> andy@Pro480:~/WorkSpace/linux-next$ rg DW_DP .config
> 4044:CONFIG_ROCKCHIP_DW_DP=y
here i’m a bit lost….
greping on full kernel sources (with applied
htt
> Wiadomość napisana przez Piotr Oniszczuk w dniu 6
> mar 2025, o godz. 15:08:
>
>
>
>> Wiadomość napisana przez Andy Yan w dniu 6 mar 2025, o
>> godz. 13:15:
>>
>> Hi Piotr,
>>
>>
>>
>> Then when you DP cable plugin, you
> Wiadomość napisana przez Andy Yan w dniu 6 mar 2025, o
> godz. 13:15:
>
> Hi Piotr,
>
>
>
> Then when you DP cable plugin, you can run command as bellow to see if the
> driver detects the HPD:
>
> # cat /sys/class/drm/card0-DP-1/status
> connected
> #
>
Andy,
Thx!
With above chan
> Wiadomość napisana przez Andy Yan w dniu 6 mar 2025, o
> godz. 09:53:
>
>
> Hi,
>
> 在 2025-03-06 16:42:00，"Piotr Oniszczuk" 写道：
>>
>>
>>> Wiadomość napisana przez Andy Yan w dniu 6 mar 2025, o
>>> godz. 01:59:
>>>
> Wiadomość napisana przez Andy Yan w dniu 5 mar 2025, o
> godz. 03:30:
>
>>
>
> I only see the HDMI connector from your dri/state ; so it appears the DP
> driver hasn't been successfully
> initialized（I think kernel dmesg can tell that）.
> Have you enabled CONFIG_ROCKCHIP_DW_DP ? This is
> Wiadomość napisana przez Andy Yan w dniu 1 mar 2025, o
> godz. 13:24:
>
>
> Hi Piotr,
>
>>
>> is it worth to play with this or it is too early?
>
> I think you could give it a try if it using the Standard DP（non-ALT mode）
> port for output.
> Since I don't currently have a development
> Wiadomość napisana przez Detlev Casanova w
> dniu 25 lut 2025, o godz. 15:58:
>
> From what I see, the error is not present anymore on linux 6.14-rc4. I tried
> reverting your patch "ASoC: simple-card-utils.c: add missing dlc->of_node"
> (dabbd325b25edb5cdd99c94391817202dd54b651) and the
> Wiadomość napisana przez Andy Yan w dniu 23 lut 2025, o
> godz. 12:30:
>
> From: Andy Yan
>
>
> There are two DW DPTX based DisplayPort Controller on rk3588 which
> are compliant with the DisplayPort Specification Version 1.4 with
> the following features:
>
> * DisplayPort 1.4a
> * Mai
Small data point: on rock5b switching in dts analog audio: from
audio-graph-card to simple-audio-card (so dts is:
https://gist.github.com/warpme/349b27e49bc6f617ef1041047e75adab ) makes kernel
oops go away with analog audio still working…
so maybe issue is in audio-graph-card code (or its dts
> Wiadomość napisana przez Detlev Casanova w
> dniu 20 lut 2025, o godz. 18:03:
>
> Hi Piotr,
>
> On Thursday, 20 February 2025 06:16:20 EST Piotr Oniszczuk wrote:
>>
>>
>> Detelv,
>>
>> Just curious of your opinion:
>>
>&g
> Wiadomość napisana przez Detlev Casanova w
> dniu 17 lut 2025, o godz. 22:47:
>
> To support HDMI audio on the rk3588 based devices, the generic HDMI
> Codec framework is used in the dw-hdmi-qp DRM bridge driver.
>
> The implementation is mainly based on the downstream driver, ported to th
> Wiadomość napisana przez Sebastian Reichel
> w dniu 13 lut 2025, o godz. 18:26:
>
> Hello Piotr,
>
>
> The RK3588 has two different DP controllers. The one handled in this
> series should get the eDP port running, which is routed to the
> "eDP Panel" in the block diagram on page 3 of the
> Wiadomość napisana przez Diederik de Haas w dniu 13
> lut 2025, o godz. 17:56:
>
> On Thu Feb 13, 2025 at 3:54 PM CET, Piotr Oniszczuk wrote:
>>
>>
>
> I don't know if it's relevant, but while HDMI0 got enabled for quite a
> few devices in
> Wiadomość napisana przez Damon Ding w dniu 23 sty
> 2025, o godz. 11:07:
>
> Picked from:
> https://patchwork.kernel.org/project/linux-rockchip/list/?series=923593
>
> These patchs have been tested with a 1536x2048p60 eDP panel on
> RK3588S EVB1 board, and HDMI 1080P/4K display also has be
> Wiadomość napisana przez Chris Morgan w dniu
> 05.08.2024, o godz. 18:20:
>
> On Sat, Aug 03, 2024 at 03:24:06PM +0200, Piotr Oniszczuk wrote:
>> Hi Cristian,
>>
>> Will you find some time and motivation to add CEC support to Quad-Pixel (QP)
>> TX con
Hi Cristian,
Will you find some time and motivation to add CEC support to Quad-Pixel (QP) TX
controller ?
Probably you recall - I added initial CEC support to yours v1 series and i’m
stuck with timing issue (cec pulses are 3x too long).
For me it looks like clock issue.
I’m out of ideas how to
Cristian,
I'm hacking with adding cec support for rk3588 hdmi on 6.10-rc7 mainline.
Cec kernel module is my backport from bsp.
Module loads. Cec line (observed on osciloscope) has pulses when i'm issuing
i.e. cec-ctl -d /dev/cec0 --phys-addr=1.0.0.0 —playback
My issue is that timings are 2,9
(resent as plain text instead of html)
Cristian,
I was awaiting over year for this work!
I’m devel. 2 distros where single mainline kernel serves
2835/2711/2712/h6/h313/h616/h618/rk3328/rk3399/rk3566/rk3568/rk3588/s905/s912/sm1/g12.
Before this work rk3588 was excluded because rk3588 hdmi was
Cristian,
I was awaiting over year for this work!
I’m devel. 2 distros where single mainline kernel serves
2835/2711/2712/h6/h313/h616/h618/rk3328/rk3399/rk3566/rk3568/rk3588/s905/s912/sm1/g12.
Before this work rk3588 was excluded because rk3588 hdmi was regressing hdmi on
other socs.
With thi
> Wiadomość napisana przez Michael Riesch w
> dniu 13.09.2022, o godz. 08:55:
>
> Hi,
>
> On 9/12/22 20:02, Chris Morgan wrote:
>> From: Chris Morgan
>
> Cc: Sascha -> any thoughts on this one?
>
> Best regards,
> Michael
>
>> If I use more than one VP to output on an RK3566 based device
> Wiadomość napisana przez Robin Murphy w dniu
> 11.07.2022, o godz. 12:41:
>
> On 2022-06-25 16:31, Piotr Oniszczuk wrote:
>>> Wiadomość napisana przez Peter Geis w dniu
>>> 25.06.2022, o godz. 16:00:
>>>
>>>
>>> The first iss
> Wiadomość napisana przez Piotr Oniszczuk w dniu
> 25.06.2022, o godz. 17:31:
>
>
>
>> Wiadomość napisana przez Peter Geis w dniu 25.06.2022,
>> o godz. 16:00:
>>
>>
>> The first issue you have is the TV isn't responding until the ab
> Wiadomość napisana przez Peter Geis w dniu 25.06.2022,
> o godz. 16:00:
>
>
> The first issue you have is the TV isn't responding until the absolute
> end.
I suspect this is because lack on idle gaps between cec commands sent from
board to tv.
Maybe TV sw. can't deal with consecutive com
> Wiadomość napisana przez Peter Geis w dniu 25.06.2022,
> o godz. 01:50:
>
> On Fri, Jun 24, 2022 at 2:57 PM Piotr Oniszczuk
> wrote:
>>
>>
>>
>>> Wiadomość napisana przez Peter Geis w dniu
>>> 24.06.2022, o godz. 14:40:
>>>
> Wiadomość napisana przez Peter Geis w dniu 24.06.2022,
> o godz. 14:40:
>
>>
>> Sascha, Peter
>>
>> I returned to trying to find why hdmi-cec is not working on rock3-a v1.31 hw.
>>
>> I'm on vop2 v11 on 5.18 mainline.
>>
>> Current findings:
>>
>> (1) the same sw. stack/binaries works
> Wiadomość napisana przez Piotr Oniszczuk w dniu
> 14.05.2022, o godz. 15:58:
>
>
>
>> Wiadomość napisana przez Peter Geis w dniu 09.05.2022,
>> o godz. 18:00:
>>
>> If you want to confirm the hardware is configured correctly you can
>> rem
> Wiadomość napisana przez Peter Geis w dniu 09.05.2022,
> o godz. 18:00:
>
> If you want to confirm the hardware is configured correctly you can
> remove the cec pin from the hdmi node and set up a cec-gpio node.
> https://elixir.bootlin.com/linux/v5.18-rc5/source/Documentation/devicetree/bi
> Wiadomość napisana przez Peter Geis w dniu 11.05.2022,
> o godz. 00:49:
>
> I've pulled your dts and with a few fixes got a working system from
> it. At least on the v1.1 board cec is functional:
> Total for dwhdmi-rockchip device /dev/cec0: 1, Succeeded: 1, Failed:
> 0, Warnings: 0
Peter,
> Wiadomość napisana przez Peter Geis w dniu 10.05.2022,
> o godz. 14:08:
>
>
> You are on the clk_rtc32k_frac which is a fractional divider that is
> fed from the 24m clock. Your clock likely isn't the issue here. I'd
> recommend setting up the cec-gpio node to validate your hardware
> work
> Wiadomość napisana przez Peter Geis w dniu 10.05.2022,
> o godz. 03:35:
>
> Could you grab the clock tree from /sys/kernel/debug/clk/clk_summary
> for the clk_hdmi_cec tree?
Here it is:
enable prepare protect
duty hardware
>
> If you want to confirm the hardware is configured correctly you can
> remove the cec pin from the hdmi node and set up a cec-gpio node.
> https://elixir.bootlin.com/linux/v5.18-rc5/source/Documentation/devicetree/bindings/media/cec-gpio.txt
>
> For some reason the board developers decided to
>>
>> I think i have this already (pls see L231/L232 in
>> https://pastebin.com/67wu9QrH )
>
> I see you have hdmitxm1_cec as the enabled pin. Are you certain it's
> the m1 pin and not the m0 pin?
It depends on board ver.
pls look:
https://github.com/radxa/kernel/commit/c1d727692e85c0a265913
> Wiadomość napisana przez Peter Geis w dniu 08.05.2022,
> o godz. 18:53:
>
>>
>> I was trying to do this in dts https://pastebin.com/67wu9QrH but cec is
>> still non-functional
>>
>> Maybe You have some hints/pointers here?
>
> Add the following to the HDMI node:
> assigned-clocks = <&cr
> Wiadomość napisana przez Sascha Hauer w dniu
> 22.04.2022, o godz. 09:28:
>
> From: Michael Riesch
>
> Enable the RK356x Video Output Processor (VOP) 2 on the Radxa
> ROCK3 Model A.
>
> Signed-off-by: Michael Riesch
> Reported-by: kernel test robot
> Link:
> https://lore.kernel.org/r/
> Wiadomość napisana przez Daniel Stone w dniu
> 12.04.2022, o godz. 13:30:
>
>> Testing Sacha patch (see today's email from Sascha) i'm getting
>>
>> Qt: EGL Error : Could not create the egl surface: error = 0x3009
>>
>> i'm reading this as: Qt tries allocate EGL surface and EGL returns er
> Wiadomość napisana przez Lucas Stach w dniu
> 12.04.2022, o godz. 10:10:
>
> This could be both a Mesa/Panfrost or application issue. The
> application is supposed to try to allocate with a arbitrary chosen
> format and the valid modifiers queried from the plane it wants to put
> the surfac
> Wiadomość napisana przez Sascha Hauer w dniu
> 12.04.2022, o godz. 09:50:
>
>
> Somehow negotiation of the format goes wrong. Applications shouldn't
> pick these formats when the GPU is used for rendering. I don't know how
> and where this should be fixed properly, but your application sho
> Wiadomość napisana przez Sascha Hauer w dniu
> 11.04.2022, o godz. 11:08:
>
> Ok, so #37 for video, #43 for GUI.
>
> Where is the OSD rendered? Is it rendered on the GUI layer?
Yes
>
>> ...
>>
>>
>> playback:
>> .
>> 2022-04-08 17:48:55.457823 I DRMVideo: Using Plane #37 for v
> Wiadomość napisana przez Sascha Hauer w dniu
> 08.04.2022, o godz. 14:00:
>
>> That turned out to be simpler than I thought it would be. The zpos
>> values were never actually written to the hardware. Please try the
>> following fixup, it should fix this issue.
>
> Or better try v10 which
> Wiadomość napisana przez Sascha Hauer w dniu
> 07.04.2022, o godz. 12:16:
>
>
> Yes, and it raises a few more ;)
pls see at end of email: DRI state with playback
>
>>
>> player:
>>
>> 2022-04-06 17:52:26.424487 I Display: Geometry: 1920x1080+0+0 Size(Qt):
>> 930mmx530mm
>> 2022-04-06
> Wiadomość napisana przez Sascha Hauer w dniu
> 06.04.2022, o godz. 16:58:
>
> On Wed, Apr 06, 2022 at 11:47:22AM +0200, Piotr Oniszczuk wrote:
>>
>>
>> Sascha,
>>
>> Having vop2 finally working with drm planes rendering i discovered anot
> Wiadomość napisana przez Piotr Oniszczuk w dniu
> 01.04.2022, o godz. 15:05:
>
>
>
>> Wiadomość napisana przez Sascha Hauer w dniu
>> 01.04.2022, o godz. 14:52:
>>
>> Based on the discussion with Andy please try the following patch, it
>>
> Wiadomość napisana przez Sascha Hauer w dniu
> 01.04.2022, o godz. 14:52:
>
> Based on the discussion with Andy please try the following patch, it
> should fix your green screen issue. Note that with this patch the
> CRTC and plane ids will change, so the modetest commands need to be
> adju
> Wiadomość napisana przez Andy Yan w dniu
> 01.04.2022, o godz. 14:04:
>
> Hi Piotr:
>
> On 4/1/22 09:52, Andy Yan wrote:
>
> Pls update the new vop2_dump.sh scripts from github. The
>
> previous scripts I gave you has some bug. sorry.
>
Andy,
Sure. np.
Pls find dump with current vop2_
> Wiadomość napisana przez Piotr Oniszczuk w dniu
> 31.03.2022, o godz. 17:06:
>
>
>
>> Wiadomość napisana przez Sascha Hauer w dniu
>> 31.03.2022, o godz. 17:00:
>>
>>
>> Have you applied the bugfix I shared with you here:
>>
>>
> Wiadomość napisana przez Sascha Hauer w dniu
> 31.03.2022, o godz. 17:00:
>
>
> Have you applied the bugfix I shared with you here:
>
> https://lore.kernel.org/linux-arm-kernel/20220330072822.gx12...@pengutronix.de/
>
ps
noo
didn't noticed :-(
let me try with it!
> Wiadomość napisana przez Andy Yan w dniu
> 31.03.2022, o godz. 14:13:
>
>
> Piotr:
>
> What soc is on you board? rk3566 or rk3568?
it is rk3566 in x96-x6 tvbox
>
> I have a scripts[0] use io[1] command to dump the VOP2 register you can use
> it dump the register configuration when y
> Wiadomość napisana przez Sascha Hauer w dniu
> 30.03.2022, o godz. 21:20:
>
>> So i tried following combinations
>>
>> -boot
>> -modetest -s 69@67:1920x1080 -> ok
>> -modetest -P 43@67:1920x1080@NV12 -> green screen
>
> I have no idea what is going on here. There same commands work for me
> Wiadomość napisana przez Sascha Hauer w dniu
> 30.03.2022, o godz. 12:20:
>
> Does it change anything if you do a "modetest -s 69@67:1920x1080" before
> starting the app? Or if you run "modetest -P 43@67:1920x1080@NV12"
> before starting the app? Or other combinations thereof?
So i tried f
> Wiadomość napisana przez Sascha Hauer w dniu
> 28.03.2022, o godz. 17:10:
>
>
> Changes since v8:
> - make hclk_vo a critical clock instead of enabling it in the hdmi driver
> - Fix vop2_setup_layer_mixer(), reported by Andy Yan
> - Limit planes possible_crtcs to actually existing crtcs
>
> Wiadomość napisana przez Peter Geis w dniu 13.03.2022,
> o godz. 13:56:
>
>>
>
> I was worried about that, thanks for testing it.
> Can you send me the cec_clk rate before and after this patch?
>
Here it is:
working:
enable prepare protect
> Wiadomość napisana przez Peter Geis w dniu 26.01.2022,
> o godz. 21:24:
>
> The hdmi-cec clock must be 32khz in order for cec to work correctly.
> Ensure after enabling the clock we set it in order for the hardware to
> work as expected.
> Warn on failure, in case this is a static clock tha
> Wiadomość napisana przez Sascha Hauer w dniu
> 27.01.2022, o godz. 12:00:
>
>>
>> -on rk3399 it gives me 4k screen where right vertical 1/3 part of screen is
>> garbage
>> -on rk3566 my samsung 4k monitor has black screen and cycle of OSD msgs:
>> HDMI2 connected; HDMI2 disconnected; ...
Sascha,
FYI
small report regarding 4k modes support in v4:
-on rk3399 it gives me 4k screen where right vertical 1/3 part of screen is
garbage
-on rk3566 my samsung 4k monitor has black screen and cycle of OSD msgs: HDMI2
connected; HDMI2 disconnected;
I would suggest split v4 into 2 sep
> Wiadomość napisana przez Sascha Hauer w dniu
> 21.01.2022, o godz. 11:32:
>
>>
>> 1. how support for CEC looks/prospects (plans for future, not in this code,
>> expecting others should implement, etc)?
>
> I had to google what CEC actually is. We don't have plans supporting it.
> It look
> Wiadomość napisana przez Sascha Hauer w dniu
> 20.12.2021, o godz. 12:06:
>
>
> Third round of patches and last one for this year. I hopefully integrated
> all review feedback. Additionally the driver is now fully converted to
> regmap, so no struct vop_reg necessary anymore.
>
> Sascha
>
> Wiadomość napisana przez Clément Péron w dniu
> 09.07.2020, o godz. 16:03:
>
> Add an Operating Performance Points table for the GPU to
> enable Dynamic Voltage & Frequency Scaling on the H6.
>
> The voltage range is set with minival voltage set to the target
> and the maximal voltage set t
61 matches
Mail list logo
