| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | fsl-diu-fb: remove check for pixel clock ranges | Timur Tabi | 2011-06-24 | 1 | -6/+0 |
| | | | | | | | | | | | | | | | | | | The Freescale DIU framebuffer driver defines two constants, MIN_PIX_CLK and MAX_PIX_CLK, that are supposed to represent the lower and upper limits of the pixel clock. These values, however, are true only for one platform clock rate (533MHz) and only for the MPC8610. So the actual range for the pixel clock is chip-specific, which means the current values are almost always wrong. The chance of an out-of-range pixel clock being used are also remote. Rather than try to detect an out-of-range clock in the DIU driver, we depend on the board-specific pixel clock function (e.g. p1022ds_set_pixel_clock) to clamp the pixel clock to a supported value. Signed-off-by: Timur Tabi <timur@freescale.com> Signed-off-by: Paul Mundt <lethal@linux-sh.org> | ||||
| * | fsl-diu-fb: drop dead ioctl define | Mike Frysinger | 2010-11-15 | 1 | -1/+0 |
| | | | | | | | | | The fsl-diu-fb driver no longer uses this define, and we have a common one to cover this already (FBIO_WAITFORVSYNC). Signed-off-by: Mike Frysinger <vapier@gentoo.org> Signed-off-by: Paul Mundt <lethal@linux-sh.org> | ||||
| * | powerpc/5121: move fsl-diu-fb.h to include/linux | Anatolij Gustschin | 2010-08-01 | 1 | -0/+223 |
| Some DIU structures will be used in platform code in subsequent MPC5121 DIU patch, so we move this header to be able to include it elsewhere. Signed-off-by: Anatolij Gustschin <agust@denx.de> Acked-by: Timur Tabi <timur@freescale.com> Signed-off-by: Grant Likely <grant.likely@secretlab.ca> | |||||
 |
index : kernel_samsung_smdk4412.git | |
| kernel for Galaxy S3 |
| aboutsummaryrefslogtreecommitdiffstats |