[lkml]   [2010]   [Nov]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH/RFC] core: add a function to safely try to get device driver owner
On Mon, 29 Nov 2010, Jonathan Corbet wrote:

> On Mon, 29 Nov 2010 23:10:50 +0100 (CET)
> Guennadi Liakhovetski <> wrote:
> > In my case I have two platform devices: CEU and CSI2. In some cases (with
> > parallel sensors) CEU operates on its own. With serial (CSI-2) camera
> > sensors we need the CSI2 driver. So, I want to
> > try_module_get(csi2_dev->driver->owner) the CSI2 driver from my CEU
> > driver. This call can Oops if not done safely. Am I missing something? Is
> > there an easier way to achieve the same?
> This looks exactly like what the V4L2 subdev mechanism was meant to do.
> Is there a reason you can't use that interface?

Subdev doesn't solve this completely. Media controller, probably, will,
not sure to what extent, but it is not yet in the mainline.

These my devices do use the subdev API, the CEU driver registers a
v4l2_device, and the CSI2 driver and the attached sensor register
v4l2_subdev instances. The problem is - when you register v4l2_subdev, you
have to specify the respective v4l2_device. In case of sensor (and other
I2C) drivers this is solved with I2C probing. Generally speaking, the
v4l2_device registers a device for the subdev driver, and expects a driver
to attach to it. Then, when the subdev driver probes with the newly
registered device, it passes its v4l2_subdev instance back with its
i2c_client object, and then the caller can match them. While doing so they
also allow a race like

if (!try_module_get(client->driver->driver.owner))

which is exactly what my patch is attempting to fix.

Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer

 \ /
  Last update: 2010-11-30 08:21    [W:0.068 / U:4.320 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site