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: Sat Oct 28 05:00:17 CEST 2017
media-tree git hash:bbae615636155fa43a9b0fe0ea31c678984be864
media_build gi
Hi Mauro,
Here are the atomisp cleanups that were dependent the fixes. Included is
Andy's patches to remove unused code (no hardware, makes fixing
atomisp/sensor interfaces difficult). Also Kee Cook's timer fixes are in.
Please pull.
The following changes since commit bbae615636155fa43a9b0fe0ea
From: Andy Shevchenko
struct camera_af_platform_data and bound functions are not used anywhere.
Signed-off-by: Andy Shevchenko
Signed-off-by: Sakari Ailus
---
since v1:
- Remove af_power_ctrl which is now unused.
.../media/atomisp/include/linux/atomisp_platform.h | 6 ---
.../platform/inte
From: Colin Ian King
Variable freq is initialized to f->frequency however this value
is never read and freq is later updated; hence the initialization
is redundant and can be removed.
Cleans up clang warning:
drivers/media/radio/radio-raremono.c:257:6: warning: Value stored
to 'freq' during its
Hi,
On Fri, Oct 27, 2017 at 11:26:29AM +0300, Sakari Ailus wrote:
> Refactor the V4L2 async framework a little in preparation for async
> sub-device notifiers. This avoids making some structural changes in the
> patch actually implementing sub-device notifiers, making that patch easier
> to review
Hi,
On Thu, Oct 26, 2017 at 10:53:25AM +0300, Sakari Ailus wrote:
> Register the sub-device before calling the notifier's bound callback.
> Doing this the other way around is problematic as the struct v4l2_device
> has not assigned for the sub-device yet and may be required by the bound
> callback
Hi,
On Thu, Oct 26, 2017 at 10:53:26AM +0300, Sakari Ailus wrote:
> The information on how many async sub-devices would be bindable to a
> notifier is typically dependent on information from platform firmware and
> it's not driver's business to be aware of that.
>
> Many V4L2 main drivers are per
Hi,
On Thu, Oct 26, 2017 at 10:53:22AM +0300, Sakari Ailus wrote:
> If no source pads are found in an entity, print the name of the entity.
>
> Signed-off-by: Sakari Ailus
> Acked-by: Hans Verkuil
> Acked-by: Pavel Machek
> ---
Reviewed-by: Sebastian Reichel
-- Sebastian
> drivers/media/p
Hi,
On Thu, Oct 26, 2017 at 10:53:24AM +0300, Sakari Ailus wrote:
> Add three helper functions to call async operations callbacks. Besides
> simplifying callbacks, this allows async notifiers to have no ops set,
> i.e. it can be left NULL.
>
> Signed-off-by: Sakari Ailus
> Acked-by: Hans Verkuil
Hi,
On Thu, Oct 26, 2017 at 10:53:23AM +0300, Sakari Ailus wrote:
> From: Laurent Pinchart
>
> The async subdev notifier .bound(), .unbind() and .complete() operations
> are function pointers stored directly in the v4l2_async_subdev
> structure. As the structure isn't immutable, this creates a p
Hi Mauro,
On Fri, Oct 27, 2017 at 04:25:08PM +0200, Mauro Carvalho Chehab wrote:
> Em Thu, 19 Oct 2017 18:21:20 +0300
> Sakari Ailus escreveu:
>
> > Hi Mauro,
> >
> > Here's the second version of the atomisp pull request. Since v1, I've added
> > more patches, including an oops fix from Hans de
Hi,
On Thu, Oct 26, 2017 at 10:53:21AM +0300, Sakari Ailus wrote:
> We only want to link sub-devices that were bound to the async notifier the
> isp driver registered but there may be other sub-devices in the
> v4l2_device as well. Check for the correct async notifier.
>
> Signed-off-by: Sakari A
Hi,
On Thu, Oct 26, 2017 at 10:53:19AM +0300, Sakari Ailus wrote:
> Instead of using a custom driver implementation, use
> v4l2_async_notifier_parse_fwnode_endpoints() to parse the fwnode endpoints
> of the device.
>
> Signed-off-by: Sakari Ailus
> Acked-by: Hans Verkuil
> Reviewed-by: Laurent
Hi,
On Thu, Oct 26, 2017 at 10:53:14AM +0300, Sakari Ailus wrote:
> The notifier complete callback may return an error. This error code was
> simply returned to the caller but never handled properly.
>
> Move calling the complete callback function to the caller from
> v4l2_async_test_notify and u
On Thu, Oct 26, 2017 at 10:53:37AM +0300, Sakari Ailus wrote:
> Document optional lens-focus and flash-leds properties for the smiapp
> driver.
>
> Signed-off-by: Sakari Ailus
> Acked-by: Hans Verkuil
> Acked-by: Pavel Machek
> ---
> Documentation/devicetree/bindings/media/i2c/nokia,smia.txt |
Em Thu, 19 Oct 2017 18:21:20 +0300
Sakari Ailus escreveu:
> Hi Mauro,
>
> Here's the second version of the atomisp pull request. Since v1, I've added
> more patches, including an oops fix from Hans de Goede and move to
> timer_setup from Kees Cook. Also Andy's patches to clean up the driver are
On Wed, Aug 2, 2017 at 9:00 AM, wrote:
> From: Olli Salonen
>
> Xbox One Digital TV Tuner is a low-cost USB 2.0 multistandard TV tuner. It
> supports DVB-T, DVB-T2 and DVB-C broadcast standards.
>
> USB bridge: DibCom 0700C
> Demodulator: Panasonic MN88472
> Tuner: TDA18250BHN
>
> The demodulato
On 2017-10-26 10:53:36 +0300, Sakari Ailus wrote:
> Add a convenience function for parsing firmware for information on related
> devices using v4l2_async_notifier_parse_fwnode_sensor_common() registering
> the notifier and finally the async sub-device itself.
>
> This should be useful for sensor d
Hi Mauro,
This pull request includes two fixes for the atomisp driver. This replaces
the earlier atomisp pull request.
Please pull.
The following changes since commit 61065fc3e32002ba48aa6bc3816c1f6f9f8daf55:
Merge commit '3728e6a255b5' into patchwork (2017-10-17 17:22:20 -0700)
are availa
Hi Wenyou,
Unfortunately the v4 patch series was just merged instead of v5. Can you make a
new
patch applying just the v4 -> v5 changes?
Thanks!
Hans
On 10/27/2017 05:21 AM, Wenyou Yang wrote:
> To improve the readability of code, rework the format list table,
> split the format array
Hi Wenyou,
On Fri, Oct 27, 2017 at 03:42:20PM +0800, Wenyou Yang wrote:
> Add the device tree binding documentation for ov7740 driver and
> add a new entry of ov7740 to the MAINTAINERS file.
>
> Signed-off-by: Wenyou Yang
> ---
>
> Changes in v2:
> - Split off the bindings into a separate patc
While registering a notifier, check that each newly added fwnode is
unique, and return an error if it is not. Also check that a newly added
notifier does not have the same fwnodes twice.
Signed-off-by: Sakari Ailus
Acked-by: Hans Verkuil
Acked-by: Niklas Söderlund
---
drivers/media/v4l2-core/v
On Wed, Aug 2, 2017 at 9:00 AM, wrote:
> From: Olli Salonen
>
> NXP TDA18250 silicon tuner driver.
>
> Version 3 removes regmap_exit as I was pointed out that device
> management code automatically frees the regmap.
>
> Signed-off-by: Olli Salonen
Reviewed-by: Michael Ira Krufky
> ---
> dri
The atomisp driver uses the videobuf1 framework for buffer management. The
framework is being removed; switch to videobuf2 needs to be made. There
are only a handful of remaining non-staging drivers using videobuf1.
Signed-off-by: Sakari Ailus
---
drivers/staging/media/atomisp/TODO | 2 ++
1 fil
On 2017-10-26 10:53:33 +0300, Sakari Ailus wrote:
> Add function v4l2_fwnode_reference_parse() for parsing them as async
> sub-devices. This can be done on e.g. flash or lens async sub-devices that
> are not part of but are associated with a sensor.
>
> Signed-off-by: Sakari Ailus
> Acked-by: Han
Hi Sakari,
On 2017-10-27 13:06:09 +0300, Sakari Ailus wrote:
> Hi Niklas,
>
> On Fri, Oct 27, 2017 at 11:52:27AM +0200, Niklas Söderlund wrote:
> > Hi Sakari,
> >
> > Thanks for your patch.
> >
> > On 2017-10-26 10:53:29 +0300, Sakari Ailus wrote:
> > > While registering a notifier, check that
On Thu, Oct 19, 2017 at 11:30:34AM +0200, Arnd Bergmann wrote:
> The newly added driver has incorrect #ifdef annotations on its
> PM functions, leading to a harmless compile-time warning when
> CONFIG_PM is disabled:
>
> drivers/media/platform/rockchip/rga/rga.c:760:13: error: 'rga_disable_clocks'
On Fri, Oct 20, 2017 at 07:50:12PM -0200, Gustavo Padovan wrote:
From: Gustavo Padovan
Add section to VIDIOC_QBUF about it
v3:
- make the out_fence refer to the current buffer (Hans)
- Note what happens when the IN_FENCE is not set (Hans)
v2:
- mention that fences are
Hi Niklas,
On Fri, Oct 27, 2017 at 11:52:27AM +0200, Niklas Söderlund wrote:
> Hi Sakari,
>
> Thanks for your patch.
>
> On 2017-10-26 10:53:29 +0300, Sakari Ailus wrote:
> > While registering a notifier, check that each newly added fwnode is
> > unique, and return an error if it is not. Also ch
Hi Gustavo,
On Fri, Oct 20, 2017 at 07:50:11PM -0200, Gustavo Padovan wrote:
From: Gustavo Padovan
If V4L2_BUF_FLAG_OUT_FENCE flag is present on the QBUF call we create
an out_fence and send to userspace on the V4L2_EVENT_OUT_FENCE when
the buffer is queued to the driver, or right away if the
Hi Sakari,
Thanks for your patch.
On 2017-10-26 10:53:29 +0300, Sakari Ailus wrote:
> While registering a notifier, check that each newly added fwnode is
> unique, and return an error if it is not. Also check that a newly added
> notifier does not have the same fwnodes twice.
>
> Signed-off-by:
Hi Gustavo,
Sorry for the sporadic review... I'm struggling to get time to look at
these.
On Fri, Oct 20, 2017 at 07:50:10PM -0200, Gustavo Padovan wrote:
From: Gustavo Padovan
Add vb2_setup_out_fence() and the needed members to struct vb2_buffer.
v2: - change it to reflect fd_install at
Hi Mauro,
The smiapp driver no longer depends on s_power with these patches.
Please pull.
The following changes since commit 8382e556b1a2f30c4bf866f021b33577a64f9ebf:
Simplify major/minor non-dynamic logic (2017-10-11 15:32:11 -0400)
are available in the git repository at:
ssh://linuxtv.
On 10/27/2017 10:52 AM, Sergei Shtylyov wrote:
Add detection of source pad number for drivers aware of the media
controller API, so that the combination of soc_camera and rcar_vin
can create device nodes to support modern drivers such as adv7604.c
(for HDMI on Lager) and the converted adv7180.c
Hello!
On 7/23/2015 2:21 PM, William Towle wrote:
Add detection of source pad number for drivers aware of the media
controller API, so that the combination of soc_camera and rcar_vin
can create device nodes to support modern drivers such as adv7604.c
(for HDMI on Lager) and the converted adv718
On 2017-10-27 11:27:09 +0300, Sakari Ailus wrote:
> Registering a notifier has required the knowledge of struct v4l2_device
> for the reason that sub-devices generally are registered to the
> v4l2_device (as well as the media device, also available through
> v4l2_device).
>
> This information is n
Hi Sakari,
Thanks for your patch.
On 2017-10-27 11:26:29 +0300, Sakari Ailus wrote:
> Refactor the V4L2 async framework a little in preparation for async
> sub-device notifiers. This avoids making some structural changes in the
> patch actually implementing sub-device notifiers, making that patch
On Fri, Oct 27, 2017 at 10:10:02AM +0200, Niklas Söderlund wrote:
> > > @@ -151,6 +152,31 @@ static int v4l2_async_match_notify(struct
> > > v4l2_async_notifier *notifier,
> > > return 0;
> > > }
> > >
> > > +/* Test all async sub-devices in a notifier for a match. */
> > > +static int v4l2_a
Registering a notifier has required the knowledge of struct v4l2_device
for the reason that sub-devices generally are registered to the
v4l2_device (as well as the media device, also available through
v4l2_device).
This information is not available for sub-device drivers at probe time.
What this
Refactor the V4L2 async framework a little in preparation for async
sub-device notifiers. This avoids making some structural changes in the
patch actually implementing sub-device notifiers, making that patch easier
to review.
Signed-off-by: Sakari Ailus
Acked-by: Hans Verkuil
---
drivers/media/
Hi Sakari,
On 2017-10-27 00:10:51 +0200, Niklas Söderlund wrote:
> On 2017-10-26 10:53:27 +0300, Sakari Ailus wrote:
> > Refactor the V4L2 async framework a little in preparation for async
> > sub-device notifiers. This avoids making some structural changes in the
> > patch actually implementing s
Arnd Bergmann wrote:
> The stack consumption in this driver is still relatively high, with one
> remaining warning if the warning level is lowered to 1536 bytes:
>
> drivers/net/wireless/broadcom/brcm80211/brcmsmac/phy/phy_n.c:17135:1: error:
> the frame size of 1880 bytes is larger than 1536 b
On 2017/10/27 15:10, Hans Verkuil wrote:
On 10/27/2017 05:30 AM, Wenyou Yang wrote:
From: Songjun Wu
The ov7740 (color) image sensor is a high performance VGA CMOS
image snesor, which supports for output formats: RAW RGB and YUV
and image sizes: VGA, and QVGA, CIF and any size smaller.
Two
Add a Video4Linux2 sensor-level driver for the OmniVision OV7740
VGA camera image sensor.
Changes in v2:
- Split off the bindings into a separate patch.
- Add a new entry to the MAINTAINERS file.
Wenyou Yang (2):
media: i2c: Add the ov7740 image sensor driver
media: ov7740: Document device
Add the device tree binding documentation for ov7740 driver and
add a new entry of ov7740 to the MAINTAINERS file.
Signed-off-by: Wenyou Yang
---
Changes in v2:
- Split off the bindings into a separate patch.
- Add a new entry to the MAINTAINERS file.
.../devicetree/bindings/media/i2c/ov7740
The ov7740 (color) image sensor is a high performance VGA CMOS
image snesor, which supports for output formats: RAW RGB and YUV
and image sizes: VGA, and QVGA, CIF and any size smaller.
Signed-off-by: Songjun Wu
Signed-off-by: Wenyou Yang
---
Changes in v2: None
drivers/media/i2c/Kconfig |
Strange, this is actually an updated version for an earlier pull request that
I sent on October 17th but that never showed up in patchwork!
Odd, hopefully this will register there correctly.
Regards,
Hans
The following changes since commit 61065fc3e32002ba48aa6bc3816c1f6f9f8daf55:
Me
On 10/27/2017 05:30 AM, Wenyou Yang wrote:
> From: Songjun Wu
>
> The ov7740 (color) image sensor is a high performance VGA CMOS
> image snesor, which supports for output formats: RAW RGB and YUV
> and image sizes: VGA, and QVGA, CIF and any size smaller.
Two short remarks: please split off the
48 matches
Mail list logo
