From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933460AbcI3MtJ (ORCPT ); Fri, 30 Sep 2016 08:49:09 -0400 Received: from mail-wm0-f66.google.com ([74.125.82.66]:35003 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933065AbcI3Msw (ORCPT ); Fri, 30 Sep 2016 08:48:52 -0400 Date: Fri, 30 Sep 2016 12:49:42 +0000 From: Karl Beldan To: Bartosz Golaszewski Cc: Kevin Hilman , Michael Turquette , Sekhar Nori , Rob Herring , Mark Rutland , Russell King , LKML , arm-soc Subject: Re: [PATCH 4/6] ARM: dts: da850-lcdk: add support for 1024x768 resolution Message-ID: <20160930124942.ul737vxmdmkxqdre@gobelin> References: <1475166715-7857-1-git-send-email-bgolaszewski@baylibre.com> <1475166715-7857-5-git-send-email-bgolaszewski@baylibre.com> <20160929185805.q2pdihajikgzo4lm@gobelin> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/ (1.7.0) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Sep 30, 2016 at 11:37:57AM +0200, Bartosz Golaszewski wrote: > 2016-09-29 20:58 GMT+02:00 Karl Beldan : > > Hi, > > > > On Thu, Sep 29, 2016 at 06:31:53PM +0200, Bartosz Golaszewski wrote: > >> Add svga timings for 1024x768 resolution to the da850-lcdk > >> device tree. > >> > > > > [snip] > > > > > Why do you also call 1024x768 svga ? > > > > Thanks, should have been xga. will fix in v2. > > > I don't think the LCDK can cope with this resolution at this frequency > > (in terms of mem bandwidth), at least that's what I observed back in > > August. If confirmed I think it is worth mentioning in the log at least, > > but then I doubt adding this config would be useful. > > > > Thanks for the heads up. How would that manifest itself? This seems to > work fine for me - I'm not getting any warnings on a simple system - > maybe if I added some additional memory load it would complain. > A mere dmesg > /dev/tty0 (or repeatedly cat-ting a file to /dev/tty0) should suffice to make the issue visible and trigger FIFO underflows. Regards, Karl