On 08/24/2013 09:03 PM, Mauro Carvalho Chehab wrote:
Em Fri, 23 Aug 2013 00:15:52 +0200
Frank Schäfer<fschaefer.oss@xxxxxxxxxxxxxx> escreveu:
Am 21.08.2013 23:42, schrieb Sylwester Nawrocki:
On 08/21/2013 10:39 PM, Frank Schäfer wrote:
Am 20.08.2013 18:34, schrieb Frank Schäfer:
Am 20.08.2013 15:38, schrieb Laurent Pinchart:
On Sunday 18 August 2013 12:20:08 Mauro Carvalho Chehab wrote:
Em Sun, 18 Aug 2013 13:40:25 +0200 Frank Schäfer escreveu:
Am 17.08.2013 12:51, schrieb Guennadi Liakhovetski:
Hi Frank,
As I mentioned on the list, I'm currently on a holiday, so,
replying
briefly.
Sorry, I missed that (can't read all mails on the list).
Since em28xx is a USB device, I conclude, that it's supplying
clock to
its components including the ov2640 sensor. So, yes, I think the
driver
should export a V4L2 clock.
Ok, so it's mandatory on purpose ?
I'll take a deeper into the v4l2-clk code and the
em28xx/ov2640/soc-camera interaction this week.
Have a nice holiday !
commit 9aea470b399d797e88be08985c489855759c6c60
Author: Guennadi Liakhovetski<g.liakhovetski@xxxxxx>
Date: Fri Dec 21 13:01:55 2012 -0300
[media] soc-camera: switch I2C subdevice drivers to use v4l2-clk
Instead of centrally enabling and disabling subdevice master
clocks in
soc-camera core, let subdevice drivers do that themselves,
using the
V4L2 clock API and soc-camera convenience wrappers.
Signed-off-by: Guennadi Liakhovetski<g.liakhovetski@xxxxxx>
Acked-by: Hans Verkuil<hans.verkuil@xxxxxxxxx>
Acked-by: Laurent Pinchart<laurent.pinchart@xxxxxxxxxxxxxxxx>
Signed-off-by: Mauro Carvalho Chehab<mchehab@xxxxxxxxxx>
(c/c the ones that acked with this broken changeset)
We need to fix it ASAP or to revert the ov2640 changes, as some
em28xx
cameras are currently broken on 3.10.
I'll also reject other ports to the async API if the drivers are
used outside an embedded driver, as no PC driver currently defines
any clock source. The same applies to regulators.
Guennadi,
Next time, please check if the i2c drivers are used outside
soc_camera
and apply the fixes where needed, as no regressions are allowed.
We definitely need to check all users of our sensor drivers when
making such a
change. Mistakes happen, so let's fix them.
Guennadi is on holidays until the end of this week. Would that be
too late to
fix the issue (given that 3.10 is already broken) ? The fix
shouldn't be too
complex, registering a dummy V4L2 clock in the em28xx driver should
be enough.
I would prefer either a) making the clock optional in the senor
driver(s) or b) implementing a real V4L2 clock.
Reading the soc-camera code, it looks like NULL-pointers for struct
v4l2_clk are handled correctly. so a) should be pretty simple:
priv->clk = v4l2_clk_get(&client->dev, "mclk");
- if (IS_ERR(priv->clk)) {
- ret = PTR_ERR(priv->clk);
- goto eclkget;
- }
+ if (IS_ERR(priv->clk))
+ priv->clk = NULL;
Some additional NULL-pointer checks might be necessary, e.g. before
calling v4l2_clk_put().
Tested and that works.
Patch follows.
That patch breaks subdevs registration through the v4l2-async. See commit
ef6672ea35b5bb64ab42e18c1a1ffc717c31588a
[media] V4L2: mt9m111: switch to asynchronous subdevice probing
Sensor probe() callback must return EPROBE_DEFER when the clock is not
found. This cause the sensor's probe() callback to be called again by
the driver core after some other driver has probed, e.g. the one that
registers v4l2_clk. If specific error code is not returned from probe()
the whole registration process breaks.
Urgh... great. :/
So the presence of a clock is used as indicator if the device is ready ?
Honestly, that sounds like a misuse... Is there no other way to check if
the device is ready ?
Please don't get me wrong, I noticed you've been working on the async
subdevice registration patches for quite a long time and I'm sure it
wasn't an easy task.
Yeah, constructive critics is always welcome ;)
The deferred probing mechanism has been getting more common recently, as
it is difficult to model all dependencies between devices. So if some
_resource_ for a device is missing its probe() is being deferred. It then
gets retried after some other device probed, e.g. the one that provides
the missing resource. So I can't see, what exactly is a misuse here ?
The interface was written to mimic what OF does with clock.
Kind of, as I see it we just pass control of one of device's resource to
its particular driver, rather than handling it somewhere else.
Typically image sensors in embedded systems need specific sequence of
voltage supply, GPIO and clock control. And its a driver of the device
that will have coded such sequences. We don't have board files any more
on systems using Device Tree, so any hack that used to live in board
files need to be replaced with proper, i.e. more exact driver/resource
modelling.
Yeah, I agree that this sucks for non OF drivers.
Yes, I agree. But we need to make it to suck as little as possible...
Not sure if it is relevant, but there has been some works on optional
regulator support: https://lkml.org/lkml/2013/7/30/334.
Presumably we could add a platform data flag indicating not to handle
a clock in subdev drivers. For those used by bridge drivers like em28xx.
On DT systems platform_data is in most cases NULL.
Btw: only 2 of the 14 drivers return -EPROBE_DEFER when no clock is
found: imx074, mt9m111m.
All others return the error code from v4l2_clk_get(), usually -ENODEV.
Probably because they weren't converted yet to the new way.
Yes, I saw only patches for those 2 sensors adding v4l2-async support.
Likely this is only what Guennadi could test.
Concerning b): I'm not yet sure if it is really needed/makes sense...
Who is supposed to configure/enable/disable the clock in a
constellation
like em28xx+ov2640 ?
For UXGA for example, the clock needs to be switched to 12MHz, while
24MHz is used for smaller reolutions.
But I'm not sure if it is a good idea to let the sensor driver do the
switch (to define fixed bindings between resoultions and clock
frequencies).
Btw, what if a frequency is requested which isn't supported ? Set the
clock to the next nearest supported frequency ?
Regards,
Frank
I tried to implement a v4l2_clk for the em28xx driver (not yet beeing
sure if it really makes sense) and I noticed the following problem:
The ov2640 driver (as well as all other sensor drivers) seems to have
specific expectations for the names of the clock.
The name must me "mclk" and dev_name must be the device name of the i2c
client device.
Is "mclk" supposed to be a clock type ? Wouldn't an enum be a better
choice in this case ?
This is made similar to the common clock API, a string is an identifier
of a clock for the device. I can't see anything unusual in that, it will
also make it easier to phase out the v4l2-clk API and replace it with
the common clock API once that is more widely available.
The name is supposed to come from the datasheet and usually be different
for each sensor, but since we mostly deal with just one clock a common
"mclk" name was chosen for simplicity.
Hmm... the common clock API probably needs to be more flexible.
An enum would be safer to use, that's my though.
With Device Tree per device clocks can be looked up by index. And mapping
of system clocks for a consumer device is done in the device tree. For
compatibility with original clock API names (character strings) are mapped
to those indexes. Which clock is which is described in a DT binding of
a device. Still drivers reference the clocks by name.
So in case of DT it is actually a mixture of enums/strings currently.
Most of the clock provider drivers expose a table of clocks and mapping
for clock consumers is done using a handle to DT node of the clocks
supplier + (in simplest case) an index to the table.
Again, this is due to OF/DT. Open Firmware/Device Tree wants to have a
flexible, OS-independent way to specify clock sources, device parameters,
etc.
Anyway, let's focus on the main issue.
Anyway, the sensor subdevices are registered using
v4l2_i2c_new_subdev_board(), which sets up an i2c client, loads the
module and returns v4l2_subdev.
The v4l2_clock needs to be registered before (otherwise no clock is
found during sensor probing), but at this point the device name of the
i2c_client isn't known yet...
[...]
snprintf(clk_name, sizeof(clk_name), "%d-%04x",
dev->i2c_adap[dev->def_i2c_bus].nr, ov2640_info.addr);
That's a joke, isn't it ? ;)
So people have to grub through half of the kernel to figure out which
specific string the subdev driver expects and duplicate the code that
creates this compound string to be able to use the driver ?
You're right, the drivers should not need to know detailed device names
as created in other subsystems (in this case i2C core).
It's easy to add a helper function to v4l2 core either returning clock
name or entirely registering a clock. However I don't want to see v4l2-clk
API spreading too much, it should rather die soon. We should use the
common clock API. x86 already enables COMMON_CLK.
Anyway, whether we use v4l2-clk or the common clk API is not something
those drivers that want use a dummy clock would need to know, it could
be handled entirely in the core.
And translation from a v4l2-clk user calls to the common clk provider
calls can be done easily in v4l2-clk.
You may ask why do we need all this complexity ? Because we want to have
common subdev drivers across all possible systems ?
There are some docs describing DT somewhere at Documentation.
Maybe Documentation/video4linux/v4l2-framework.txt?
Perhaps it is incomplete.
clk = v4l2_clk_register(&em28xx_sensor_clk_ops, clk_name, "mclk",
icd);
if (IS_ERR(icd->clk)) {
...
}
//////////////////////////////////////////////////////
subdev =
v4l2_i2c_new_subdev_board(&dev->v4l2_dev,
&dev->i2c_adap[dev->def_i2c_bus],
&ov2640_info, NULL);
...
Alternatively all sensors modified by changeset 9aea470b399d797e88be
"[media] soc-camera: switch I2C subdevice drivers to use v4l2-clk" could
receive a platform data flag that would be set for drivers like em28xx,
and which would be indicating if the clock should be used or not. It
probably should has been done originally if it wasn't clear which bridge
drivers use that modified sensors and that regressions were possible.
Yes, but not using a clock would still break the async subdevice
registration (although drivers like the em28xx likely don't need/use it
at the moment).
Well, async subdev only makes sense for Device Tree.
A synchronous init works a way better, as everything initializes at the
same order, every time. Allowing subdevs to initialize on a random order is
a mess, and should be avoided if possible, as we have already enough
complexity to handle. Let's not introduce more if not needed.
Yes, I agree with that.
It seems fine to only use the a new "dont_use_clk_api" flag on synchronous
init.
I guess it wouldn't be too bad. But if we were to introduce this optionality
into many subdevs just to satisfy a few bridge drivers I guess it's
better to
make a helper function to create a dummy clock and just use it in those few
bridge drivers. The memory waste argument seems bogus on PC systems. The
only
problem could be (under-documented ?) bridge-dependent clock frequency
requirements. But currently there is no clock frequency setting in those
affected soc-camera subdevs, just clock gating. It's interesting, who is
supposed to set frequency then ?
--
Regards,
Sylwester
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
