From: Liviu Dudau <liviu.dudau@arm.com>
To: Cunyuan Liu <cunyuan.liu@cixtech.com>
Cc: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
neil.armstrong@linaro.org, heiko@sntech.de, marex@nabladev.com,
dev@kael-k.io, prabhakar.mahadev-lad.rj@bp.renesas.com,
andre.przywara@arm.com, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
cix-kernel-upstream@cixtech.com
Subject: Re: [PATCH v2 0/3] Arm China Linlon-D6 display controller support
Date: Tue, 24 Mar 2026 16:10:10 +0000 [thread overview]
Message-ID: <acK3YnKOyPbAroFu@e142607> (raw)
In-Reply-To: <20260313033119.33686-1-cunyuan.liu@cixtech.com>
On Fri, Mar 13, 2026 at 11:31:16AM +0800, Cunyuan Liu wrote:
> Adds Komeda DRM support for Arm China Linlon-D6. The IP is register-compatible
> with Mali-D71, so we reuse the D71 code path.
>
> [1/3] dt-bindings: vendor-prefixes: add Arm Technology (China) "armchina"
> [2/3] dt-bindings: add armchina,linlon-d6 compatible (fallback to arm,mali-d71)
> [3/3] drm/komeda: add Linlon-D6 product ID and of_device_id, use D71 funcs
>
> Changes in v2:
> - PATCH [2/3]: rework compatible schema using enum as suggested by Krzysztof.
>
> v1: https://lore.kernel.org/dri-devel/20260311055506.12023-1-cunyuan.liu@cixtech.com/
>
> Tested on Radxa Orion O6 with Linlon-D6, basic display bring-up works as expected.
>
> Thanks,
> Cunyuan
>
> Cunyuan Liu (3):
> dt-bindings: vendor-prefixes: Add Arm Technology (China) Co., Ltd.
> dt-bindings: display: arm,komeda: add Arm China Linlon D6 compatible
> drm/komeda: Add support for Arm China Linlon-D6
>
> Documentation/devicetree/bindings/display/arm,komeda.yaml | 4 +++-
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> drivers/gpu/drm/arm/display/include/malidp_product.h | 1 +
> drivers/gpu/drm/arm/display/komeda/d71/d71_dev.c | 1 +
> drivers/gpu/drm/arm/display/komeda/komeda_drv.c | 1 +
> 5 files changed, 8 insertions(+), 1 deletion(-)
>
> --
> 2.53.0
>
Pushed the whole series to drm-misc-next.
Best regards,
Liviu
--
====================
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
¯\_(ツ)_/¯
prev parent reply other threads:[~2026-03-24 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 3:31 [PATCH v2 0/3] Arm China Linlon-D6 display controller support Cunyuan Liu
2026-03-13 3:31 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add Arm Technology (China) Co., Ltd Cunyuan Liu
2026-03-19 16:32 ` Liviu Dudau
2026-03-13 3:31 ` [PATCH v2 2/3] dt-bindings: display: arm,komeda: add Arm China Linlon D6 compatible Cunyuan Liu
2026-03-21 20:23 ` Krzysztof Kozlowski
2026-03-13 3:31 ` [PATCH v2 3/3] drm/komeda: Add support for Arm China Linlon-D6 Cunyuan Liu
2026-03-24 16:10 ` Liviu Dudau [this message]
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=acK3YnKOyPbAroFu@e142607 \
--to=liviu.dudau@arm.com \
--cc=airlied@gmail.com \
--cc=andre.przywara@arm.com \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=cunyuan.liu@cixtech.com \
--cc=dev@kael-k.io \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marex@nabladev.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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