Tomasz Figa wrote:
>
> Exynos4212 and Exynos4412 SoCs differ only in number of ARM cores and
> there is no need to have separate Kconfig options for them, since they
> use the same code.
>
> This patch removes CONFIG_SOC_EXYNOS4412, leaving CONFIG_SOC_EXYNOS4212
> as the one supporting both SoCs
Hi Mauro,
Please pull these two patches for the mt9p031 sensor.
The following changes since commit ab5060cdb8829c0503b7be2b239b52e9a25063b4:
[media] drxk_hard: Remove most 80-cols checkpatch warnings (2013-06-08
22:11:39 -0300)
are available in the git repository at:
git://linuxtv.org/pin
Hi Guennadi,
On 06/14/2013 10:45 PM, Guennadi Liakhovetski wrote:
On Fri, 14 Jun 2013, Laurent Pinchart wrote:
> On Friday 14 June 2013 21:08:10 Guennadi Liakhovetski wrote:
> > v11 of the V4L2 clock helper and asynchronous probing patch set.
> > Functionally identical to v10, only differ
On 06/13/13 19:10, Duval Mickael wrote:
Hello,
Hi,
I send this email to you for a DVB-T scan file for the city of Cherbourg
FRANCE, modified with the last channels.
I also enclose a package file that includes all channels available for
DVB-T in France.
I've applied your patch (after manually
Set freqency during initialization to fix v4l2-compliance error.
This also fixes VIDIOC_G_FREQUENCY always returning zero (broken by me during
LM7000 conversion).
Signed-off-by: Ondrej Zary
---
drivers/media/radio/radio-sf16fmi.c | 25 +
1 files changed, 17 insertions(
These patches fix two remaining v4l2-compliance problems of radio-sf16fmi
driver after
control framework conversion:
http://www.mail-archive.com/linux-media%40vger.kernel.org/msg62772.html
Tested with SF16-FMI card.
--
Ondrej Zary
--
To unsubscribe from this list: send the line "unsubscribe li
Fix v4l2-compliance in VIDIOC_QUERYCAP by changing "ISA" to "ISA:radio-sf16fmi".
Signed-off-by: Ondrej Zary
---
drivers/media/radio/radio-sf16fmi.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/media/radio/radio-sf16fmi.c
b/drivers/media/radio/radio-sf16fmi.c
Please add support this tuner to v4l.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Laurent
On Fri, 14 Jun 2013, Laurent Pinchart wrote:
> Hi Guennadi,
>
> Thank you for the patches.
>
> On Friday 14 June 2013 21:08:10 Guennadi Liakhovetski wrote:
> > v11 of the V4L2 clock helper and asynchronous probing patch set.
> > Functionally identical to v10, only differences are a c
Hi Guennadi,
Thank you for the patches.
On Friday 14 June 2013 21:08:10 Guennadi Liakhovetski wrote:
> v11 of the V4L2 clock helper and asynchronous probing patch set.
> Functionally identical to v10, only differences are a couple of comment
> lines and one renamed struct field - as requested by
Add support for asynchronous subdevice probing, using the v4l2-async API.
The legacy synchronous mode is still supported too, which allows to
gradually update drivers and platforms. The selected approach adds a
notifier for each struct soc_camera_device instance, i.e. for each video
device node, ev
Both synchronous and asynchronous imx074 subdevice probing is supported by
this patch.
Signed-off-by: Guennadi Liakhovetski
---
drivers/media/i2c/soc_camera/imx074.c | 20 +---
1 files changed, 17 insertions(+), 3 deletions(-)
diff --git a/drivers/media/i2c/soc_camera/imx074.c
v11 of the V4L2 clock helper and asynchronous probing patch set.
Functionally identical to v10, only differences are a couple of comment
lines and one renamed struct field - as requested by respectable
reviewers :)
Only patches #15, 16 and 18 changed.
Guennadi Liakhovetski (21):
soc-camera:
Typical video devices like camera sensors require an external clock source.
Many such devices cannot even access their hardware registers without a
running clock. These clock sources should be controlled by their consumers.
This should be performed, using the generic clock framework. Unfortunately
Use the v4l2-async API to support asynchronous subdevice probing,
including the CSI2 subdevice. Synchronous probing is still supported too.
Signed-off-by: Guennadi Liakhovetski
---
.../platform/soc_camera/sh_mobile_ceu_camera.c | 134 +-
drivers/media/platform/soc_camera/sh_
It is often useful to have simple means to get from a subdevice to the
underlying physical device. This patch adds such a pointer to struct
v4l2_subdev and sets it accordingly in the I2C and SPI cases.
Signed-off-by: Guennadi Liakhovetski
---
v11: extended a comment
drivers/media/v4l2-core/v4l
Add an OF hook to sh_mobile_ceu_camera.c, no properties so far. Booting
with DT also requires platform data to be optional.
Signed-off-by: Guennadi Liakhovetski
---
.../platform/soc_camera/sh_mobile_ceu_camera.c | 33 ++--
1 files changed, 23 insertions(+), 10 deletions(-)
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
---
drivers/media/i2c/soc_camera/imx074.c | 18 ++-
Currently bridge device drivers register devices for all subdevices
synchronously, typically, during their probing. E.g. if an I2C CMOS sensor
is attached to a video bridge device, the bridge driver will create an I2C
device and wait for the respective I2C driver to probe. This makes linking
of dev
Register the imx074 camera I2C and the CSI-2 platform devices directly
in board platform data instead of letting the sh_mobile_ceu_camera driver
and the soc-camera framework register them at their run-time. This uses
the V4L2 asynchronous subdevice probing capability.
Signed-off-by: Guennadi Liakh
Some CEU implementations have non-standard (larger) maximum supported
width and height values. Add two OF properties to specify them.
Signed-off-by: Guennadi Liakhovetski
---
.../devicetree/bindings/media/sh_mobile_ceu.txt| 18 +++
.../platform/soc_camera/sh_mobile_ceu_camera.c
Exynos4212 and Exynos4412 SoCs differ only in number of ARM cores and
there is no need to have separate Kconfig options for them, since they
use the same code.
This patch removes CONFIG_SOC_EXYNOS4412, leaving CONFIG_SOC_EXYNOS4212
as the one supporting both SoCs from this series.
Cc: "Rafael J.
Hi Arun,
On 06/14/2013 03:21 PM, Arun Kumar K wrote:
> On Fri, Jun 14, 2013 at 3:23 PM, Sylwester Nawrocki
> wrote:
>> On 06/14/2013 11:26 AM, Arun Kumar K wrote:
> + static const char * const vpx_num_partitions[] = {
> + "1 partition",
> + "2 partitions",
When adding and removing a client, the atmel-isi camera host driver only
activates and deactivates its camera interface respectively, which doesn't
include any client-specific actions. Move this functionality into
.clock_start() and .clock_stop() callbacks.
Signed-off-by: Guennadi Liakhovetski
--
When adding and removing a client, the pxa-camera driver only activates
and deactivates its camera interface respectively, which doesn't include
any client-specific actions. Move this functionality into .clock_start()
and .clock_stop() callbacks.
Signed-off-by: Guennadi Liakhovetski
---
drivers/
All existing soc-camera host drivers use .clock_start() and .clock_stop()
callbacks to activate and deactivate their camera interfaces, whereas
.add() and .remove() callbacks are usually dummy. Make the former two
compulsory and the latter two optional.
Signed-off-by: Guennadi Liakhovetski
---
d
When adding and removing a client, the sh-mobile-ceu-camera driver activates
and, respectively, deactivates its camera interface and, if necessary, the
CSI2 controller. Only handling of the CSI2 interface is client-specific and
is only needed, when a data-exchange with the client is taking place. M
All soc-camera host drivers include a pointer to an soc-camera device in
their host private struct to check, that only one client is connected.
Move this common code to soc_camera.c.
Signed-off-by: Guennadi Liakhovetski
---
drivers/media/platform/soc_camera/atmel-isi.c | 10 +-
driver
When adding and removing a client, the mx3-camera driver only activates
and deactivates its camera interface respectively, which doesn't include
any client-specific actions. Move this functionality into .clock_start()
and .clock_stop() callbacks.
Signed-off-by: Guennadi Liakhovetski
---
drivers/
When adding and removing a client, the omap1-camera driver only activates
and deactivates its camera interface respectively, which doesn't include
any client-specific actions. Move this functionality into .clock_start()
and .clock_stop() callbacks.
Signed-off-by: Guennadi Liakhovetski
---
driver
Currently soc-camera uses a single camera host callback to activate the
interface master clock and to configure the interface for a specific
client. However, during probing we might not have the information about
a client, we just need to activate the clock. Add new camera host driver
callbacks to
When adding and removing a client, the mx1-camera driver only activates
and deactivates its camera interface respectively, which doesn't include
any client-specific actions. Move this functionality into .clock_start()
and .clock_stop() callbacks.
Signed-off-by: Guennadi Liakhovetski
---
drivers/
During client probing we only have to turn on the host's clock, no need to
actually attach the client to the host.
Signed-off-by: Guennadi Liakhovetski
---
drivers/media/platform/soc_camera/soc_camera.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/media/p
When adding and removing a client, the mx2-camera driver only activates
and deactivates its camera interface respectively, which doesn't include
any client-specific actions. Move this functionality into .clock_start()
and .clock_stop() callbacks.
Signed-off-by: Guennadi Liakhovetski
---
drivers/
This patch changes the firmware file names of the FIMC-IS subsystem.
It is needed since there are different firmwares used across various
SoC series, e.g. Exynos4 and Exynos5.
Also the sensor specific "setfile" name is changed, to account for
it depends on an image sensor and is also specific to t
This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date: Fri Jun 14 19:00:22 CEST 2013
git branch: test
git hash: dd8c393b3c39f7ebd9ad69ce50cc836773d512b6
gcc versi
This patch adds support for the Exynos5250 SoC variant of the FIMC-LITE
IP. A 'compatible' string is added for Exynos5250 compatible devices
and the capture DMA handling is reworked to use the FLITE_REG_CIFCNTSEQ
register, masking output DMA buffer address slots. The frame interrupt
is enabled so t
The FIMC-LITE IP block is available only on platforms instantiated
from device tree.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
drivers/media/platform/exynos4-is/fimc-lite.c |3 ---
drivers/media/platform/exynos4-is/fimc-lite.h |3 ---
2 files changed, 6 deletion
The ISP clock register content is not preserved over the ISP power domain
off/on cycle. Instead of setting the clock frequencies once at probe time
the clock rates set up is moved to the runtime_resume handler, which is
invoked after the related power domain is already enabled, ensuring the
clocks
Generic PHY drivers are used to handle the MIPI CSIS and MIPI DSIM
DPHYs so we can remove now unused code at arch/arm/plat-samsung.
In case there is any board file for S5PV210 platforms using MIPI
CSIS/DSIM (not any upstream currently) it should use the generic
PHY API to bind the PHYs to respectiv
Use the generic PHY API instead of the platform callback to control
the MIPI CSIS DPHY.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
drivers/media/platform/exynos4-is/mipi-csis.c | 11 +--
include/linux/platform_data/mipi-csis.h |9 -
2 files ch
Add PHY provider node for the MIPI CSIS and MIPI DSIM PHYs.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
arch/arm/boot/dts/exynos4.dtsi | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4.dtsi b/arch/arm/boot/dts/exynos4.dtsi
index
Use the generic PHY API instead of the platform callback to control
the MIPI DSIM DPHY.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
drivers/video/display/source-exynos_dsi.c | 36 +
include/video/exynos_dsi.h|5
2 fil
Add a PHY provider driver for the Samsung S5P/Exynos SoC MIPI CSI-2
receiver and MIPI DSI transmitter DPHYs.
Signed-off-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
.../bindings/phy/exynos-video-mipi-phy.txt | 16 ++
drivers/phy/Kconfig| 10
Hi,
The following is a simple driver for the Samsung S5P/Exynos SoCs MIPI CSI-2
receiver and MIPI DSI transmitter DPHYs, using the generic PHY framework [1].
Previously the MIPI CSIS and MIPI DSIM used a platform callback to control
the PHY power enable and reset bits. The callback can be dropped
On Fri June 14 2013 15:59:26 Devin Heitmueller wrote:
> Making G_TUNER calls can take a long time on some tuners, in
> particular those that load firmware or do power management. As a
> result, we don't want to call G_TUNER unless the user is actually
> doing a tuning related call. The current co
Know this information and you would succeed with ladies.
http://r.instinctbot.pw
Unsubscribe:
http://uns.mountain-lion.pw
88932
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo in
Making G_TUNER calls can take a long time on some tuners, in
particular those that load firmware or do power management. As a
result, we don't want to call G_TUNER unless the user is actually
doing a tuning related call. The current code makes a G_TUNER
call regardless of what command the user is
Has anyone here tried the Ion "Video 2 PC" converter? I picked one up
from the clearance shelf at Staples yesterday, but don't see any way to
use it on my Slackware workstations. I did plug it in and got the
following data.
-8< --
tail /var/l
Em Fri, 14 Jun 2013 09:15:02 +0200
Hans de Goede escreveu:
> Hi All,
>
> IIRC the 0.9.x series were meant as development releases leading up to a new
> stable 1.0.0 release. Lately there have been no maintenance 0.8.x releases
> and a lot of interesting development going on in the 0.9.x, while a
Hi Sylwester,
On Fri, Jun 14, 2013 at 3:23 PM, Sylwester Nawrocki
wrote:
> Hi Arun,
>
> On 06/14/2013 11:26 AM, Arun Kumar K wrote:
>> Hi Sylwester,
>>
+ static const char * const vpx_num_partitions[] = {
+ "1 partition",
+ "2 partitions",
+
Hi Guennadi,
On Friday 14 June 2013 09:14:48 Guennadi Liakhovetski wrote:
> On Thu, 13 Jun 2013, Sylwester Nawrocki wrote:
> > Hi Guennadi,
> >
> > Overall it looks quite neat at this v10. :)
>
> Thanks :)
>
> > On 06/11/2013 10:23 AM, Guennadi Liakhovetski wrote:
> > > Currently bridge device
Hi Sylwester,
On Friday 14 June 2013 11:40:12 Sylwester Nawrocki wrote:
> On 06/14/2013 11:14 AM, Guennadi Liakhovetski wrote:
> > On Fri, 14 Jun 2013, Hans Verkuil wrote:
> >> On Fri 14 June 2013 09:14:48 Guennadi Liakhovetski wrote:
> >>> On Thu, 13 Jun 2013, Sylwester Nawrocki wrote:
> On
I've got a fix for a really bad performance bug, so if you can hold
off on doing a release a couple of hours until I can get in front of
my Linux box and submit a patch, I would appreciate it.
Thanks,
Devin
On Fri, Jun 14, 2013 at 4:51 AM, Hans Verkuil wrote:
> On Fri 14 June 2013 09:15:02 Hans
Hi Arun,
On 06/14/2013 11:26 AM, Arun Kumar K wrote:
> Hi Sylwester,
>
>>> + static const char * const vpx_num_partitions[] = {
>>> + "1 partition",
>>> + "2 partitions",
>>> + "4 partitions",
>>> + "8 partitions",
>>> + NULL,
>>> +
On Fri, 14 Jun 2013, Sylwester Nawrocki wrote:
> Hi,
>
> On 06/14/2013 11:14 AM, Guennadi Liakhovetski wrote:
> > On Fri, 14 Jun 2013, Hans Verkuil wrote:
> >> On Fri 14 June 2013 09:14:48 Guennadi Liakhovetski wrote:
> >>> On Thu, 13 Jun 2013, Sylwester Nawrocki wrote:
> On 06/11/2013 10:23
Hi,
On 06/14/2013 11:14 AM, Guennadi Liakhovetski wrote:
> On Fri, 14 Jun 2013, Hans Verkuil wrote:
>> On Fri 14 June 2013 09:14:48 Guennadi Liakhovetski wrote:
>>> On Thu, 13 Jun 2013, Sylwester Nawrocki wrote:
On 06/11/2013 10:23 AM, Guennadi Liakhovetski wrote:
[...]
> + * @v4l2_dev:
Hi Sylwester,
>> + static const char * const vpx_num_partitions[] = {
>> + "1 partition",
>> + "2 partitions",
>> + "4 partitions",
>> + "8 partitions",
>> + NULL,
>> + };
>> + static const char * const vpx_num_ref_frames[] =
Hi Hans
On Fri, 14 Jun 2013, Hans Verkuil wrote:
> On Fri 14 June 2013 09:14:48 Guennadi Liakhovetski wrote:
> > Hi Sylwester
> >
> > On Thu, 13 Jun 2013, Sylwester Nawrocki wrote:
> >
> > > Hi Guennadi,
> > >
> > > Overall it looks quite neat at this v10. :)
> >
> > Thanks :)
> >
> > > On 0
On Fri 14 June 2013 09:14:48 Guennadi Liakhovetski wrote:
> Hi Sylwester
>
> On Thu, 13 Jun 2013, Sylwester Nawrocki wrote:
>
> > Hi Guennadi,
> >
> > Overall it looks quite neat at this v10. :)
>
> Thanks :)
>
> > On 06/11/2013 10:23 AM, Guennadi Liakhovetski wrote:
> > > Currently bridge dev
On Fri 14 June 2013 09:15:02 Hans de Goede wrote:
> Hi All,
>
> IIRC the 0.9.x series were meant as development releases leading up to a new
> stable 1.0.0 release. Lately there have been no maintenance 0.8.x releases
> and a lot of interesting development going on in the 0.9.x, while at the
> sam
Hi All,
IIRC the 0.9.x series were meant as development releases leading up to a new
stable 1.0.0 release. Lately there have been no maintenance 0.8.x releases
and a lot of interesting development going on in the 0.9.x, while at the
same time there have been no issues reported against 0.9.x (iow
Hi Sylwester
On Thu, 13 Jun 2013, Sylwester Nawrocki wrote:
> Hi Guennadi,
>
> Overall it looks quite neat at this v10. :)
Thanks :)
> On 06/11/2013 10:23 AM, Guennadi Liakhovetski wrote:
> > Currently bridge device drivers register devices for all subdevices
> > synchronously, tupically, duri
63 matches
Mail list logo
