From: Ezequiel Garcia <ezequiel@collabora.com>
To: Paul Cercueil <paul@crapouillou.net>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Sean Paul <sean@poorly.run>,
devicetree@vger.kernel.org, linux-mips@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [5.2][PATCH 0/3] Ingenic JZ47xx KMS driver
Date: Tue, 16 Apr 2019 11:02:35 -0300 [thread overview]
Message-ID: <16b99f4040a1837bcdbf860d0e9517eb53002aed.camel@collabora.com> (raw)
In-Reply-To: <1552304705.1929.0@crapouillou.net>
On Mon, 2019-03-11 at 12:45 +0100, Paul Cercueil wrote:
> Hi Ezequiel,
>
> On Mon, Mar 11, 2019 at 1:02 AM, Ezequiel Garcia
> <ezequiel@collabora.com> wrote:
> > On Thu, 2019-02-28 at 19:07 -0300, Paul Cercueil wrote:
> > > Hi,
> > >
> > > This is a first attempt at a KMS driver for the JZ47xx MIPS SoCs by
> > > Ingenic. It is aimed to replace the aging jz4740-fb driver.
> > >
> > > The driver will later be updated with new features (overlays, TV-out
> > > etc.), that's why I didn't go with the simple/tiny DRM driver.
> > >
> > > The driver has been tested on the Ben Nanonote (JZ4740) and the
> > > RetroMini RS-90 (JZ4725B) handheld gaming console.
> > >
> >
> > Does this support JZ4780? Or otherwise,
> > is there any similarity with JZ4780 display controller?
> >
> > Thanks,
> > Eze
>
> The JZ4780 LCD controller would in theory work with this driver, but
> to test on the CI20 you'd need to add support for HDMI first.
>
After reviewing a bit this driver and the JZ480 one on the CI20 repo,
there seems to be some differences.
To begin with, the JZ480 apparently has a new 8-word descriptor.
The HDMI looks pretty much a Synopsys DW HDMI, mostly compatible
with the dw-hdmi encoder.
I'll try to put together some patches to enable JZ4780 support.
Won't happen anytime soon, so if anyone wants to give it
a shot, be my guest :-)
Regards,
Eze
prev parent reply other threads:[~2019-04-16 14:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 22:07 [5.2][PATCH 0/3] Ingenic JZ47xx KMS driver Paul Cercueil
2019-02-28 22:07 ` [PATCH 1/3] dt-bindings: Add doc for the ingenic-drm driver Paul Cercueil
2019-03-01 20:16 ` Sam Ravnborg
2019-03-01 22:40 ` Paul Cercueil
2019-03-08 22:23 ` Linus Walleij
2019-03-09 12:33 ` Paul Cercueil
2019-03-09 0:23 ` Rob Herring
2019-02-28 22:07 ` [PATCH 2/3] dt-bindings: Add header for the ingenic-drm driver bindings Paul Cercueil
2019-02-28 22:07 ` [PATCH 3/3] DRM: Add KMS driver for the Ingenic JZ47xx SoCs Paul Cercueil
2019-03-01 8:26 ` Daniel Vetter
2019-03-01 16:21 ` Paul Cercueil
2019-03-14 12:36 ` Paul Cercueil
2019-03-15 10:53 ` Daniel Vetter
2019-03-01 21:00 ` Sam Ravnborg
2019-03-01 23:33 ` Paul Cercueil
2019-03-11 0:02 ` [5.2][PATCH 0/3] Ingenic JZ47xx KMS driver Ezequiel Garcia
2019-03-11 11:45 ` Paul Cercueil
2019-04-16 14:02 ` Ezequiel Garcia [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=16b99f4040a1837bcdbf860d0e9517eb53002aed.camel@collabora.com \
--to=ezequiel@collabora.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=paul@crapouillou.net \
--cc=robh+dt@kernel.org \
--cc=sean@poorly.run \
/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;
as well as URLs for NNTP newsgroup(s).