linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Scott Jiang <scott.jiang.linux@gmail.com>
Cc: linux-media@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@redhat.com>,
	uclinux-dist-devel@blackfin.uclinux.org
Subject: Re: [PATCH RFC] [media] add Aptina mt9m114 HD digital image sensor driver
Date: Thu, 28 Mar 2013 10:10:19 +0100	[thread overview]
Message-ID: <1691028.0qtxercLZ8@avalon> (raw)
In-Reply-To: <CAHG8p1CP8nSjVFeus17wDfiSgq1qTMDDvAJtJODmt5OxL3zj=A@mail.gmail.com>

Hi Scott,

On Thursday 28 March 2013 16:29:30 Scott Jiang wrote:
> >> This driver support parallel data output mode and
> >> QVGA/VGA/WVGA/720P resolution. You can select YCbCr and RGB565
> >> output format.
> > 
> > What host bridge do you use this driver with ?
> 
> I only tested with blackfin.
> 
> >> + */
> > 
> > [snip]
> > 
> >> +struct mt9m114_reg {
> >> +     u16 reg;
> >> +     u32 val;
> >> +     int width;
> >> +};
> >> +
> >> +enum {
> >> +     MT9M114_QVGA,
> >> +     MT9M114_VGA,
> >> +     MT9M114_WVGA,
> >> +     MT9M114_720P,
> >> +};
> > 
> > This is the part I don't like. Instead of hardcoding 4 different
> > resolutions and using large register address/value tables, you should
> > compute the register values from the image size requested by the user.
> 
> In fact we get this table with the Aptina development tool. So we only
> support fixed resolutions. If we compute each register value, it only makes
> the code more complex.

But it also makes the code more useful, as the user won't be limited to the 4 
resolutions above.

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2013-03-28  9:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 22:00 [PATCH RFC] [media] add Aptina mt9m114 HD digital image sensor driver Scott Jiang
2013-03-18 23:42 ` Mauro Carvalho Chehab
2013-03-27  0:51 ` Laurent Pinchart
2013-03-28  8:29   ` Scott Jiang
2013-03-28  9:10     ` Laurent Pinchart [this message]
2013-04-01  9:33       ` Scott Jiang
2013-04-04 13:34         ` Laurent Pinchart
2013-04-07 10:35           ` Scott Jiang
2013-04-29 20:58             ` Laurent Pinchart

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=1691028.0qtxercLZ8@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=scott.jiang.linux@gmail.com \
    --cc=uclinux-dist-devel@blackfin.uclinux.org \
    /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;
as well as URLs for NNTP newsgroup(s).