From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Sascha Hauer <s.hauer@pengutronix.de>, Martin Kaiser <martin@kaiser.cx>
Cc: kernel@pengutronix.de, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] video: imxfb: always allocate 256 entries for the color map
Date: Wed, 11 Jan 2017 14:29:49 +0000 [thread overview]
Message-ID: <2846203.pYN6Pvhiy7@amdc3058> (raw)
In-Reply-To: <20170109125942.tk6iutwdnzzxysix@pengutronix.de>
Hi,
On Monday, January 09, 2017 01:59:42 PM Sascha Hauer wrote:
> On Mon, Jan 02, 2017 at 11:24:02PM +0100, Martin Kaiser wrote:
> > The current code calculates the number of color map entries as
> > 1 << info->var.bits_per_pixel. For 32bpp modes, 1 << 32 is 0 when
> > written to an int variable. As a consequence, the subsequent copying
> > of the default (non-empty) color map into our newly allocated color map
> > fails and imxfb's probe function returns an error.
> >
> > On both imx1 and imx21 platforms, the color map is used only for modes
> > with <= 8bpp. By allocating 256 entries for the color map, we're on the
> > safe side.
> >
> > Signed-off-by: Martin Kaiser <martin@kaiser.cx>
>
> Acked-by: Sascha Hauer <s.hauer@pengutronix.de>
Thanks, patch queued for 4.11.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
> Sascha
>
> > ---
> > Re-sending: corrected a typo in the LKML address, sorry for that.
> >
> > drivers/video/fbdev/imxfb.c | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/video/fbdev/imxfb.c b/drivers/video/fbdev/imxfb.c
> > index fe0c4ee..1b0faad 100644
> > --- a/drivers/video/fbdev/imxfb.c
> > +++ b/drivers/video/fbdev/imxfb.c
> > @@ -985,7 +985,11 @@ static int imxfb_probe(struct platform_device *pdev)
> > */
> > imxfb_check_var(&info->var, info);
> >
> > - ret = fb_alloc_cmap(&info->cmap, 1 << info->var.bits_per_pixel, 0);
> > + /*
> > + * For modes > 8bpp, the color map is bypassed.
> > + * Therefore, 256 entries are enough.
> > + */
> > + ret = fb_alloc_cmap(&info->cmap, 256, 0);
> > if (ret < 0)
> > goto failed_cmap;
prev parent reply other threads:[~2017-01-11 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 22:20 [PATCH] video: imxfb: always allocate 256 entries for the color map Martin Kaiser
2017-01-02 22:24 ` Martin Kaiser
2017-01-09 12:59 ` Sascha Hauer
2017-01-11 14:29 ` Bartlomiej Zolnierkiewicz [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=2846203.pYN6Pvhiy7@amdc3058 \
--to=b.zolnierkie@samsung.com \
--cc=kernel@pengutronix.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@kaiser.cx \
--cc=s.hauer@pengutronix.de \
/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).