| commit | 2b6c53b1504865728a6dfad3e720918a2f89f3a5 | |
| author | Jon Medhurst (Tixy) <tixy@linaro.org> | |
| Wed, 20 Aug 2014 12:41:04 +0000 (20 13:41 +0100) | ||
| committer | Tomi Valkeinen <tomi.valkeinen@ti.com> | |
| Tue, 26 Aug 2014 09:50:27 +0000 (26 12:50 +0300) | ||
| tree | d54533ccd807a97d74365e065157dd36a3439991 | treesnapshot (tar.gz zip) |
| parent | 754d561ab694ff240ad1615abd0d99f3c1db79a2 | commitdiff |
video: ARM CLCD: Fix calculation of bits-per-pixel
If the device-tree specifies a max-memory-bandwidth property then the
CLCD driver uses that to calculate the bits-per-pixel supported,
however, this calculation is faulty for two reasons.
1. It doesn't ensure that the result is a sane value, i.e. a power of 2
and <= 32 as the rest of the code assumes.
2. It uses the displayed resolution and calculates the average bandwidth
across the whole frame. It should instead calculate the peak
bandwidth based on the pixel clock.
This patch fixes both the above.
Signed-off-by: Jon Medhurst <tixy@linaro.org>
Acked-by: Pawel Moll <pawel.moll@arm.com>
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
If the device-tree specifies a max-memory-bandwidth property then the
CLCD driver uses that to calculate the bits-per-pixel supported,
however, this calculation is faulty for two reasons.
1. It doesn't ensure that the result is a sane value, i.e. a power of 2
and <= 32 as the rest of the code assumes.
2. It uses the displayed resolution and calculates the average bandwidth
across the whole frame. It should instead calculate the peak
bandwidth based on the pixel clock.
This patch fixes both the above.
Signed-off-by: Jon Medhurst <tixy@linaro.org>
Acked-by: Pawel Moll <pawel.moll@arm.com>
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
| drivers/video/fbdev/amba-clcd.c | diffblobblamehistory |