Re: [PATCH][RESEND] [media] davinci: vpfe: remove deprecated IRQF_DISABLED

Hi Prabhakar On 02/25/2014 07:02 AM, Prabhakar Lad wrote: > Hi Michael, > > On Mon, Feb 24, 2014 at 11:01 AM, Prabhakar Lad > wrote: >> Hi Michael, >> >> On Thu, Feb 20, 2014 at 6:47 PM, Michael Opdenacker >> wrote: >>> Hi Laurent, >>> >>> On 02/20/2014 12:36 PM, Laurent Pinchart wrote: Hi

Re: [PATCH v2] media: soc-camera: OF cameras

Hi Bryan, On Mon, 24 Feb 2014, Bryan Wu wrote: > On Tue, Feb 18, 2014 at 10:40 AM, Bryan Wu wrote: > > On Wed, Feb 12, 2014 at 12:05 PM, Bryan Wu wrote: > >> From: Guennadi Liakhovetski > >> > >> With OF we aren't getting platform data any more. To minimise changes we > >> create all the missi

Re: [PATCH][RESEND] [media] davinci: vpfe: remove deprecated IRQF_DISABLED

Hi Michael, On Mon, Feb 24, 2014 at 11:01 AM, Prabhakar Lad wrote: > Hi Michael, > > On Thu, Feb 20, 2014 at 6:47 PM, Michael Opdenacker > wrote: >> Hi Laurent, >> >> On 02/20/2014 12:36 PM, Laurent Pinchart wrote: >>> Hi Michael, >>> >>> What's the status of this patch ? Do expect Prabhakar to

Re: [GIT PULL FOR v3.15] Davinci VPFE Patches

Hi Mauro On Thu, Feb 20, 2014 at 12:21 PM, Prabhakar Lad wrote: > Hi Mauro, > > Please pull the following patch for davinci vpfe driver. > I have included one more patch from Michael, with a fresh pull request. Thanks, --Prabhakar Lad The following changes since commit efab6b6a6ea9364ececb955f6

cron job: media_tree daily build: WARNINGS

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: Tue Feb 25 04:00:21 CET 2014 git branch: test git hash: efab6b6a6ea9364ececb955f69a9d3ffc6b782a1 gcc versio

Re: [PATCH v2] media: soc-camera: OF cameras

On Tue, Feb 18, 2014 at 10:40 AM, Bryan Wu wrote: > On Wed, Feb 12, 2014 at 12:05 PM, Bryan Wu wrote: >> From: Guennadi Liakhovetski >> >> With OF we aren't getting platform data any more. To minimise changes we >> create all the missing data ourselves, including compulsory struct >> soc_camera_

Re: [PATCH v5 04/10] V4L: Add driver for s5k6a3 image sensor

Hi Sylwester, On Mon, Feb 24, 2014 at 06:35:16PM +0100, Sylwester Nawrocki wrote: > This patch adds subdev driver for Samsung S5K6A3 raw image sensor. > As it is intended at the moment to be used only with the Exynos > FIMC-IS (camera ISP) subsystem it is pretty minimal subdev driver. > It doesn't

Re: [PATCH] media: soc_camera: rcar_vin: Add support for 10-bit YUV cameras

Hi Phil, Thank you for the patch. On Monday 24 February 2014 15:49:05 Phil Edworthy wrote: > Signed-off-by: Phil Edworthy > --- > drivers/media/platform/soc_camera/rcar_vin.c |7 +++ > 1 file changed, 7 insertions(+) > > diff --git a/drivers/media/platform/soc_camera/rcar_vin.c > b/dri

Re: [patch] [media] em28xx-cards: don't print a misleading message

Thank you so much for the review. I should have noticed that myself... I will send a patch to correct the indenting instead. regards, dan carpenter -- 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

Re: [patch] [media] em28xx-cards: don't print a misleading message

Am 17.02.2014 21:04, schrieb Dan Carpenter: > There were some missing curly braces so it always says that the transfer > mode changed even if it didn't. It's not a transfer mode change, it's the initial selection (which never changes). The intention of this section is to print which interface (ty

Re: [PATCH v5 2/7] v4l: Use full 32 bits for buffer flags

Hi Hans, On Monday 24 February 2014 17:02:20 Hans Verkuil wrote: > On 02/24/2014 04:34 PM, Sakari Ailus wrote: > > Hans Verkuil wrote: > >> On 02/15/2014 09:53 PM, Sakari Ailus wrote: > >>> The buffer flags field is 32 bits but the defined only used 16. This is > >>> fine, but as more than 16 bits

[PATCH v5 05/10] V4L: s5c73m3: Add device tree support

This patch adds the V4L2 asynchronous subdev registration and device tree support. Common clock API is used to control the sensor master clock from within the subdev. Signed-off-by: Andrzej Hajda Signed-off-by: Sylwester Nawrocki Acked-by: Kyungmin Park --- Changes since v4: - none. Changes

Re: Support for Empia 2980 video/audio capture chip set

Am 06.02.2014 13:57, schrieb Keith Lawson: > On Mon, Jan 20, 2014 at 09:08:25PM +0100, Frank Schäfer wrote: >> On 17.01.2014 01:11, Keith Lawson wrote: >>> On Wed, Jan 15, 2014 at 10:37:44PM +0100, Frank Schäfer wrote: Am 14.01.2014 01:48, schrieb Keith Lawson: > On 2014-01-12 11:56, Fran

[PATCH v5 03/10] Documentation: devicetree: Update Samsung FIMC DT binding

This patch documents following updates of the Exynos4 SoC camera subsystem devicetree binding: - addition of #clock-cells property to 'camera' node - the #clock-cells property is needed when the sensor sub-devices use clock provided by the camera host interface, - addition of an optional c

[PATCH v5 09/10] ARM: dts: Add rear camera nodes for Exynos4412 TRATS2 board

This patch enables the rear facing camera (s5c73m3) on TRATS2 board by adding the I2C0 bus controller, s5c73m3 sensor, MIPI CSI-2 receiver and the sensor's voltage regulator supply nodes. Signed-off-by: Andrzej Hajda Acked-by: Kyungmin Park Signed-off-by: Sylwester Nawrocki --- Changes since v4

[PATCH v5 07/10] exynos4-is: Add clock provider for the SCLK_CAM clock outputs

This patch adds clock provider so the the SCLK_CAM0/1 output clocks can be accessed by image sensor devices through the clk API. Signed-off-by: Sylwester Nawrocki Acked-by: Kyungmin Park --- Changes since v4: - retrieve clk parent name through __clk_get_name() on the input clock instead of i

[PATCH v5 10/10] ARM: dts: exynos4: Update camera clk provider and s5k6a3 sensor node

Remove unused /camera/clock-controller node and required clock properties to the camera node. This is required for a clock provider that will be referenced by image sensor devices. Also add required clock related changes to s5k6a3 device node and afvdd regulator supply. Signed-off-by: Sylwester Na

[PATCH v5 08/10] exynos4-is: Add support for asynchronous subdevices registration

Add support for registering external sensor subdevs using v4l2-async API. The async API is used only for sensor subdevs and only for booting from DT. Signed-off-by: Sylwester Nawrocki Acked-by: Kyungmin Park --- Changes since v4: - call v4l2_async_notifier_register() only if any camera sensor

[PATCH v5 01/10] Documentation: dt: Add binding documentation for S5K6A3 image sensor

This patch adds binding documentation for the Samsung S5K6A3(YX) raw image sensor. Signed-off-by: Sylwester Nawrocki Acked-by: Kyungmin Park Acked-by: Mark Rutland --- Changes since v4: - none. Changes since v2: - rephrased 'clocks' and 'clock-names' properties' description; --- .../device

[PATCH v5 02/10] Documentation: dt: Add binding documentation for S5C73M3 camera

This adds DT binding documentation for Samsung S5C73M3 camera sensor with an embedded ISP. Signed-off-by: Sylwester Nawrocki Acked-by: Kyungmin Park Acked-by: Mark Rutland --- Changes since v4: - added missing unit-address at the example SPI device node; Changes since v3: - DT binding docume

[PATCH v5 06/10] exynos4-is: Use external s5k6a3 sensor driver

This patch removes the common fimc-is-sensor driver for image sensors that are normally controlled by the FIMC-IS firmware. The FIMC-IS driver now contains only a table of properties specific to each sensor. The sensor properties required for the ISP's firmware are parsed from device tree and retri

[PATCH v5 04/10] V4L: Add driver for s5k6a3 image sensor

This patch adds subdev driver for Samsung S5K6A3 raw image sensor. As it is intended at the moment to be used only with the Exynos FIMC-IS (camera ISP) subsystem it is pretty minimal subdev driver. It doesn't do any I2C communication since the sensor is controlled by the ISP and its own firmware. T

Re: [RFC PATCH] [media]: of: move graph helpers from drivers/media/v4l2-core to drivers/of

Am Dienstag, den 18.02.2014, 16:26 + schrieb Grant Likely: > On Tue, 18 Feb 2014 08:06:24 +0100, Sascha Hauer > wrote: > > Hi Grant, > > > > On Mon, Feb 17, 2014 at 06:14:51PM +, Grant Likely wrote: > > > On Tue, 11 Feb 2014 07:56:33 -0600, Rob Herring > > > wrote: > > > > On Tue, Feb

[PATCH v5 00/10] Add device tree support for Exynos4 camera interface

This series adds devicetree support for the front and rear camera of the Exynos4412 SoC Trats2 board. It converts related drivers to use the v4l2-async API. The SoC output clocks are provided to external image image sensors through the common clock API. This iteration includes mostly further chang

[PATCH 3/6] dma-buf: use reservation objects

This allows reservation objects to be used in dma-buf. it's required for implementing polling support on the fences that belong to a dma-buf. Signed-off-by: Maarten Lankhorst Acked-by: Mauro Carvalho Chehab #drivers/media/v4l2-core/ Acked-by: Thomas Hellstrom #drivers/gpu/drm/ttm --- drivers/b

[PATCH 1/6] fence: dma-buf cross-device synchronization (v17)

A fence can be attached to a buffer which is being filled or consumed by hw, to allow userspace to pass the buffer without waiting to another device. For example, userspace can call page_flip ioctl to display the next frame of graphics after kicking the GPU but while the GPU is still rendering. T

[PATCH 4/6] android: convert sync to fence api, v5

Just to show it's easy. Android syncpoints can be mapped to a timeline. This removes the need to maintain a separate api for synchronization. I've left the android trace events in place, but the core fence events should already be sufficient for debugging. v2: - Call fence_remove_callback in sync

[PATCH 5/6] reservation: add support for fences to enable cross-device synchronisation

Signed-off-by: Maarten Lankhorst Reviewed-by: Rob Clark --- include/linux/reservation.h | 20 +++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/include/linux/reservation.h b/include/linux/reservation.h index 813dae960ebd..f3f57460a205 100644 --- a/include/linux

[PATCH 6/6] dma-buf: add poll support, v3

Thanks to Fengguang Wu for spotting a missing static cast. v2: - Kill unused variable need_shared. v3: - Clarify the BUG() in dma_buf_release some more. (Rob Clark) Signed-off-by: Maarten Lankhorst --- drivers/base/dma-buf.c | 108 +++ include/linux

[PATCH 2/6] seqno-fence: Hardware dma-buf implementation of fencing (v5)

This type of fence can be used with hardware synchronization for simple hardware that can block execution until the condition (dma_buf[offset] - value) >= 0 has been met when WAIT_GEQUAL is used, or (dma_buf[offset] != 0) has been met when WAIT_NONZERO is set. A software fallback still has to be p

[PATCH 0/6] dma-buf synchronization patches (updated)

The following series implements fence and converts dma-buf and android sync to use it. Patch 5 and 6 add support for polling to dma-buf, blocking until all fences are signaled. Patches that received some minor updates: - seqno fence (wait condition member added) - android (whitespace changes and a

RE: [PATCH v5 2/7] v4l: Use full 32 bits for buffer flags

Hi, > From: Sakari Ailus [mailto:sakari.ai...@iki.fi] > Sent: Monday, February 24, 2014 4:35 PM > > Hans Verkuil wrote: > > On 02/15/2014 09:53 PM, Sakari Ailus wrote: > >> The buffer flags field is 32 bits but the defined only used 16. This > >> is fine, but as more than 16 bits will be used in

Re: [PATCH v5 2/7] v4l: Use full 32 bits for buffer flags

On 02/24/2014 04:34 PM, Sakari Ailus wrote: > Hans Verkuil wrote: >> On 02/15/2014 09:53 PM, Sakari Ailus wrote: >>> The buffer flags field is 32 bits but the defined only used 16. This is >>> fine, but as more than 16 bits will be used in the very near future, define >>> them as 32-bit numbers for

[PATCH] media: soc_camera: rcar_vin: Add support for 10-bit YUV cameras

Signed-off-by: Phil Edworthy --- drivers/media/platform/soc_camera/rcar_vin.c |7 +++ 1 file changed, 7 insertions(+) diff --git a/drivers/media/platform/soc_camera/rcar_vin.c b/drivers/media/platform/soc_camera/rcar_vin.c index 3b1c05a..9929375 100644 --- a/drivers/media/platform/soc_c

Re: [PATCH v5 2/7] v4l: Use full 32 bits for buffer flags

Hans Verkuil wrote: > On 02/15/2014 09:53 PM, Sakari Ailus wrote: >> The buffer flags field is 32 bits but the defined only used 16. This is >> fine, but as more than 16 bits will be used in the very near future, define >> them as 32-bit numbers for consistency. >> >> Signed-off-by: Sakari Ailus >

Re: [PATCH 4/6] android: convert sync to fence api, v4

op 19-02-14 14:56, Thomas Hellstrom schreef: >+static void fence_check_cb_func(struct fence *f, struct fence_cb *cb) >+{ >+ struct sync_fence_cb *check = container_of(cb, struct sync_fence_cb, cb); >+ struct sync_fence *fence = check->fence; >+ >+ // TODO: Add a fence->status member and che

af9035 vs. it913x

Hello, old it913x had support reporting of signal strength on IT9135 v2. af9035 driver does not. Could that be corrected ? And I would like to know: How to get and build drivers from source with patches which are presented in this forum. E.g. - driver it913x is now obsolete and IT9135 is now