# Re: \[PATCH\] fsl-diu-fb: remove check for pixel clock ranges

- From: Paul Mundt \<hidden\>
- Date: 2011-06-24 08:59:45 
- List: linux-fbdev
- Page: https://ratatoskr.run/linux-fbdev/2011/06/9465099
- Thread: https://ratatoskr.run/linux-fbdev/2011/06/9465091/t.md

```text
On Thu, Jun 23, 2011 at 03:20:26PM -0500, Timur Tabi wrote:
> 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 <redacted>

Applied, thanks.
```