From patchwork Tue Aug 26 09:38:10 2014 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: ????? X-Patchwork-Id: 4779301 Return-Path: X-Original-To: patchwork-linux-fbdev@patchwork.kernel.org Delivered-To: patchwork-parsemail@patchwork2.web.kernel.org Received: from mail.kernel.org (mail.kernel.org [198.145.19.201]) by patchwork2.web.kernel.org (Postfix) with ESMTP id 62783C0338 for ; Tue, 26 Aug 2014 09:45:02 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id 7489020154 for ; Tue, 26 Aug 2014 09:45:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 50BBA2014A for ; Tue, 26 Aug 2014 09:44:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934228AbaHZJo6 (ORCPT ); Tue, 26 Aug 2014 05:44:58 -0400 Received: from p654789.hkidff01.ap.so-net.ne.jp ([121.101.71.137]:44555 "EHLO gw.atmark-techno.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934225AbaHZJo6 (ORCPT ); Tue, 26 Aug 2014 05:44:58 -0400 X-Greylist: delayed 400 seconds by postgrey-1.27 at vger.kernel.org; Tue, 26 Aug 2014 05:44:57 EDT Received: from gw.atmark-techno.com (localhost [IPv6:::1]) by gw.atmark-techno.com (Postfix) with ESMTP id 244DAC02EF for ; Tue, 26 Aug 2014 18:38:13 +0900 (JST) Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by gw.atmark-techno.com (Postfix) with ESMTPS id AE30BC0446 for ; Tue, 26 Aug 2014 18:38:12 +0900 (JST) Received: by mail-qc0-f172.google.com with SMTP id i8so15342497qcq.3 for ; Tue, 26 Aug 2014 02:38:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to:cc :content-type; bh=WPeU/UcYU5gBNOvaN2G7FgqNc0U9hZomMODZVupQbPg=; b=AaaKocRlW6dQl7Hd7XNv3JK2YWJLxivi2A6IzNjwlDE588PQxq25FXbACTrqe1a516 TEfOCiasNR1vsioR+JOwhFz2lP8hq5HvGJyGDMBK3cp5eBuYgGxlFU4LlYczyXE79aMb gyozi4FrLlzZnn2/LCWRKYUjyZaLdJxKtoQ9hkwliYNxWGKGjLzk5qSGNL5mVMkY7i0+ mBeFYddAtcIzjnOxOpGm0lyiXTCjZC39es1B3K/csOTCxAVB44sv8hKleiqxMv6APy/m oOfDE46ZZqKyA0scdijxZQLGUDJUd9o0aFAUlH5acR84YoXQ/ftIzdhRnHssq5q2Qb+o pTow== X-Gm-Message-State: ALoCoQlG04Hgwcs0qSAoi0xXTZSudjDMsIRK9TCguEEvhy8KUWrYA4L+6/0vhStYswBdOPXhi2AUBNr8rNgo/Ko2VnU2hd5B2MlALmsjKYHg/87FDNu0hJWVtniZV+jVo/9OO0SQVbtH X-Received: by 10.224.128.9 with SMTP id i9mr44643441qas.50.1409045890959; Tue, 26 Aug 2014 02:38:10 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.224.128.9 with SMTP id i9mr44643430qas.50.1409045890882; Tue, 26 Aug 2014 02:38:10 -0700 (PDT) Received: by 10.140.95.233 with HTTP; Tue, 26 Aug 2014 02:38:10 -0700 (PDT) Date: Tue, 26 Aug 2014 18:38:10 +0900 Message-ID: Subject: Questions about cea_modes database in modedb.c From: =?UTF-8?B?5L2Q44CF5pyo5aSn6LyU?= To: linux-fbdev@vger.kernel.org Cc: =?UTF-8?B?6I2Y5Y+46Z2W?= Sender: linux-fbdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fbdev@vger.kernel.org X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00, NORMAL_HTTP_TO_IP, RCVD_IN_DNSWL_HI, RP_MATCHES_RCVD, UNPARSEABLE_RELAY autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Dear experts, This is a first time for me to write a email to this mailing list. I am trying to output the video signal from the LCD controller of the embedded system. I want to output the signal whose timings are defined in the "CEA Standard ". I am looking at the documentation for the CEA-816-D. I understand that the signal timing of CEA Standard is defined as "drivers/fbdev/core/modedb.c". I have some questions on cea_modes database in modedb.c. Q.1) In interlaced mode, for the values of the upper_margin, lower_margin and vsync_len, do I need to set the doubled number of the specs of the CEA Standard? Q.2) When the two pixel clock frequencies are defined in one format, how would you choose the value of pixclock? For example, Format 5 can be selected 74.025MHz and 74.176MHz. The modedb.c file, how do I manage about this format? (Can I use in common to this file? Or, rewritten for each system?) Q.3) Format 5: is the value of pixclock correct? In CEA Standard, pixclock of this format is 74.176 or 74.250MHz. Q.4) Format 7 and 9: is the value of pixclock correct? In CEA Standard, pixclock of this format is 27.000 or 27.027MHz. Q.5) Format 20: The value of hsync_len is wrong? I think, hsync_len should be 44. Any feedback is really appreciated. --- Daisuke Sasaki Atmark Techno, Inc. -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git drivers/video/fbdev/core/modedb.c drivers/video/fbdev/core/modedb.c index a9a907c..ed6b883 100644 --- drivers/video/fbdev/core/modedb.c +++ drivers/video/fbdev/core/modedb.c @@ -305,18 +305,18 @@ const struct fb_videomode cea_modes[64] = { }, /* #5: 1920x1080i@59.94/60Hz */ [5] = { - NULL, 60, 1920, 1080, 13763, 148, 88, 15, 2, 44, 5, + NULL, 60, 1920, 1080, 13468, 148, 88, 30, 4, 44, 10, FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT, FB_VMODE_INTERLACED, 0, }, /* #7: 720(1440)x480iH@59.94/60Hz */ [7] = { - NULL, 60, 1440, 480, 18554/*37108*/, 114, 38, 15, 4, 124, 3, 0, + NULL, 60, 1440, 480, 37037, 114, 38, 30, 8, 124, 6, 0, FB_VMODE_INTERLACED, 0, }, /* #9: 720(1440)x240pH@59.94/60Hz */ [9] = { - NULL, 60, 1440, 240, 18554, 114, 38, 16, 4, 124, 3, 0, + NULL, 60, 1440, 240, 37037, 114, 38, 16, 4, 124, 3, 0, FB_VMODE_NONINTERLACED, 0, }, /* #18: 720x576pH@50Hz */ @@ -332,7 +332,7 @@ const struct fb_videomode cea_modes[64] = { }, /* #20: 1920x1080i@50Hz */ [20] = { - NULL, 50, 1920, 1080, 13480, 148, 528, 15, 5, 528, 5, + NULL, 50, 1920, 1080, 13468, 148, 528, 30, 4, 44, 10, FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT, FB_VMODE_INTERLACED, 0, },