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: Wed Nov 1 05:00:16 CET 2017
media-tree git hash:f283c01b8094da9454f4b51c997f578227c29d95
media_build
This is hopefully the uncontroversial lead-in set of changes that lay
the groundwork for solving the dax-dma vs truncate problem. The overview
of the changes is:
1/ Disable DAX when we do not have struct page entries backing dax
mappings, or otherwise allow limited DAX support for axonram and
V4L2 memory registrations are incompatible with filesystem-dax that
needs the ability to revoke dma access to a mapping at will, or
otherwise allow the kernel to wait for completion of DMA. The
filesystem-dax implementation breaks the traditional solution of
truncate of active file backed mappings
Hi
After updating my operating system I notice that my Mygica X8507 board
has stopped working the digital part.
After bisecting the kernel: git:
//git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
I find that the patch:
Hi Mauro,
On Tue, Oct 31, 2017 at 02:22:59PM -0400, Mauro Carvalho Chehab wrote:
> There is a get/put operation in order to get firmware is_available
> data there at the __v4l2_async_notifier_parse_fwnode_endpoints()
> function. However, instead of using it, the code just reads again
> without
Hi!
Sakari, I am actually playing with N9 camera, not N950. That comes
next.
And the clock error I mentioned ... seems to be
-EPROBE_DEFER. So... not an issue.
Strange thing is, that my sensors seems to have different resolution
from yours:
- entity 89: smiapp pixel_array 1-0010 (1 pad, 1
Leave the autorepeat handling up to the input layer, and move
to the new timer API.
Compile tested only.
Signed-off-by: Sean Young
---
v2:
- fixes and improvements from Dmitry Torokhov
drivers/media/pci/ttpci/av7110.h| 2 +-
drivers/media/pci/ttpci/av7110_ir.c | 56
Hi Dmitry,
On Tue, Oct 31, 2017 at 11:22:36AM -0700, Dmitry Torokhov wrote:
> Hi Sean,
>
> On Tue, Oct 31, 2017 at 05:45:58PM +, Sean Young wrote:
> > Leave the autorepeat handling up to the input layer, and move
> > to the new timer API.
> >
> > Compile tested only.
> >
> > Signed-off-by:
There is a get/put operation in order to get firmware is_available
data there at the __v4l2_async_notifier_parse_fwnode_endpoints()
function. However, instead of using it, the code just reads again
without the lock. That's probably a mistake, as a similar code on
another function use the cached
Hi Sean,
On Tue, Oct 31, 2017 at 05:45:58PM +, Sean Young wrote:
> Leave the autorepeat handling up to the input layer, and move
> to the new timer API.
>
> Compile tested only.
>
> Signed-off-by: Sean Young
> ---
> drivers/media/pci/ttpci/av7110.h| 2 +-
>
Em Tue, 31 Oct 2017 17:27:58 +
Sean Young escreveu:
> On Tue, Oct 24, 2017 at 05:40:05PM -0700, Dmitry Torokhov wrote:
> > In preparation for unconditionally passing the struct timer_list pointer to
> > all timer callbacks, switch to using the new timer_setup() and
Leave the autorepeat handling up to the input layer, and move
to the new timer API.
Compile tested only.
Signed-off-by: Sean Young
---
drivers/media/pci/ttpci/av7110.h| 2 +-
drivers/media/pci/ttpci/av7110_ir.c | 54 ++---
2 files changed, 21
On Tue, Oct 24, 2017 at 05:40:05PM -0700, Dmitry Torokhov wrote:
> In preparation for unconditionally passing the struct timer_list pointer to
> all timer callbacks, switch to using the new timer_setup() and from_timer()
> to pass the timer pointer explicitly.
>
> Also stop poking into input core
Setting both V4L2_CAP_VIDEO_CAPTURE_MPLANE and V4L2_CAP_VIDEO_OUTPUT_MPLANE
for mem2mem video nodes is obsolete since commit f0476a83d61a ("[media]
V4L: Add capability flags for memory-to-memory devices"). It was enough
time to adapt all users to the new flags, so drop the legacy caps for now
to
Setting both V4L2_CAP_VIDEO_CAPTURE_MPLANE and V4L2_CAP_VIDEO_OUTPUT_MPLANE
for mem2mem video nodes is obsolete since commit f0476a83d61a ("[media]
V4L: Add capability flags for memory-to-memory devices"). It was enough
time to adapt all users to the new flags, so drop the legacy caps for now
to
The #ifs inside the code makes confusing for reviewers and also
cause problems with smatch:
drivers/staging/media/atomisp/pci/atomisp2/atomisp_ioctl.c:2937:1:
error: directive in argument list
drivers/staging/media/atomisp/pci/atomisp2/atomisp_ioctl.c:2939:1:
error: directive in
As reported by smatch:
drivers/staging/media/atomisp/pci/atomisp2/css2400/runtime/pipeline/src/pipeline.c:607
pipeline_stage_create() warn: inconsistent indenting
drivers/staging/media/atomisp/i2c/atomisp-ov2680.c:255
ov2680_write_reg_array() warn: inconsistent indenting
On lots of places, assert/return are starting at the first
column, causing indentation issues, as complained by spatch:
drivers/staging/media/atomisp/pci/atomisp2/css2400/hive_isp_css_common/host/irq_private.h:32
irq_reg_store() warn: inconsistent indenting
Used this small script to fix such
drivers/staging/media/atomisp/pci/atomisp2/css2400/sh_css.c:5801:1: error:
directive in argument list
drivers/staging/media/atomisp/pci/atomisp2/css2400/sh_css.c:5803:1: error:
directive in argument list
drivers/staging/media/atomisp/pci/atomisp2/css2400/sh_css.c:3795
create_host_acc_pipeline()
The places at atomisp.h that use stddef.h are wrong: the
types it needs are actually defined at linux/types.h. Also,
it causes lots of smatch warnings due to the redefinition of
ofsetof() macro:
/opt/gcc-7.1.0/x86/lib/gcc/x86_64-pc-linux-gnu/7.1.0/include/stddef.h:417:9:
warning: preprocessor
Don't hide function declaration on ugly macros.
Signed-off-by: Mauro Carvalho Chehab
---
.../base/circbuf/interface/ia_css_circbuf.h| 39 +++---
.../base/circbuf/interface/ia_css_circbuf_desc.h | 15 -
The atomisp alone produces a way more warnings with smatch than all other
media drivers. That prevents me to identify what's wrong on other drivers.
Cleanup the no-brain ones, in order to reduce the list to something that
would be easier to handle.
Still, after this series, we have several
Fix a switch at input_system.c that were causing smatch warnings:
drivers/staging/media/atomisp/pci/atomisp2/css2400/hive_isp_css_common/host/input_system.c:610
rx_channel_get_state() warn: inconsistent indenting
On Sun, Oct 29, 2017 at 8:50 AM, Colin King wrote:
> From: Colin Ian King
>
> Variable index is set to zero and then set to zero again
> a few lines later in a for loop initialization. Remove the
> redundant setting of index to zero. Cleans up
Hi,
Very long I try to run ov2722 on Acer Aspire SW5-012 / Fendi2 Z3537F
Kernel 4.13.10 + atomisp from 4.14 and all your corrections for atomisp
from here
https://patchwork.linuxtv.org/project/linux-media/list/?submitter=Andy+Shevchenko=*
Since i2c_unregister_device() became NULL-aware we may remove duplicate
NULL check.
Cc: Kieran Bingham
Cc: Mauro Carvalho Chehab
Cc: linux-media@vger.kernel.org
Signed-off-by: Andy Shevchenko
---
Since i2c_unregister_device() became NULL-aware we may remove duplicate checks.
Cc: Lars-Peter Clausen
Cc: Mauro Carvalho Chehab
Cc: linux-media@vger.kernel.org
Signed-off-by: Andy Shevchenko
---
Hi Mauro,
Here's essentially what ended up being missed in the previous sensor driver
pull request (due to various oddities that happened on the way, no harm
done in the end). All are fixes.
Please pull.
The following changes since commit 1bfbb88564b17bbc2187cbce9e867628532ce1a8:
media:
From: Colin Ian King
The pointer h is already initialized to codeclist_top so the second
identical assignment is redundant and can be removed. Cleans up clang
warning:
drivers/media/pci/zoran/videocodec.c:322:21: warning: Value stored to 'h'
during its initialization
tree: git://git.ragnatech.se/linux media-tree
head: bbae615636155fa43a9b0fe0ea31c678984be864
commit: 0985dd306f727df6c0e71cd8a8eda93e8fa5206e [2807/2822] media: imx274:
V4l2 driver for Sony imx274 CMOS sensor
drivers/media/i2c/imx274.c:659 imx274_regmap_util_write_table_8() error:
From: Colin Ian King
Variable mask is being set to 0x80 and then set to this value again
in the following for-loop. Remove the extraneous first setting of mask.
Cleans up clang warning:
drivers/media/pci/pt3/pt3_i2c.c:88:2: warning: Value stored to 'mask'
is never read
Em Thu, 26 Oct 2017 12:02:55 +0300
Sakari Ailus escreveu:
> Hi Mauro,
>
> Here's the final set of sensor driver patches for 4.15.
>
> Please pull.
Hi Sakari,
Could you please rebase this series on the top of master? The first
patch started with a merge conflict, and you
drivers/media/platform/atmel/atmel-isc.c: In function 'isc_async_complete':
drivers/media/platform/atmel/atmel-isc.c:1900:28: warning: variable 'sd_entity'
set but not used [-Wunused-but-set-variable]
struct isc_subdev_entity *sd_entity;
^
Signed-off-by:
but will reject the others, not just this driver but all of them
that are currently pending in our patchwork
(https://patchwork.linuxtv.org).
I find it very surprising that you rejected 146 useful update suggestions
so easily.
Feel free to repost, but only if you organize
On Tue, Oct 31, 2017 at 09:11:42AM +0800, Wenyou Yang wrote:
> Add a Video4Linux2 sensor-level driver for the OmniVision OV7740
> VGA camera image sensor.
Oh, and please wait until the patches have been reviewed, no need to send
v5 before that.
--
Sakari Ailus
e-mail: sakari.ai...@iki.fi
Hi Wenyou,
On Tue, Oct 31, 2017 at 09:11:42AM +0800, Wenyou Yang wrote:
> Add a Video4Linux2 sensor-level driver for the OmniVision OV7740
> VGA camera image sensor.
For the next version, could you rearrange your patches a bit as follows:
1. DT bindings
2. The driver and MAINTAINERS entry
Hi!
We are pcb supplier since 2007 and we have special materials in stock.
If you are interested just email me back.
Best Regards,
Sammy Chang
Overseas Sales
Mobile: +86 13580982656
Skype: +86 13580982656
Shenzhen Plus Circuits Limited
Website: www.pluscircuits.com
Add: Building 05, Lisheng
37 matches
Mail list logo