From: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>
To: Jianfeng Liu <liujianfeng1994@gmail.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, heiko@sntech.de,
krzk+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
robh@kernel.org, sfr@canb.auug.org.au
Subject: Re: [PATCH] arm64: dts: rockchip: add hdmi1 support to ROCK 5 ITX
Date: Sun, 16 Feb 2025 20:53:27 +0100 [thread overview]
Message-ID: <2FE649E5-61FE-4299-81D1-F838298A04A5@gmail.com> (raw)
In-Reply-To: <20250216134918.1357069-1-liujianfeng1994@gmail.com>
> Wiadomość napisana przez Jianfeng Liu <liujianfeng1994@gmail.com> w dniu 16 lut 2025, o godz. 14:49:
>
> Hi Piotr,
>
> On Sun, 16 Feb 2025 13:37:05 +0100, Piotr wrote:
>> Is there anywhere repo with this patch applied to test it on rock5 itx hw?
>
> This patch is applied to 6.13 and I was testing with armbian:
> https://github.com/armbian/build/pull/7829.
Well - i build 6.12.3 with current armbian patches:
https://github.com/armbian/build/tree/main/patch/kernel/archive/rockchip64-6.13 (all rk3588-*.patch)
+ https://github.com/armbian/build/pull/7829
and i’m still getting:
root@myth-frontend-56b0f018b5e0:~ # dmesg | grep drm
[ 0.529361] rockchip-drm display-subsystem: bound fdd90000.vop (ops vop2_component_ops)
[ 0.531139] rockchip-drm display-subsystem: bound fdea0000.hdmi (ops dw_hdmi_qp_rockchip_ops)
[ 0.532197] [drm] Initialized rockchip 1.0.0 for display-subsystem on minor 0
[ 0.532846] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes
[ 0.533538] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes
[ 10.157564] panthor fb000000.gpu: [drm] clock rate = 198000000
[ 10.160033] panthor fb000000.gpu: [drm] mali-g610 id 0xa867 major 0x0 minor 0x0 status 0x5
[ 10.160755] panthor fb000000.gpu: [drm] Features: L2:0x7120306 Tiler:0x809 Mem:0x301 MMU:0x2830 AS:0xff
[ 10.161569] panthor fb000000.gpu: [drm] shader_present=0x50005 l2_present=0x1 tiler_present=0x1
[ 10.219825] panthor fb000000.gpu: [drm] Firmware protected mode entry not be supported, ignoring
[ 10.221411] panthor fb000000.gpu: [drm] Firmware git sha: 814b47b551159067b67a37c4e9adda458ad9d852
[ 10.222315] panthor fb000000.gpu: [drm] CSF FW using interface v1.1.0, Features 0x0 Instrumentation features 0x71
[ 10.223733] [drm] Initialized panthor 1.2.0 for fb000000.gpu on minor 1
Initially i was thinking my board is defective but…..hdmi1 works nicely with Roobi OS flashed by radxa in eMMC so i’m really puzzled with this…
Is it possible to provide me url with kernel package you are using (wich works ok for you)?
next prev parent reply other threads:[~2025-02-16 19:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 15:25 Jianfeng Liu
2025-02-15 22:22 ` Sebastian Reichel
2025-02-16 1:08 ` Jianfeng Liu
2025-02-16 12:37 ` Piotr Oniszczuk
2025-02-16 13:49 ` Jianfeng Liu
2025-02-16 19:53 ` Piotr Oniszczuk [this message]
2025-02-17 2:35 ` Jianfeng Liu
2025-02-17 9:48 ` Piotr Oniszczuk
2025-02-17 13:21 ` Jianfeng Liu
2025-02-18 13:20 ` Piotr Oniszczuk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2FE649E5-61FE-4299-81D1-F838298A04A5@gmail.com \
--to=piotr.oniszczuk@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=liujianfeng1994@gmail.com \
--cc=robh@kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®