From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] drm/sun4i: Handle DRM_MODE_FLAG_**SYNC_POSITIVE correctly
Date: Mon, 29 Jan 2018 13:53:41 +0100 [thread overview]
Message-ID: <20180129125341.elup47ymedzxornn@flea.lan> (raw)
In-Reply-To: <18ec71dc-a785-a771-76d4-176d95032c97@micronovasrl.com>
Hi,
On Fri, Jan 26, 2018 at 04:55:54PM +0100, Giulio Benetti wrote:
> > > > > It behaves the same way as A20, so as I mean IO polarity,
> > > > > all signals(except D0-D23), are inverted.
> > > > > For A33 I've used A33-OLinuXino.
> > > > > For A20 our LiNova1.
> > > >
> > > > Indeed, HSYNC and VSYNC look inverted.
> > >
> > > Yes, so they should be inverted inside the driver.
> >
> > Yep. And the LCD panels used on our boards as well in order to avoid
> > any breakages.
>
> Can you provide a list?
> Or is there a way I can find it on my own?
> I can create a whole patch-set providing this too on panel-simple.c
> Ok?
Grepping through the DT, it seems like there's only the A13 q8 tablet
and the SinA33. The former uses simple-panel, the latter a custom
panel driver.
> > > A little out of thread but:
> > > I'd like to send one for u-boot too,
> > > but this means also to modify every sunxi "sync:3" to "sync:0" and
> > > vice-versa.
> > >
> > > What do you think?
> >
> > That it's going to be a nightmare... We've advertised since the very
> > beginning something, and we're about to break it. I'm not sure we want
> > to do that.
>
> I can take care about that.
> But I also think that a lot of displays work because they use only DE-mode,
> almost ignoring HSync and VSync signals(HV-mode).
>
> In any case I have to produce these patches because of my company's board
> based on A20 and A33, and modify defconfig according to it.
> The only technical nightmare I see is to produce a commit for every
> defconfig to be modified and copy-paste che commit-log substituing board
> name(1-2 days of work).
> Problem is testing, but we're speaking about something that probably was
> badly working, but you couldn't see it on display.
> So I think this is only an improvement at the end.
It really is a separate discussion, but you would also need to fix all
the environments everywhere, which is simply not feasible.
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: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180129/884737a3/attachment-0001.sig>
next prev parent reply other threads:[~2018-01-29 12:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-20 18:50 [PATCH 1/2] drm/sun4i: Handle DRM_BUS_FLAG_PIXDATA_*EDGE Giulio Benetti
2018-01-20 18:50 ` [PATCH 2/2] drm/sun4i: Handle DRM_MODE_FLAG_**SYNC_POSITIVE correctly Giulio Benetti
2018-01-22 8:51 ` Maxime Ripard
2018-01-22 20:27 ` Giulio Benetti
2018-01-24 17:38 ` Giulio Benetti
2018-01-24 19:37 ` Giulio Benetti
2018-01-25 15:21 ` Maxime Ripard
2018-01-25 16:50 ` Giulio Benetti
2018-01-26 14:56 ` Maxime Ripard
2018-01-26 15:55 ` Giulio Benetti
2018-01-27 22:07 ` Giulio Benetti
2018-02-01 10:14 ` Maxime Ripard
2018-02-01 16:09 ` Giulio Benetti
2018-02-05 14:21 ` Maxime Ripard
2018-01-29 12:53 ` Maxime Ripard [this message]
2018-02-07 10:39 ` Maxime Ripard
2018-02-07 12:49 ` Giulio Benetti
2018-02-08 20:40 ` Maxime Ripard
2018-02-09 10:13 ` Chen-Yu Tsai
2018-02-15 18:05 ` Giulio Benetti
2018-02-16 15:50 ` Maxime Ripard
2018-02-28 15:56 ` Giulio Benetti
2018-01-22 8:45 ` [PATCH 1/2] drm/sun4i: Handle DRM_BUS_FLAG_PIXDATA_*EDGE 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=20180129125341.elup47ymedzxornn@flea.lan \
--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