From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/2] Add support ov772x driver setting for Migo-R
Date: Wed, 03 Dec 2008 09:38:52 +0000 [thread overview]
Message-ID: <20081203093852.GA14321@linux-sh.org> (raw)
In-Reply-To: <u3ah7m2kz.wl%morimoto.kuninori@renesas.com>
On Tue, Dec 02, 2008 at 04:38:34PM +0900, Kuninori Morimoto wrote:
>
> Signed-off-by: Kuninori Morimoto <morimoto.kuninori@renesas.com>
> ---
> this patch is for linux 2.6.29
> V4L2 maintainer said ov772x driver will be added to linux 2.6.29
>
As these depend on new headers and data structures, I will include these
with the second round of updates for the merge window, after the V4L2
merge has taken place.
> arch/sh/boards/mach-migor/setup.c | 22 ++++++++++++++++++++++
> 1 files changed, 22 insertions(+), 0 deletions(-)
>
> diff --git a/arch/sh/boards/mach-migor/setup.c b/arch/sh/boards/mach-migor/setup.c
> index 03d2dea..4b348d8 100644
> --- a/arch/sh/boards/mach-migor/setup.c
> +++ b/arch/sh/boards/mach-migor/setup.c
> @@ -441,6 +452,13 @@ static struct platform_device migor_ceu_device = {
> },
> };
>
> +struct ov772x_camera_info ov7725_info = {
> + .buswidth = SOCAM_DATAWIDTH_8,
> + .link = {
> + .power = ov7725_power,
> + },
> +};
> +
> static struct platform_device *migor_devices[] __initdata = {
> &smc91x_eth_device,
> &sh_keysc_device,
Also note that ov7725_info should be static, as you are assigning it to
platform_data and nothing outside of this file is using it otherwise.
next prev parent reply other threads:[~2008-12-03 9:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 7:38 [PATCH 1/2] Add support ov772x driver setting for Migo-R Kuninori Morimoto
2008-12-03 9:38 ` Paul Mundt [this message]
2008-12-03 10:23 ` morimoto.kuninori
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=20081203093852.GA14321@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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