linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Andreas Naumann <anaumann@ultratronik.de>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] omap2 dss: omap_display_init: Dont allow more than the maximum number of displays.
Date: Wed, 12 Jun 2013 09:05:51 +0300	[thread overview]
Message-ID: <51B80FBF.9030308@ti.com> (raw)
In-Reply-To: <1370851055-15960-1-git-send-email-anaumann@ultratronik.de>

[-- Attachment #1: Type: text/plain, Size: 818 bytes --]

Hi,

On 10/06/13 10:57, Andreas Naumann wrote:
> Currently the maximum number of display is hardcoded in the array omapfb2_device. Made the number a #define and check it in init routine.
> 
> Signed-off-by: Andreas Naumann <anaumann@ultratronik.de>
> ---
> Our board supports a lot of panels and we could probably solve this more effectively, but arrays shouldnt silently overflow when using more than 10 displays. Created the patch on 3.1 and tested it there. This one is rebased on todays linux-omap.git
>  arch/arm/mach-omap2/display.c       |  5 +++++
>  drivers/video/omap2/omapfb/omapfb.h | 10 +++++-----
>  include/video/omapdss.h             |  2 ++
>  3 files changed, 12 insertions(+), 5 deletions(-)

This is an omapfb change, so it should only change omapfb files, not
omapdss.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

      reply	other threads:[~2013-06-12  6:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10  7:57 [PATCH] omap2 dss: omap_display_init: Dont allow more than the maximum number of displays Andreas Naumann
2013-06-12  6:05 ` Tomi Valkeinen [this message]

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=51B80FBF.9030308@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=anaumann@ultratronik.de \
    --cc=linux-omap@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).