From: maxime.ripard@bootlin.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] drm/sun4i: Handle DRM_MODE_FLAG_**SYNC_POSITIVE correctly
Date: Fri, 16 Feb 2018 16:50:49 +0100 [thread overview]
Message-ID: <20180216155049.r2mc724nfluwrrbe@flea.lan> (raw)
In-Reply-To: <e5d49c13-9b8f-d597-508c-10fed5300769@micronovasrl.com>
On Thu, Feb 15, 2018 at 07:05:56PM +0100, Giulio Benetti wrote:
> > If so, and if remember the captures properly, the sampling would occur
> > right before the rise, and not really around the fall.
> >
> > Would 2/3 be better here?
>
> Yes, you're right, 2/3 phase is better:
>
> 1/3 phase: https://pasteboard.co/H4VehON.png
> 2/3 phase: https://pasteboard.co/H4Veq8a.png
>
> Take a look at the bit in middle(yellow) sampled by clock(blue).
>
> Rising edge is almost in the middle of D0 bit.
>
> >
> > > According to scope captures above on both A20 and A33.
> > > Unfortunately I don't have other boards for the other SoCs to take captures.
> > >
> > > What do you think?
> >
> > I guess we can make that part applicable to all SoCs, we haven't seen
> > any significant differences on those part.
>
> So let's keep:
> - As normal(rising edge) => IO_POL_REG "0x2 => 2/3 phase"
> - As inverted(falling edge) => IO_POL_REG "0x0 => normal phase"
I was actually thinking 1/3 for rising, 2/3 for falling.
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.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/20180216/af2ccffd/attachment.sig>
next prev parent reply other threads:[~2018-02-16 15:50 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
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 [this message]
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=20180216155049.r2mc724nfluwrrbe@flea.lan \
--to=maxime.ripard@bootlin.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