On 21/08/12 06:49 AM, Tomi Valkeinen wrote:
> On Wed, 2012-08-15 at 11:26 -0400, Raphaël Assénat wrote:
>
>>> +
>>> + /* ChiMei G121S1-L01 */
>>> + {
>>> + {
>>
>> ...
>>
>>> + .vsync_level = OMAPDSS_SIG_ACTIVE_HIGH,
>>> + .hsync_level = OMAPDSS_SIG_ACTIVE_HIGH,
>>> + .data_pclk_edge = OMAPDSS_DRIVE_SIG_RISING_EDGE,
>>> + .de_level = OMAPDSS_SIG_ACTIVE_HIGH,
>>> + .sync_pclk_edge = OMAPDSS_DRIVE_SIG_OPPOSITE_EDGES,
>>
>> Actually those 3 panels only use the DE signal. The hsync/vsync signals
>> are not used and on our system we mux them out to make sure they are
>> kept low as recommended in the panel datasheets.
>>
>> Since vsync/hsync are not used, I think the vsync_level, hsync_level and
>> sync_pclk_edge entries could be removed. Otherwise the updated patch
>> works fine as is.
>
> Okay. How do panels like that work? How can they know where a new frame
> starts?
By DE being inactive for a different number of pixel clock cycles during
the vertical and horizontal blanking periods.
> Actually, I now googled for those panels, and they are all LVDS panels,
> not DPI panels. So the patch doesn't look correct at all.
>
> Do you have a DPI-to-LVDS converter chip on your board?
Yes, we do. Depending on the board, we use a SN75LVDS83B or a SN65LVDS84.
The reason for using this approach was that the panels covered by
this patch seemed not to be compatible with Flatlink 3G, which meant
driving them directly from the AM35xx SDI serial interface was not possible.
We unfortunately do not get to select which LVDS deserializer is
used at the panel side..
Best regards,
Raphaël Assénat
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
