From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] drm/sun4i: Introduce A33 display driver
Date: Fri, 2 Sep 2016 21:06:06 +0200 [thread overview]
Message-ID: <20160902190605.GF6313@lukather> (raw)
In-Reply-To: <18951472779805@web6g.yandex.ru>
Hi Icenowy,
On Fri, Sep 02, 2016 at 09:30:05AM +0800, Icenowy Zheng wrote:
>
>
> 01.09.2016, 23:40, "Maxime Ripard" <maxime.ripard@free-electrons.com>:
> > Hi everyone,
> >
> > This serie introduces the support in the sun4i-drm driver for the A33.
> >
> > Beside the new IPs and special cases for the A33 new IPs, there's
> > nothing really outstanding, and is now at feature parity with the A13.
>
> How can the driver be modified to support LVDS screen?
>
> I have an A33 tablet with a 1024x768 LVDS panel. (iNet D978 Rev2 board,
> which I pushed a dt a few days ago)
Awesome, I don't have such a screen myself, so feel free to work on
it.
I haven't looked into the details of LVDS, but it should be something
along the lines of commit 29e57fab97fc ("drm: sun4i: Add RGB output").
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160902/a1772678/attachment.sig>
next prev parent reply other threads:[~2016-09-02 19:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 15:31 [PATCH 0/7] drm/sun4i: Introduce A33 display driver Maxime Ripard
2016-09-01 15:31 ` [PATCH 1/7] drm/sun4i: support TCONs without channel 1 Maxime Ripard
2016-09-02 1:47 ` Chen-Yu Tsai
2016-09-01 15:31 ` [PATCH 2/7] drm/sun4i: support A33 tcon Maxime Ripard
2016-09-02 6:02 ` Chen-Yu Tsai
2016-09-05 20:22 ` Maxime Ripard
2016-09-01 15:32 ` [PATCH 3/7] drm/sun4i: Add SAT and DRC drivers Maxime Ripard
2016-09-02 6:45 ` Chen-Yu Tsai
2016-09-05 20:27 ` Maxime Ripard
2016-09-04 20:03 ` [linux-sunxi] " Peter Korsgaard
2016-09-06 13:59 ` Maxime Ripard
2016-09-01 15:32 ` [PATCH 4/7] drm/panel: Add Sinlinx SinA33 7" panel Maxime Ripard
2016-09-02 7:01 ` Chen-Yu Tsai
2016-09-04 17:03 ` Icenowy Zheng
2016-09-05 20:02 ` Maxime Ripard
2016-09-06 2:53 ` Chen-Yu Tsai
2016-09-06 9:12 ` Thierry Reding
2016-09-06 14:33 ` Maxime Ripard
2016-09-01 15:32 ` [PATCH 5/7] ARM: sun8i: a33: Add display pipeline Maxime Ripard
2016-09-02 6:28 ` Chen-Yu Tsai
2016-09-05 20:21 ` Maxime Ripard
2016-09-06 2:51 ` Chen-Yu Tsai
2016-09-01 15:32 ` [PATCH 6/7] ARM: sun8i: a33: Add RGB666 pins Maxime Ripard
2016-09-02 1:44 ` [linux-sunxi] " Chen-Yu Tsai
2016-09-01 15:32 ` [PATCH 7/7] ARM: sun8i: sina33: Enable display Maxime Ripard
2016-09-02 1:30 ` [PATCH 0/7] drm/sun4i: Introduce A33 display driver Icenowy Zheng
2016-09-02 19:06 ` Maxime Ripard [this message]
2016-09-03 1:43 ` Chen-Yu Tsai
2016-09-05 20:37 ` Maxime Ripard
2016-09-06 2:50 ` Chen-Yu Tsai
2016-09-06 18:54 ` Maxime Ripard
2016-09-07 4:49 ` Chen-Yu Tsai
2016-09-12 9:56 ` Maxime Ripard
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=20160902190605.GF6313@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).