[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100429130638.0abff0dc@tpl.lwn.net>
Date: Thu, 29 Apr 2010 13:06:38 -0600
From: Jonathan Corbet <corbet@....net>
To: Bruno Prémont <bonbons@...ux-vserver.org>
Cc: linux-kernel@...r.kernel.org, Harald Welte <laforge@...monks.org>,
linux-fbdev@...r.kernel.org, JosephChan@....com.tw,
ScottFang@...tech.com.cn,
Florian Tobias Schandinat <FlorianSchandinat@....de>
Subject: Re: [PATCH 24/30] viafb: Add a driver for the video capture engine
On Thu, 29 Apr 2010 19:16:24 +0200
Bruno Prémont <bonbons@...ux-vserver.org> wrote:
> I think the extra 'viafb-camera' entry should be wrapped into a
>
> #if defined(CONFIG_FB_VIA_CAMERA) || defined(CONFIG_FB_VIA_CAMERA_MODULE)
I think you're right, yes. (As noted above, the camera driver isn't
quite ready for merging yet - but I can't swear I would have caught
this one, so I'm glad you did).
> or probably better be dynamically added when camera module is loaded
> and/or detects/probes the camera sub-device.
That's a little harder - the platform device is the means by which the
camera and the core communicate. I guess I could add a general "I'm a
via-core subdev and I'm here now" exported function in the core, but
I'm not sure that would be better than just having the platform dev be
there.
But it definitely shouldn't be around if the camera is configured out.
Thanks,
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists