public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
From: 杨孙运 <yangsunyun1993@gmail.com>
To: Jingyi Wang <jingyi.wang@oss.qualcomm.com>
Cc: syyang@lontium.com, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, andrzej.hajda@intel.com,
	neil.armstrong@linaro.org, dmitry.baryshkov@oss.qualcomm.com,
	maarten.lankhorst@linux.intel.com, rfoss@kernel.org,
	mripard@kernel.org, Laurent.pinchart@ideasonboard.com,
	jonas@kwiboo.se, jernej.skrabec@gmail.com,
	devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org,
	xmzhu@lontium.corp-partner.google.com, tzimmermann@suse.de,
	xmzhu@lontium.com, rlyu@lontium.com, xbpeng@lontium.com
Subject: Re: [PATCH v3 0/2] Add LT9611C(EX/UXD) DRM bridge driver and device tree
Date: Tue, 21 Apr 2026 13:49:02 +0800	[thread overview]
Message-ID: <CAFQXuNYFwRLbm8yLFNzAcwO24NuBWEKnaAQP=O5BhCuCb+eWuQ@mail.gmail.com> (raw)
In-Reply-To: <b2a5ef92-f312-4e0a-9772-4d430b80a46e@oss.qualcomm.com>

Jingyi Wang <jingyi.wang@oss.qualcomm.com> 于2026年4月21日周二 13:09写道:
>
>
>
> On 4/20/2026 2:16 PM, syyang@lontium.com wrote:
> > From: Sunyun Yang <syyang@lontium.com>
> >
> > This series adds support for the Lontium LT9611C(EX/UXD) MIPI DSI to HDMI
> > chip:
> >
> > -dt-bindings: bridge: This patch adds new content to the lontium,lt9611.yaml
> >   binding file.
> > -drm/bridge: This patch add new DRM bridge driver for LT9611C(EX/UXD) chip.
> >
> > Signed-off-by: Sunyun Yang<syyang@lontium.com>
>
> "This patch" should be avoided in the commit msg, begin with "add" will be enough.
>
it will be fixed  in the next version.
> Thanks,
> Jingyi
>
> > ---
> > Changes in v3:
> > -dt-binding:
> >   1. lt9611c(ex/uxd) content merged into lontium,lt9611.yaml
> > -drm/bridge:
> >   1. Drop the licence text, only use SPDX header
> >   2. Sort the headers
> >   3. Use library functions for crc8
> >   4. Drop i2c_read_byte and i2c_write_byte
> >   5. Lowercase all hex values
> >   6. Use paged writes as implemented for LT9611C(EX/UXD)
> >   7. Drop dev_info, use dev_dbg
> >   8. Modify lt9611c_get_edid_block, don't store EDID in the long-term structures
> >   9. Use HDMI audio helpers.
> >   10.Remove unnecessary flags,Implement proper cleanup path, unwinding resources
> >      one by one.
> >   11.Replace devm_kzalloc with devm_drm_bridge_alloc.
> >   12.Remove extra kthread.
> > -Link to v1: https://lore.kernel.org/lkml/20250903123825.1721443-1-syyang@lontium.com/
> >
> > Changes in v2:
> >   1. Forget modify code, operation error, Please disregard this submit.
> >
> > Changes in v1:
> > -dt-binding:
> >   1. Submit the first version of the code.
> > -drm/bridge:
> >   1. Submit the first version of the code.
> >
> > ---
> > Sunyun Yang (2):
> >    dt-bindings: bridge: This patch adds new content to the
> >      lontium,lt9611.yaml binding file
> >    drm/bridge: This patch add new DRM bridge driver for LT9611C chip
> >
> >   .../display/bridge/lontium,lt9611.yaml        |    8 +-
> >   drivers/gpu/drm/bridge/Kconfig                |   18 +
> >   drivers/gpu/drm/bridge/Makefile               |    1 +
> >   drivers/gpu/drm/bridge/lontium-lt9611c.c      | 1365 +++++++++++++++++
> >   4 files changed, 1390 insertions(+), 2 deletions(-)
> >   create mode 100755 drivers/gpu/drm/bridge/lontium-lt9611c.c
> >
>

      reply	other threads:[~2026-04-21  7:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-20  6:16 [PATCH v3 0/2] Add LT9611C(EX/UXD) DRM bridge driver and device tree syyang
2026-04-20  6:16 ` [PATCH v3 1/2] dt-bindings: bridge: This patch adds new content to the lontium, lt9611.yaml binding file syyang
2026-04-20 11:33   ` [PATCH v3 1/2] dt-bindings: bridge: This patch adds new content to the lontium,lt9611.yaml " Krzysztof Kozlowski
2026-04-20 14:15     ` Krzysztof Kozlowski
2026-04-20 14:18       ` Krzysztof Kozlowski
2026-04-21  3:39         ` 杨孙运
2026-04-23  0:19     ` Claude review: " Claude Code Review Bot
2026-04-20  6:16 ` [PATCH v3 2/2] drm/bridge: This patch add new DRM bridge driver for LT9611C(EX/UXD) chip syyang
2026-04-20 12:18   ` Dmitry Baryshkov
2026-04-21  7:37     ` 杨孙运
2026-04-21 10:48       ` Dmitry Baryshkov
2026-04-22  4:41         ` 杨孙运
2026-04-22 18:56           ` Dmitry Baryshkov
2026-04-23  0:19     ` Claude review: " Claude Code Review Bot
2026-04-20 10:45 ` [PATCH v3 0/2] Add LT9611C(EX/UXD) DRM bridge driver and device tree Dmitry Baryshkov
2026-04-20 11:05   ` 杨孙运
2026-04-21 10:49     ` Dmitry Baryshkov
2026-04-23  0:19   ` Claude review: " Claude Code Review Bot
2026-04-21  5:09 ` Jingyi Wang
2026-04-21  5:49   ` 杨孙运 [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='CAFQXuNYFwRLbm8yLFNzAcwO24NuBWEKnaAQP=O5BhCuCb+eWuQ@mail.gmail.com' \
    --to=yangsunyun1993@gmail.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=andrzej.hajda@intel.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=jingyi.wang@oss.qualcomm.com \
    --cc=jonas@kwiboo.se \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=rfoss@kernel.org \
    --cc=rlyu@lontium.com \
    --cc=robh@kernel.org \
    --cc=syyang@lontium.com \
    --cc=tzimmermann@suse.de \
    --cc=xbpeng@lontium.com \
    --cc=xmzhu@lontium.com \
    --cc=xmzhu@lontium.corp-partner.google.com \
    /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