RE: [PATCH 4/5 v2] [media] ov9740: Remove hardcoded resolution regs

Andrew Chew
2011-06-01T01:50:54Z

> > + /* Width must be a multiple of 4 pixels. */
> > + *width += *width % 4;
>
> No, this doesn't make it a multiple of 4, unless it was
> even;) Just take 5
> as an example. What you really want here is

Geez, you're right. Not sure what was going on in my head when I did this. Thanks for catching it.

> > + /*
> > + * Try to use as much of the sensor area as possible
> when supporting
> > + * smaller resolutions. Depending on the aspect ratio of the
> > + * chosen resolution, we can either use the full width
> of the sensor,
> > + * or the full height of the sensor (or both if the
> aspect ratio is
> > + * the same as 1280x720.
> > + */
> > + if ((OV9740_MAX_WIDTH * height) > (OV9740_MAX_HEIGHT * width)) {
> > + scale_input_x = (OV9740_MAX_HEIGHT * width) / height;
> > + scale_input_y = OV9740_MAX_HEIGHT;
> > } else {
> > - dev_err(&client->dev, "Failed to select resolution!\n");
> > - return -EINVAL;
> > + scale_input_x = OV9740_MAX_WIDTH;
> > + scale_input_y = (OV9740_MAX_WIDTH * height) / width;
> > }
>
> I don'z know how this sensor works, but the above two divisions round
> down. And these are input sizes. Cannot it possibly lead to
> the output
> window being smaller, than required? Maybe you have to round
> up (hint:
> use DIV_ROUND_UP())?

The intention is to do some ratio math without floating point instructions, which resulted in some algebraic twiddling (which is why that math looks so weird). I think what's there is okay. If there's any rounding at all (and there shouldn't be any rounding, if "standard" image dimensions are called for), then there's going to be some aspect ratio weirdness no matter which way you round that division.