All of lore.kernel.org
 help / color / mirror / Atom feed
From: Inochi Amaoto <inochiama@gmail.com>
To: Chen Wang <unicorn_wang@outlook.com>,
	nick@detello.com,  sophgo@lists.linux.dev,
	Inochi Amaoto <inochiama@gmail.com>
Cc: inochiama@outlook.com
Subject: Re: SG2000 display: DSI host + LT8912B HDMI working on v7.2, intent to upstream
Date: Wed, 14 Oct 2026 11:06:09 +0800	[thread overview]
Message-ID: <as7tp4C3SDCSq6DS@inochi.infowork> (raw)
In-Reply-To: <MA5P287MB6080428F77038F40E008D314FE9D2@MA5P287MB6080.INDP287.PROD.OUTLOOK.COM>

On Wed, Oct 14, 2026 at 10:43:12AM +0800, Chen Wang wrote:
> Adding inochi's gmail address, which is the email address he currently uses.
> 
> Inochi, could you please help reply Nick on this?
> 
> Thanks,
> 
> Chen
> 
> On 10/13/2026 8:49 PM, nick@detello.com wrote:
> > (Resent in plain text; the list rejected the HTML copy.)
> > 
> > On 2026-10-13 02:24, nick@detello.com wrote:
> > > Hi Chen, Inochi,
> > > 
> > > I have the SG2000 display path working on v7.2 with two small kernel
> > > patches: DISP, DSI MAC and D-PHY driven by a new DRM host driver,
> > > through the in-tree lontium-lt8912b bridge, to HDMI at 1280x720@60
> > > over
> > > two lanes. It's tested on both cores (RISC-V and ARM) on the Nix Badge
> > > 2.0,
> > > a custom board around the Milk-V Duo S module: console on HDMI and a
> > > 15 fps framebuffer animation.
> > > 
> > > Two questions before I prepare the submission:
> > > 
> > > 1. Is either of you, or anyone you know of, working on the VO/DSI
> > > block
> > >    for cv18xx/SG2000? I would rather join than duplicate.

IIRC, there is no other ones, maybe someone has done similar, but they
are not opened and I am not sure why.
I already had a plan and finished bindings, but I am in bad health so
I have limit time on it (and this is why I may have a bad respond time
in LKML). The driver is a hard thing as I need to cover some SoCs with
simliar design.

> > > 2. Any preference on where the host driver lives
> > >    (drivers/gpu/drm/sophgo/?) and on compatibles before I write the
> > >    bindings? The branch uses sophgo,sg2000-dsi and a
> > >    sophgo,sg2000-vip-sys syscon, and adds one clock ID
> > >    (CLK_DSI_SYNTH_SRC) to the cv1800 binding header.
> > > 
> > > Code, as one reviewable PR against the board's NixOS repo:
> > >   https://github.com/NixVegas/BadgeOS/pull/8
> > >   Driver:  pkgs/video/sophgo-dsi/src/sophgo-dsi.c (~1,500 lines,
> > >            register provenance from sophgo/osdrv cited in place)
> > >   Patches: pkgs/kernel/patches/ (clk-cv18xx: poll DISPPLL's real lock
> > >            bit and expose the DSI source gate; lt8912b: do the bridge
> > >            setup in pre_enable, between the host's LP-11 and HS)
> > >   DT:      pkgs/firmware/dts/sg2000-milkv-duo-s-common.dtsi
> > > 

I have checked the PR and find it is very simple. I do not think it
reflect the real hardware, IIRC it will be divided into several parts with 
phy/dsi/vpu/isp/pinctrl/clk. And your driver only contains some of them.
If you take these thing with a whole view, you will see they are things
that work together.

I also disagree with the clk data fix. Although it should expose a new
div2 clock, the default configuration of DISP PLL should not be changed,
but If I did make a mistake, please send this patch directly and I am
happy with that. ^^.

Sorry for no detailed information, The detailed datasheet is not opened,
they are only opened to the trusted one, So I can not share you with the
detailed design and how the device is co-worked. But at least I can told
you, you may need pinctrl and clock-frequency properties to all display
node.

Regards,
Inochi

> > > Planned order: the clk fix; display nodes for sg2000.dtsi and for the
> > > Duo S DTS Joshua Milas's series added in July; the DSI host as an RFC
> > > to dri-devel; then the lt8912b change, which as written is specific to
> > > this host (fixed HDMI mode, LVDS and PM paths dropped) and will be
> > > rebased on Maxime's atomic-callback conversion on drm-misc-next before
> > > it goes anywhere. Known gaps before the RFC: fixed mode (no EDID, no
> > > hot-plug; HPD goes to the bridge on this board), no vblank interrupt,
> > > and register sequences reproduced from the vendor driver rather than
> > > modelled.
> > > 
> > > Happy to share a video, serial logs or register traces. The driver was
> > > developed with Claude Code assistance; I have read and tested every
> > > line and will carry the review.
> > > 
> > > Thanks,
> > > Nick DeTello

  reply	other threads:[~2026-10-14  3:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cdbe4812564fe417b8a7321e035cc7b3@detello.com>
2026-10-13 12:49 ` SG2000 display: DSI host + LT8912B HDMI working on v7.2, intent to upstream nick
2026-10-14  2:43   ` Chen Wang
2026-10-14  3:06     ` Inochi Amaoto [this message]
2026-10-14  6:37       ` nick

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=as7tp4C3SDCSq6DS@inochi.infowork \
    --to=inochiama@gmail.com \
    --cc=inochiama@outlook.com \
    --cc=nick@detello.com \
    --cc=sophgo@lists.linux.dev \
    --cc=unicorn_wang@outlook.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.