[lkml]   [2015]   [Sep]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 6/9] drm: bridge/dw_hdmi: adjust pixel clock values in N calculation
On Fri, Sep 04, 2015 at 07:03:11PM -0700, Doug Anderson wrote:
> AKA: just replace your entire "compute_n" function with:
> return (128 * freq) / 1000;
> ...and it's 100% simpler _and_ gets you a (marginally) better rate
> (assuming you really have 22.175000). If it was just about a
> 32000.222 vs 32000 I'd not be saying anything right now. It's about
> adding complexity.

No. It doesn't work for all cases. Do the calculations for every
sample rate in those tables in the HDMI spec, and you'll find out

FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to

 \ /
  Last update: 2015-09-05 10:41    [W:0.132 / U:6.860 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site