From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: Jose Abreu <Jose.Abreu@synopsys.com>
Cc: Carlos Palminha <CARLOS.PALMINHA@synopsys.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
"airlied@linux.ie" <airlied@linux.ie>
Subject: Re: [PATCH] drm: arcpgu: Allow some clock deviation in crtc->mode_valid() callback
Date: Wed, 12 Jul 2017 17:06:05 +0000 [thread overview]
Message-ID: <1499879164.3875.8.camel@synopsys.com> (raw)
In-Reply-To: <bf5c60fb64278fc4894098f50add801f6365d823.1498574041.git.joabreu@synopsys.com>
Hi Jose,
On Tue, 2017-06-27 at 15:36 +0100, Jose Abreu wrote:
> Currently we expect that clock driver produces the exact same value
> as we are requiring. There can, and will, be some deviation however
> so we need to take into account that instead of rejecting the mode.
>
> According to HDMI spec we have a max of +-0.5% for the pixel clock
> frequency variation. Lets take that into an advantage and use it
> to calculate how much deviation we can support.
>
> This patch was based on today's drm-misc-next.
>
> Signed-off-by: Jose Abreu <joabreu@synopsys.com>
> Cc: Carlos Palminha <palminha@synopsys.com>
> Cc: Alexey Brodkin <abrodkin@synopsys.com>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Dave Airlie <airlied@linux.ie>
Finally our problem with EDID-less monitor is fixed
with that patch.
Thus,
Acked-by: Alexey Brodkin <abrodkin@synopsys.com>
prev parent reply other threads:[~2017-07-12 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 14:36 [PATCH] drm: arcpgu: Allow some clock deviation in crtc->mode_valid() callback Jose Abreu
2017-07-12 17:06 ` Alexey Brodkin [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=1499879164.3875.8.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=CARLOS.PALMINHA@synopsys.com \
--cc=Jose.Abreu@synopsys.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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