Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: karl.beldan@gmail.com (Karl Beldan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/6] ARM: dts: da850-lcdk: add support for 1024x768 resolution
Date: Fri, 30 Sep 2016 12:49:42 +0000	[thread overview]
Message-ID: <20160930124942.ul737vxmdmkxqdre@gobelin> (raw)
In-Reply-To: <CAMpxmJVA+p1st7HzwoOJftArqpY-wUQb8WKbQFAEWnBOysxF6w@mail.gmail.com>

On Fri, Sep 30, 2016 at 11:37:57AM +0200, Bartosz Golaszewski wrote:
> 2016-09-29 20:58 GMT+02:00 Karl Beldan <karl.beldan@gmail.com>:
> > 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

  parent reply	other threads:[~2016-09-30 12:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29 16:31 [PATCH 0/6] ARM: davinci: da850-lcdk: add support for tilcdc Bartosz Golaszewski
2016-09-29 16:31 ` [PATCH 1/6] ARM: davinci: da8xx-dt: add OF_DEV_AUXDATA entry for lcdc Bartosz Golaszewski
2016-09-29 16:31 ` [PATCH 2/6] ARM: dts: da850: add a node for the LCD controller Bartosz Golaszewski
2016-09-30  9:34   ` Sekhar Nori
2016-09-30 13:03     ` Bartosz Golaszewski
2016-09-29 16:31 ` [PATCH 3/6] ARM: dts: da850-lcdk: enable " Bartosz Golaszewski
2016-09-29 18:40   ` Karl Beldan
2016-09-30  9:42     ` Bartosz Golaszewski
2016-09-30 13:15       ` Karl Beldan
2016-09-30 14:21   ` Sekhar Nori
2016-09-29 16:31 ` [PATCH 4/6] ARM: dts: da850-lcdk: add support for 1024x768 resolution Bartosz Golaszewski
2016-09-29 18:58   ` Karl Beldan
2016-09-30  9:37     ` Bartosz Golaszewski
2016-09-30 11:47       ` Sekhar Nori
2016-09-30 12:49       ` Karl Beldan [this message]
2016-09-30 13:48         ` Bartosz Golaszewski
2016-10-01  9:35           ` Sekhar Nori
2016-09-29 16:31 ` [PATCH 5/6] ARM: davinci: enable the LCDC DRM driver in defconfig Bartosz Golaszewski
2016-10-01 12:39   ` Sekhar Nori
2016-09-29 16:31 ` [PATCH 6/6] ARM: da850: adjust memory settings for tilcdc Bartosz Golaszewski
2016-09-29 19:07   ` Karl Beldan
2016-09-30  9:31     ` Bartosz Golaszewski
2016-09-30  9:39       ` Karl Beldan
2016-09-30 12:59   ` Peter Ujfalusi
2016-09-30 15:06     ` Bartosz Golaszewski
2016-09-30 19:19       ` Peter Ujfalusi
2016-10-01  9:24         ` Sekhar Nori
2016-10-03  7:13           ` Peter Ujfalusi
2016-10-04 13:02             ` Kevin Hilman
2016-10-05  8:22               ` Peter Ujfalusi
2016-10-06 17:57                 ` Sekhar Nori
2016-10-04  9:20         ` Bartosz Golaszewski
2016-10-05  8:02           ` Peter Ujfalusi

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=20160930124942.ul737vxmdmkxqdre@gobelin \
    --to=karl.beldan@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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