From: Vinod Koul <vinod.koul@intel.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-arm-kernel@lists.infradead.org,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
linux-kernel@vger.kernel.org,
Fabio Estevam <fabio.estevam@freescale.com>,
Alberto Panizzo <maramaopercheseimorto@gmail.com>,
Valentin Longchamp <valentin.longchamp@keymile.com>,
Daniel Mack <daniel@caiaq.de>, Eric Benard <eric@eukrea.com>
Subject: Re: [PATCH] video IPUv1 fixes for different display connections
Date: Thu, 08 Dec 2011 13:03:26 +0530 [thread overview]
Message-ID: <1323329606.1641.25.camel@vkoul-udesk3> (raw)
In-Reply-To: <1322747932-24943-1-git-send-email-s.hauer@pengutronix.de>
On Thu, 2011-12-01 at 14:58 +0100, Sascha Hauer wrote:
> Hi,
>
> The following series fixes the display connections to the IPU on
> i.MX3 boards. The connection to the display is completely independend
> of the internal pixel format in the framebuffer. The driver instead
> changes the IPU <-> Display mapping dependent on the pixelformat
> which is wrong.
> The following patch makes 16bpp and 32bpp modes possible on both
> RGB666 and RGB888 connected displays.
> The burstsize setting for 32bpp was configured wrong, so 32bpp
> modes have obviously never been tested.
>
> Not for stable since all in kernel boards seem to work.
Applied thanks.
Couldn't help but notice that :
@@ -312,7 +312,7 @@ static void ipu_ch_param_set_size(union
chan_param_mem *params,
case IPU_PIX_FMT_RGB565:
params->ip.bpp = 2;
params->ip.pfs = 4;
is not really good way. Someone else who is using this driver has no way
of knowing what these magic numbers mean and how to use them
Perhaps you can add meaning to these numbers and some note on why they
should be set to these values.
--
~Vinod
next prev parent reply other threads:[~2011-12-08 7:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 13:58 Sascha Hauer
2011-12-01 13:58 ` [PATCH 1/2] i.MX IPU DMA: Fix wrong burstsize settings Sascha Hauer
2011-12-01 13:58 ` [PATCH 2/2] video i.MX IPU: Fix display connections Sascha Hauer
2011-12-08 7:33 ` Vinod Koul [this message]
2011-12-08 9:39 ` [PATCH] video IPUv1 fixes for different " Sascha Hauer
2011-12-08 9:47 ` Vinod Koul
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=1323329606.1641.25.camel@vkoul-udesk3 \
--to=vinod.koul@intel.com \
--cc=daniel@caiaq.de \
--cc=eric@eukrea.com \
--cc=fabio.estevam@freescale.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maramaopercheseimorto@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=valentin.longchamp@keymile.com \
/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
all inboxes | Powered by JetHome®