Add the document for ov2640 dt.
Cc: devicet...@vger.kernel.org
Signed-off-by: Josh Wu
---
v2 -> v3:
1. fix incorrect description.
2. Add assigned-clocks & assigned-clock-rates.
3. resetb pin should be ACTIVE_LOW.
v1 -> v2:
1. change the compatible string to be consistent with verdor file
The master clock (xvclk) is mandatory. It's a common clock framework clock.
It can make sensor output a pixel clock to the camera interface.
Cc: devicet...@vger.kernel.org
Signed-off-by: Josh Wu
---
v2 -> v3:
1. should return PTR_ERR().
v1 -> v2:
1. change the clock's name.
2. Make the clo
Add device tree support for ov2640.
Cc: devicet...@vger.kernel.org
Signed-off-by: Josh Wu
---
v2 -> v3:
1. fix gpiod usage.
2. refine the ov2640_probe() function.
v1 -> v2:
1. use gpiod APIs.
2. change the gpio pin's name according to datasheet.
3. reduce the delay for .reset() functio
To support async probe for ov2640, we need remove the code to get 'mclk'
in ov2640_probe() function. oterwise, if soc_camera host is not probed
in the moment, then we will fail to get 'mclk' and quit the ov2640_probe()
function.
So in this patch, we move such 'mclk' getting code to ov2640_s_power(
icd->control is the sub device dev, i.e. i2c device.
icd->pdev is the soc camera device's device.
To be consitent with power() function, we will call reset() with
icd->control as well.
Signed-off-by: Josh Wu
---
v2->v3:
1. check whether icd->control is NULL or not.
drivers/media/platform/soc
This patch series add device tree support for ov2640. And also add
the document for the devicetree properties.
v2->v3:
1. fix the gpiod_xxx api usage as we use reset pin as ACTIVE_LOW.
2. update the devicetree binding document.
v1 -> v2:
1. modified the dt bindings according to Laurent's s
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: Thu Dec 11 04:00:30 CET 2014
git branch: test
git hash: 71947828caef0c83d4245f7d1eaddc799b4ff1d1
gcc versio
On 10/12/14 23:54, Laurent Pinchart wrote:
> Hi William,
>
> Thank you for the patch.
>
> On Monday 08 December 2014 18:57:58 William Manley wrote:
>> The Magewell XI100DUSB-HDMI[1] video capture device reports the pixel
>> format "e436eb7d-524f-11ce-9f53-0020af0ba770". This is its GUID for
>> B
Convert au0828 to use videobuf2. Tested with NTSC.
Tested video and vbi devices with xawtv, tvtime,
and vlc. Ran v4l2-compliance to ensure there are
no new regressions in video and vbi now has 3 fewer
failures.
video before:
test VIDIOC_DBG_G/S_REGISTER: OK (Not Supported)
test VIDIOC_G_FMT: FAIL
Missing newline character at the end of string passed to dev_err()
Signed-off-by: Luis de Bethencourt
---
drivers/staging/media/lirc/lirc_zilog.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/media/lirc/lirc_zilog.c
b/drivers/staging/media/lirc/lirc_zilog.c
The previous patch switched some dev functions to move the string to a second
line. Doing this for all similar functions because it makes the driver easier
to read if all similar lines use the same criteria.
Signed-off-by: Luis de Bethencourt
---
drivers/staging/media/lirc/lirc_zilog.c | 57
checkpatch makes an exception to the 80-colum rule for quotes strings, and
Documentation/CodingStyle recommends not splitting quotes strings across lines
because it breaks the ability to grep for the string. Fixing these.
WARNING: quoted string split across lines
Signed-off-by: Luis de Bethencour
On Wed, Dec 10, 2014 at 04:01:04PM -0800, Joe Perches wrote:
> On Wed, 2014-12-10 at 23:57 +, Luis de Bethencourt wrote:
> > On Wed, Dec 10, 2014 at 03:39:09PM -0800, Joe Perches wrote:
> > > On Wed, 2014-12-10 at 22:33 +, Luis de Bethencourt wrote:
> > > > diff --git a/drivers/staging/medi
00>;
+interrupts = <9>;
+clocks = <&clks IMX5_CLK_VPU_REFERENCE_GATE>,
+ <&clks IMX5_CLK_VPU_GATE>;
+clock-names = "per", "ahb";
+resets = <&src 1>;
+
On Wed, 2014-12-10 at 23:57 +, Luis de Bethencourt wrote:
> On Wed, Dec 10, 2014 at 03:39:09PM -0800, Joe Perches wrote:
> > On Wed, 2014-12-10 at 22:33 +, Luis de Bethencourt wrote:
> > > diff --git a/drivers/staging/media/lirc/lirc_zilog.c
> > > b/drivers/staging/media/lirc/lirc_zilog.c
On Wed, Dec 10, 2014 at 03:39:09PM -0800, Joe Perches wrote:
> On Wed, 2014-12-10 at 22:33 +, Luis de Bethencourt wrote:
> > checkpatch makes an exception to the 80-colum rule for quotes strings, and
> > Documentation/CodingStyle recommends not splitting quotes strings across
> > lines
> > bec
Hi William,
Thank you for the patch.
On Monday 08 December 2014 18:57:58 William Manley wrote:
> The Magewell XI100DUSB-HDMI[1] video capture device reports the pixel
> format "e436eb7d-524f-11ce-9f53-0020af0ba770". This is its GUID for
> BGR 8:8:8.
>
> The UVC 1.5 spec[2] only defines GUIDs fo
On Wed, 2014-12-10 at 22:33 +, Luis de Bethencourt wrote:
> checkpatch makes an exception to the 80-colum rule for quotes strings, and
> Documentation/CodingStyle recommends not splitting quotes strings across lines
> because it breaks the ability to grep for the string. Fixing these.
[]
> diff
Hi Pavel and Jacek,
On Tue, Dec 09, 2014 at 04:50:33PM +0100, Pavel Machek wrote:
> On Tue 2014-12-09 09:54:06, Jacek Anaszewski wrote:
> > Hi Pavel,
> >
> > On 12/08/2014 09:18 PM, Pavel Machek wrote:
> > >On Mon 2014-12-08 17:55:20, Jacek Anaszewski wrote:
> > >>On 12/06/2014 01:43 PM, Pavel Ma
The previous patch switched some dev functions to move the string to a second
line. Doing this for all similar functions because it makes the driver easier
to read if all similar lines use the same criteria.
Signed-off-by: Luis de Bethencourt
---
drivers/staging/media/lirc/lirc_zilog.c | 57
checkpatch makes an exception to the 80-colum rule for quotes strings, and
Documentation/CodingStyle recommends not splitting quotes strings across lines
because it breaks the ability to grep for the string. Fixing these.
WARNING: quoted string split across lines
Signed-off-by: Luis de Bethencour
Hi all,
I'm trying to use VPU code driver on iMX51 with kernel 3.18, following
these steps:
- disabled DVI interface
- enabled LCD interface
- configured and enabled VPU
- copied iMX51 vpu firmware without header and renamed
v4l-coda7541-imx53.bin in /lib/firmware
Attached you can find the pa
From: Sakari Ailus
The flash capability register is already read as part of the limit
registers. Do no access it separately; instead use the value from the
limits.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp/smiapp-core.c |9 +
drivers/media/i2c/smiapp/smiapp.h |
From: Sakari Ailus
Also call smiapp_cleanup() in smiapp_remove(), replacing code that did the
same than the function.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp/smiapp-core.c |8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/media/i2c/smiapp/s
Clean up smiapp_init_controls() by adding newlines to appropriate places and
by removing superfluous error handling. The caller will clean up control
handlers in any case if the function fails.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp/smiapp-core.c | 19 ++-
1 f
From: Sakari Ailus
The pll_flags quirk just returned the extra PLL flags the sensor required,
but the init quirk is far more versatile. It can be used to perform any
extra initialisation needed by the sensor, including allocating memory for
sensor specific struct and creating sensor specific new
The default values and limits for certain controls need the knowledge of
available media bus codes or link frequencies. Create such controls later
on, so that most of the initialisation of the sensor has already been done
when the init quirk is called.
Signed-off-by: Sakari Ailus
---
drivers/med
Hi,
These patches contain cleanups, primarily in the sensor initialisation, and
replace the pll_flags quirk by a generic init quirk which, besides setting
pll flags, can be used to e.g. creating sensor specific controls.
--
Kind regards,
Sakari
--
To unsubscribe from this list: send the line "u
This makes the macros a little bit safer.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp/smiapp-quirk.h | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/media/i2c/smiapp/smiapp-quirk.h
b/drivers/media/i2c/smiapp/smiapp-quirk.h
index a24eb43.
As the controls creation is separated in two sections, the available media
bus codes and link frequencies can be enumerated later on.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp/smiapp-core.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/
Building with the attached random configuration file,
drivers/built-in.o: In function `smsusb_submit_urb':
smsusb.c:(.text+0xa8fdc): undefined reference to `smscore_getbuffer'
drivers/built-in.o: In function `smsusb_onresponse':
smsusb.c:(.text+0xa902f): undefined reference to
`smsendian_handle_me
* 'Greg Kroah-Hartman' | 2014-12-09 11:54:15 [-0500]:
>> You can unbind the HCD driver from the PCI-device via sysfs and this is
>> not something not only a developer does. This "unbind" calls the remove
>> function of the driver and the only difference between unbind and rmmod
>> is that the modu
Hi,
we recently fixed our CREATE_BUFS support in GStreamer master. It works
nicely with UVC drivers. The problem is that libv4l2 isn't aware of it,
and endup taking terribly decision the least quickly lead to crash.
I'm not sure what that right approach. It seems non-trivial to support
it, at lea
The v4l2_dev field of struct video_device must be set correctly.
This was never done for this driver, so no video nodes were created
anymore.
Signed-off-by: Hans Verkuil
---
drivers/media/platform/sh_veu.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/platform/sh_veu.c b/driv
Hi Mauro,
This patch series contains a bunch of cleanups:
- Remove emacs editor comments throughout drivers/media
- Switch last users of the deprecated get/set_crop pad ops to
get/set_selection.
- Drop obsolete get/set_crop and the unused enum_mbus_fmt ops.
- Small Kconfig improvement.
This us
Hi Jacek,
On Wed, Dec 03, 2014 at 05:06:54PM +0100, Jacek Anaszewski wrote:
> Add support for V4L2 Flash sub-device to the aat1290 LED Flash class
> driver. The support allows for V4L2 Flash sub-device to take the control
> of the LED Flash class device.
>
> Signed-off-by: Jacek Anaszewski
> Ack
On Wed, Dec 10, 2014 at 07:01:16PM +0530, Sumit Semwal wrote:
> Hi Daniel,
>
> Thanks a bunch for your review comments! A few comments, post our
> discussion at LPC;
>
> On 12 October 2014 at 00:25, Daniel Vetter wrote:
> > On Sat, Oct 11, 2014 at 01:37:55AM +0530, Sumit Semwal wrote:
> >> At pr
Hi Daniel,
Thanks a bunch for your review comments! A few comments, post our
discussion at LPC;
On 12 October 2014 at 00:25, Daniel Vetter wrote:
> On Sat, Oct 11, 2014 at 01:37:55AM +0530, Sumit Semwal wrote:
>> At present, struct device lacks a mechanism of exposing memory
>> access constraint
Hi!
> >>both sides: LED Flash class core and a LED Flash class driver.
> >>In the former the sysfs attribute write permissions would have
> >>to be decided in the runtime and in the latter caching mechanism
> >
> >Write attributes at runtime? Why? We can emulate sane and consistent
> >behaviour fo
On 12/09/2014 04:50 PM, Pavel Machek wrote:
On Tue 2014-12-09 09:54:06, Jacek Anaszewski wrote:
Hi Pavel,
On 12/08/2014 09:18 PM, Pavel Machek wrote:
On Mon 2014-12-08 17:55:20, Jacek Anaszewski wrote:
On 12/06/2014 01:43 PM, Pavel Machek wrote:
The format of a sysfs attribute should be co
On 12/10/2014 01:20 PM, Sylwester Nawrocki wrote:
Hi,
On 04/12/14 17:12, Pavel Machek wrote:
+- maxim,boost-mode :
+ In boost mode the device can produce up to 1.2A of total current
+ on both outputs. The maximum current on each output is reduced
+ to 625mA then. If there are
On 12/09/2014 03:41 PM, Lee Jones wrote:
On Tue, 09 Dec 2014, Jacek Anaszewski wrote:
On 12/09/2014 02:50 PM, Lee Jones wrote:
On Tue, 09 Dec 2014, Jacek Anaszewski wrote:
On 12/09/2014 11:04 AM, Lee Jones wrote:
On Tue, 09 Dec 2014, Jacek Anaszewski wrote:
On 12/09/2014 09:50 AM, Lee Jon
Hi,
On 04/12/14 17:12, Pavel Machek wrote:
+- maxim,boost-mode :
> >>+ In boost mode the device can produce up to 1.2A of total current
> >>+ on both outputs. The maximum current on each output is reduced
> >>+ to 625mA then. If there are two child led nodes defi
On 10/12/14 11:02, Jacek Anaszewski wrote:
+Optional properties:
>>> +- maxim,fleds : Array of current outputs in order: fled1, fled2.
s/current outputs/LED current regulator outputs used/ ?
>>> +Note: both current outputs can be connected to a single led
s/led/LED ? And there
Hi Jacek,
On Wed, Dec 10, 2014 at 11:02:07AM +0100, Jacek Anaszewski wrote:
> Hi Sakari,
>
> On 12/04/2014 12:40 PM, Jacek Anaszewski wrote:
>
> >On 12/04/2014 11:07 AM, Sakari Ailus wrote:
> >>Hi Jacek,
> >>
> >>On Wed, Dec 03, 2014 at 05:06:41PM +0100, Jacek Anaszewski wrote:
> >>>This patch a
These are mostly small improvements, having very small functionality
changes.
regards
Antti
The following changes since commit 71947828caef0c83d4245f7d1eaddc799b4ff1d1:
[media] mn88473: One function call less in mn88473_init() after error
(2014-12-04 16:00:47 -0200)
are available in the g
Hi Sakari,
On 12/04/2014 12:40 PM, Jacek Anaszewski wrote:
On 12/04/2014 11:07 AM, Sakari Ailus wrote:
Hi Jacek,
On Wed, Dec 03, 2014 at 05:06:41PM +0100, Jacek Anaszewski wrote:
This patch adds device tree binding documentation for
the flash cell of the Maxim max77693 multifunctional device
On 12/02/14 23:42, Ondrej Zary wrote:
> On Tuesday 02 December 2014 16:40:30 Hans Verkuil wrote:
>> This patch series deprecates the vino/saa7191 video driver (ancient SGI
>> Indy computer), the parallel port webcams bw-qcam, c-qcam and w9966, the
>> ISA video capture driver pms and the USB video c
48 matches
Mail list logo
