Hi all,
How to configure the below parameters:
Color Format: YUV_422
Color Depth: 12
Pixels Per Clock: 2
In Sensor driver and device tree, how to configure these values.
In Sensor driver, we may use the macro like this MEDIA_BUS_FMT_UYVY8_1X16.
But have the doubts on this. How to specify this P
Hi Mauro,
I love your patch! Yet something to improve:
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v4.16 next-20180406]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
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 Apr 7 05:00:16 CEST 2018
media-tree git hash:17dec0a949153d9ac00760ba2f5b78cb583e995f
media_build gi
Hi Kieran,
I've finished reviewing the series. For your convenience, I've rebased it on
top of the BRU/BRS dynamic allocation patches, and pushed the result to
git://linuxtv.org/pinchartl/media.git v4l2/vsp1/tlb-optimise
(Please note it has been compile-tested only)
I have also taken t
Hi Kieran,
Thank you for the patch.
On Thursday, 8 March 2018 02:05:31 EEST Kieran Bingham wrote:
> We are now able to configure a pipeline directly into a local display
> list body. Take advantage of this fact, and create a cacheable body to
> store the configuration of the pipeline in the video
Hi Kieran,
Thank you for the patch.
On Thursday, 8 March 2018 02:05:30 EEST Kieran Bingham wrote:
> Currently the entities store their configurations into a display list.
> Adapt this such that the code can be configured into a body directly,
> allowing greater flexibility and control of the cont
Hi Kieran,
Thank you for the patch.
On Thursday, 8 March 2018 02:05:29 EEST Kieran Bingham wrote:
> The entities provide a single .configure operation which configures the
> object into the target display list, based on the vsp1_entity_params
> selection.
>
> This restricts us to a single functi
Hi Kieran,
Thank you for the patch.
On Thursday, 8 March 2018 02:05:28 EEST Kieran Bingham wrote:
> Extend the display list body with a reference count, allowing bodies to
> be kept as long as a reference is maintained. This provides the ability
> to keep a cached copy of bodies which will not ch
Hi Kieran,
Thank you for the patch.
On Thursday, 8 March 2018 02:05:27 EEST Kieran Bingham wrote:
> Adapt the dl->body0 object to use an object from the body pool. This
> greatly reduces the pressure on the TLB for IPMMU use cases, as all of
> the lists use a single allocation for the main body.
Add support for video-i2c polling driver
Changes from v1:
* Switch to SPDX tags versus GPLv2 license text
* Remove unneeded zeroing of data structures
* Add video_i2c_try_fmt_vid_cap call in video_i2c_s_fmt_vid_cap function
Changes from v2:
* Add missing linux/kthread.h include that broke x86_64
Define the device tree bindings for the panasonic,amg88xx i2c
video driver.
Cc: devicet...@vger.kernel.org
Reviewed-by: Rob Herring
Signed-off-by: Matt Ranostay
---
.../bindings/media/i2c/panasonic,amg88xx.txt | 19 +++
1 file changed, 19 insertions(+)
create mode 1006
There are several thermal sensors that only have a low-speed bus
interface but output valid video data. This patchset enables support
for the AMG88xx "Grid-Eye" sensor family.
Signed-off-by: Matt Ranostay
---
MAINTAINERS | 6 +
drivers/media/i2c/Kconfig | 13 +
drivers/m
Hi Kieran,
Thank you for the patch.
On Thursday, 8 March 2018 02:05:26 EEST Kieran Bingham wrote:
> Each display list allocates a body to store register values in a dma
> accessible buffer from a dma_alloc_wc() allocation. Each of these
> results in an entry in the TLB, and a large number of disp
Hi Mauro,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on next-20180406]
[cannot apply to v4.16]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
Hi Frédéric,
On Thu, Mar 29, 2018 at 09:53:45AM +0200, FRÉDÉRIC PARRENIN wrote:
> The second part now.
I looked at the tables and it seems the dsdt lists two sensors (imx135 and
ov2740) but the rest of the information on how they're connected etc. is
missing. There are no sensor drivers in upstr
Hi Kieran,
Thank you for the patch.
On Thursday, 8 March 2018 02:05:24 EEST Kieran Bingham wrote:
> Throughout the codebase, the term 'fragment' is used to represent a
> display list body. This term duplicates the 'body' which is already in
> use.
>
> The datasheet references these objects as a
Hi Hans,
Thanks for your work on this. A few comments below...
On Wed, Mar 28, 2018 at 03:50:05PM +0200, Hans Verkuil wrote:
> From: Hans Verkuil
>
> Implement the core of the media request processing.
>
> Drivers can bind request objects to a request. These objects
> can then be marked comple
In order to make the vsp1_du_setup_lif() easier to read, and for
symmetry with the DRM pipeline input setup, move the pipeline output
setup code to a separate function.
Signed-off-by: Laurent Pinchart
Reviewed-by: Kieran Bingham
--
Changes since v2:
- Moved vsp1_du_pipeline_setup_input() rename
The DRM pipeline setup code used at atomic commit time is similar to the
setup code used when enabling the pipeline. Move it to a separate
function in order to share it.
Signed-off-by: Laurent Pinchart
Reviewed-by: Kieran Bingham
---
Changes since v2:
- Rename vsp1_du_pipeline_setup_input() to
Hi Mauro,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.16 next-20180406]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
Hi Mauro,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.16 next-20180406]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
On Fri, Apr 06, 2018 at 03:36:03PM +0300, Oleksandr Andrushchenko wrote:
> On 04/06/2018 02:57 PM, Gerd Hoffmann wrote:
> > Hi,
> >
> >>>I fail to see any common ground for xen-zcopy and udmabuf ...
> >>Does the above mean you can assume that xen-zcopy and udmabuf
> >>can co-exist as two differen
Hi Mauro,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.16 next-20180406]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
Since the 4.16 kernel my uvcvideo webcam on Thinkpad X1 Carbon (5th
gen) stopped working with gst-launch-1.0, kamoso (kde webcam app),
Firefox and Chromium on sites like appear.in, talky.io, Google
Hangouts and meet.jit.si.
It works fine in 4.15
The camera is:
Bus 001 Device 004: ID 04f2:b5ce Chi
Em Sat, 7 Apr 2018 00:21:07 +0800
kbuild test robot escreveu:
> Hi Mauro,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on linuxtv-media/master]
> [also build test ERROR on next-20180406]
> [cannot apply to v4.16]
> [if your patch is appli
Em Fri, 06 Apr 2018 18:46:05 +0300
Laurent Pinchart escreveu:
> Hi Mauro,
>
> Thank you for the patch.
>
> On Friday, 6 April 2018 17:23:18 EEST Mauro Carvalho Chehab wrote:
> > Instead of converting to int, use %p. That prevents this
> > warning:
> > drivers/media/platform/omap3isp/ispstat
Em Fri, 06 Apr 2018 18:54:50 +0300
Laurent Pinchart escreveu:
> Hi Mauro,
>
> Thank you for the patch.
>
> On Friday, 6 April 2018 17:23:19 EEST Mauro Carvalho Chehab wrote:
> > That prevent those warnings:
> >drivers/media/platform/omap3isp/isppreview.c:893:45: warning: incorrect
> > type
Hi Mauro,
I love your patch! Yet something to improve:
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on next-20180406]
[cannot apply to v4.16]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com
Hi Mauro,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.16 next-20180406]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
Hi Laurent,
On 05/04/18 10:18, Laurent Pinchart wrote:
> Display list completion is already reported to the frame end handler,
> but that mechanism is global to all display lists. In order to implement
> BRU and BRS reassignment in DRM pipelines we will need to commit a
> display list and wait for
Hi Laurent,
Thanks for the updates
On 05/04/18 10:18, Laurent Pinchart wrote:
> In order to make the vsp1_du_setup_lif() easier to read, and for
> symmetry with the DRM pipeline input setup, move the pipeline output
> setup code to a separate function.
>
> Signed-off-by: Laurent Pinchart
> Revi
Hi Laurent,
Thanks for this enhancement.
On 05/04/18 10:18, Laurent Pinchart wrote:
> We will soon need to return more than a boolean completion status from
> the vsp1_dlm_irq_frame_end() IRQ handler. Turn the return value into a
> bitfield to prepare for that. No functional change is introduced
Hi Tomasz,
On Tue, 2018-04-03 at 10:13 +, Tomasz Figa wrote:
> Hi Philipp,
>
> On Thu, Mar 29, 2018 at 2:12 AM Philipp Zabel
> wrote:
>
> > The driver helpfully resets the capture queue format and selection
> > rectangle whenever output format is changed. This only works while
> > the captu
Hi Ian,
On Fri, 2018-04-06 at 09:40 +0100, Ian Arkver wrote:
> > - ret = coda_try_fmt_vid_cap(file, priv, &f_cap);
> > - if (ret)
> > - return ret;
> > -
> > - q_data_src = get_q_data(ctx, V4L2_BUF_TYPE_VIDEO_OUTPUT);
> > - r.left = 0;
> > - r.top = 0;
> > - r.width = q_data
Hi Mauro,
Thank you for the patch.
On Friday, 6 April 2018 17:23:19 EEST Mauro Carvalho Chehab wrote:
> That prevent those warnings:
>drivers/media/platform/omap3isp/isppreview.c:893:45: warning: incorrect
> type in initializer (different address spaces)
> drivers/media/platform/omap3isp/ispp
Hi Mauro,
Thank you for the patch.
On Friday, 6 April 2018 17:23:18 EEST Mauro Carvalho Chehab wrote:
> Instead of converting to int, use %p. That prevents this
> warning:
> drivers/media/platform/omap3isp/ispstat.c:451 isp_stat_bufs_alloc()
> warn:
> argument 7 to %08lx specifier is cast
This driver can be built successfuly on non-x86 archs, if
we remove SONY_LAPTOP dependency.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/pci/meye/Kconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/media/pci/meye/Kconfig b/drivers/media/pci/meye/Kconfi
The dependency of DRM_OMAP = n can be relaxed for just
compilation test.
This allows building the omap3isp driver with allyesconfig
on ARM.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/video/fbdev/omap2/omapfb/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drive
Hi Mauro,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.16 next-20180406]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
Em Fri, 6 Apr 2018 16:37:15 +0200
Arnd Bergmann escreveu:
> On Fri, Apr 6, 2018 at 4:26 PM, Mauro Carvalho Chehab
> wrote:
> > Em Fri, 6 Apr 2018 16:16:46 +0200
> > Arnd Bergmann escreveu:
> >
> >> On Fri, Apr 6, 2018 at 4:15 PM, Mauro Carvalho Chehab
> >> wrote:
> >> > Em Fri, 6 Apr 2018
On Fri, Apr 6, 2018 at 4:26 PM, Mauro Carvalho Chehab
wrote:
> Em Fri, 6 Apr 2018 16:16:46 +0200
> Arnd Bergmann escreveu:
>
>> On Fri, Apr 6, 2018 at 4:15 PM, Mauro Carvalho Chehab
>> wrote:
>> > Em Fri, 6 Apr 2018 11:51:16 +0200
>> > Arnd Bergmann escreveu:
>> >
>> >> On Fri, Apr 6, 2018 at 1
Em Fri, 6 Apr 2018 16:23:18 +0200
Arnd Bergmann escreveu:
> This avoids countless sparse warnings like
>
>drivers/media/platform/fsl-viu.c:1081:25: sparse: incorrect type in
> argument 2 (different address spaces)
>drivers/media/platform/fsl-viu.c:1082:25: sparse: incorrect type in
>
Em Fri, 6 Apr 2018 16:16:46 +0200
Arnd Bergmann escreveu:
> On Fri, Apr 6, 2018 at 4:15 PM, Mauro Carvalho Chehab
> wrote:
> > Em Fri, 6 Apr 2018 11:51:16 +0200
> > Arnd Bergmann escreveu:
> >
> >> On Fri, Apr 6, 2018 at 11:47 AM, Mauro Carvalho Chehab
> >> wrote:
> >>
> >> > [PATCH] media
drivers/staging/media/davinci_vpfe/dm365_ipipe.c:74:17: warning: variable 'dev'
set but not used [-Wunused-but-set-variable]
struct device *dev;
^~~
Signed-off-by: Mauro Carvalho Chehab
---
drivers/staging/media/davinci_vpfe/dm365_ipipe.c | 2 --
1 file changed, 2 deletions(-
As warned:
drivers/staging/media/davinci_vpfe/dm365_ipipe.c:1834 vpfe_ipipe_init()
error: we previously assumed 'res' could be null (see line 1797)
There's something wrong at vpfe_ipipe_init():
1) it caches the resourse_size() from from the first region
and reuses to the second region
Fix those two warnings:
drivers/staging/media/davinci_vpfe/vpfe_mc_capture.c:90: warning: Function
parameter or member 'interface' not described in 'MODULE_PARM_DESC'
drivers/staging/media/davinci_vpfe/vpfe_mc_capture.c:90: warning: Function
parameter or member '(default' not described in '
The dm365_ipipe_hw.c and dm365_ipipe.c file check if several table
pointers, declared at davinci_vpfe_user.h, are filled before using
them.
The problem is that those pointers come from struct declarations
like:
struct vpfe_ipipe_yee {
...
short table[VPFE_IPIPE_MAX_SIZE_YE
Not sure what was the original idea here, but the implementation
went into a different way, and the fmt var is not used
anymore, as warned:
drivers/staging/media/davinci_vpfe/dm365_isif.c: In function
'__isif_get_format':
drivers/staging/media/davinci_vpfe/dm365_isif.c:1401:29: warning: variable
as warned:
drivers/staging/media/davinci_vpfe/vpfe_video.c: In function 'vpfe_streamon':
drivers/staging/media/davinci_vpfe/vpfe_video.c:1471:31: warning: variable
'sdinfo' set but not used [-Wunused-but-set-variable]
struct vpfe_ext_subdev_info *sdinfo;
^~~
resizer_set_defualt_configuration -> resizer_set_default_configuration
Signed-off-by: Mauro Carvalho Chehab
---
drivers/staging/media/davinci_vpfe/dm365_resizer.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/media/davinci_vpfe/dm365_resizer.c
b/drivers
Reduce one ident level inside those functions and use BIT()
macro.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/staging/media/davinci_vpfe/dm365_ipipe.c | 98
1 file changed, 50 insertions(+), 48 deletions(-)
diff --git a/drivers/staging/media/davinci_vpfe/dm365_ipi
if v4l2_subdev_call(..., VENC_GET_FLD,...) fails, it
currently returns a random value. Instead, return 1.
That's probably better than returning 0, as this is very
likely what happens in practice with the current code, as
as the probably of an unititialized 32 bits integer to
have an specific value
The annotations there are wrong as warned:
drivers/media/radio/si470x/radio-si470x-i2c.c:107:35: warning: cast to
restricted __be16
drivers/media/radio/si470x/radio-si470x-i2c.c:107:35: warning: cast to
restricted __be16
drivers/media/radio/si470x/radio-si470x-i2c.c:107:35: warning: cast
Solve those warnings:
drivers/media/platform/fsl-viu.c:299 restart_video_queue() warn: argument 3
to %08lx specifier is cast from pointer
drivers/media/platform/fsl-viu.c:506 buffer_queue() warn: argument 2 to
%08lx specifier is cast from pointer
drivers/media/platform/fsl-viu.c:518
That prevent those warnings:
drivers/media/platform/omap3isp/isppreview.c:893:45: warning: incorrect type
in initializer (different address spaces)
drivers/media/platform/omap3isp/isppreview.c:893:45:expected void
[noderef] *from
drivers/media/platform/omap3isp/isppreview.c:893:45:
This avoids countless sparse warnings like
drivers/media/platform/fsl-viu.c:1081:25: sparse: incorrect type in argument
2 (different address spaces)
drivers/media/platform/fsl-viu.c:1082:25: sparse: incorrect type in argument
2 (different address spaces)
Signed-off-by: Arnd Bergmann
---
Both sparse and gcc (with 'make V=1') warn about non-static symbols that
have not been declared:
drivers/media/platform/fsl-viu.c:235:16: warning: symbol 'format_by_fourcc' was
not declared. Should it be static?
drivers/media/platform/fsl-viu.c:248:6: warning: symbol 'viu_start_dma' was not
decl
There are several usages of an __iomem memory that aren't
marked as such, causing those warnings:
drivers/staging/media/davinci_vpfe/dm365_ipipeif.c:76:26: warning: incorrect
type in argument 2 (different address spaces)
drivers/staging/media/davinci_vpfe/dm365_ipipeif.c:76:26:expected void
The __user annotations on this driver are wrong, causing lots
of warnings:
drivers/staging/media/davinci_vpfe/dm365_ipipe.c:1269:22: warning:
incorrect type in assignment (different address spaces)
drivers/staging/media/davinci_vpfe/dm365_ipipe.c:1269:22:expected void
[noderef] *from
After applying this patch series:
https://www.mail-archive.com/linux-media@vger.kernel.org/msg128829.html
Which allows to build all drivers with COMPILE_TEST on x86, my scripts
can finally check for errors/warnings on those drivers.
This patch series correct those warnings.
Mauro Carvalho C
Solve those warnings:
drivers/media/platform/davinci/vpbe_display.c:288 vpbe_start_streaming()
warn: inconsistent indenting
drivers/media/platform/davinci/vpbe_display.c:1356 register_device() warn:
argument 3 to %x specifier is cast from pointer
drivers/media/platform/davinci/vpbe_d
Instead of converting to int, use %p. That prevents this
warning:
drivers/media/platform/omap3isp/ispstat.c:451 isp_stat_bufs_alloc()
warn: argument 7 to %08lx specifier is cast from pointer
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/platform/omap3isp/ispstat.c | 4 ++--
1 f
As warned:
drivers/media/platform/omap/omap_vout.c:711 omap_vout_buffer_setup()
warn: inconsistent indenting
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/platform/omap/omap_vout.c | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/drivers/media
Solve those warnings:
drivers/media/platform/marvell-ccic/mmp-driver.c:135:41: warning: incorrect
type in argument 2 (different address spaces)
drivers/media/platform/marvell-ccic/mmp-driver.c:135:41:expected void
[noderef] *
drivers/media/platform/marvell-ccic/mmp-driver.c:135:4
On all places, we do:
void *foo;
Here, it is doing, instead:
void * foo;
That tricks static analyzers, making it see errors where
there's none. So, just reorder in order to cleanup those
warnings:
drivers/media/platform/davinci/isif.c:1066:22: warning: incorrect type in
as
drivers/media/platform/davinci/vpbe_osd.c:849 try_layer_config() warn:
inconsistent indenting
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/platform/davinci/vpbe_osd.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/media/platform/davinci/vpbe_osd.c
b/
Those annotations are wrong, causing this warning:
drivers/media/platform/fsl-viu.c:1440:21: warning: incorrect type in
assignment (different address spaces)
drivers/media/platform/fsl-viu.c:1440:21:expected struct viu_reg *vr
drivers/media/platform/fsl-viu.c:1440:21:got struc
On Fri, Apr 6, 2018 at 4:15 PM, Mauro Carvalho Chehab
wrote:
> Em Fri, 6 Apr 2018 11:51:16 +0200
> Arnd Bergmann escreveu:
>
>> On Fri, Apr 6, 2018 at 11:47 AM, Mauro Carvalho Chehab
>> wrote:
>>
>> > [PATCH] media: fsl-viu: allow building it with COMPILE_TEST
>> >
>> > There aren't many things
Em Fri, 6 Apr 2018 11:51:16 +0200
Arnd Bergmann escreveu:
> On Fri, Apr 6, 2018 at 11:47 AM, Mauro Carvalho Chehab
> wrote:
>
> > [PATCH] media: fsl-viu: allow building it with COMPILE_TEST
> >
> > There aren't many things that would be needed to allow it
> > to build with compile test.
> >
> >
Hi Mauro,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.16 next-20180406]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
Hi Mauro,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.16 next-20180406]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
On 04/06/2018 02:57 PM, Gerd Hoffmann wrote:
Hi,
I fail to see any common ground for xen-zcopy and udmabuf ...
Does the above mean you can assume that xen-zcopy and udmabuf
can co-exist as two different solutions?
Well, udmabuf route isn't fully clear yet, but yes.
See also gvt (intel vgp
Am 06.04.2018 um 11:33 schrieb Gerd Hoffmann:
Hi,
The pages backing a DMA-buf are not allowed to move (at least not without a
patch set I'm currently working on), but for certain MM operations to work
correctly you must be able to modify the page tables entries and move the
pages backing the
Hi Mauro,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.16 next-20180406]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
Hi,
> > I fail to see any common ground for xen-zcopy and udmabuf ...
> Does the above mean you can assume that xen-zcopy and udmabuf
> can co-exist as two different solutions?
Well, udmabuf route isn't fully clear yet, but yes.
See also gvt (intel vgpu), where the hypervisor interface is abs
Hi Mauro,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.16 next-20180406]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
On 04/06/2018 12:07 PM, Gerd Hoffmann wrote:
I'm not sure we can create something which works on both kvm and xen.
The memory management model is quite different ...
On xen the hypervisor manages all memory. Guests can allow other guests
to access specific pages (using grant tables). In theor
On Fri, Apr 06, 2018 at 10:52:21AM +0100, Daniel Stone wrote:
> Hi Gerd,
>
> On 14 March 2018 at 08:03, Gerd Hoffmann wrote:
> >> Either mlock account (because it's mlocked defacto), and get_user_pages
> >> won't do that for you.
> >>
> >> Or you write the full-blown userptr implementation, inclu
Hi Mauro,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.16 next-20180406]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
Hi Gerd,
On 14 March 2018 at 08:03, Gerd Hoffmann wrote:
>> Either mlock account (because it's mlocked defacto), and get_user_pages
>> won't do that for you.
>>
>> Or you write the full-blown userptr implementation, including mmu_notifier
>> support (see i915 or amdgpu), but that also requires Ch
On Fri, Apr 6, 2018 at 11:47 AM, Mauro Carvalho Chehab
wrote:
> [PATCH] media: fsl-viu: allow building it with COMPILE_TEST
>
> There aren't many things that would be needed to allow it
> to build with compile test.
>
> Add the needed bits.
>
> Signed-off-by: Mauro Carvalho Chehab
Reviewed-by:
Em Thu, 5 Apr 2018 23:35:06 +0200
Arnd Bergmann escreveu:
> On Thu, Apr 5, 2018 at 7:54 PM, Mauro Carvalho Chehab
> wrote:
> > There aren't many things that would be needed to allow it
> > to build with compile test.
>
> > +/* Allow building this driver with COMPILE_TEST */
> > +#ifndef CONFI
On 04/06/2018 12:07 PM, Gerd Hoffmann wrote:
Hi,
* The general interface should be able to express sharing from any
guest:guest, not just guest:host. Arbitrary G:G sharing might be
something some hypervisors simply aren't able to support, but the
userspace API itself shoul
Hi,
> The pages backing a DMA-buf are not allowed to move (at least not without a
> patch set I'm currently working on), but for certain MM operations to work
> correctly you must be able to modify the page tables entries and move the
> pages backing them around.
>
> For example try to use fork
Hi,
> > * The general interface should be able to express sharing from any
> > guest:guest, not just guest:host. Arbitrary G:G sharing might be
> > something some hypervisors simply aren't able to support, but the
> > userspace API itself shouldn't make assumptions or restrict tha
On 05/04/18 23:29, Mauro Carvalho Chehab wrote:
> This driver builds cleanly with COMPILE_TEST, and it is
> needed in order to allow building drivers/media omap2
> driver.
>
> So, change the logic there to allow building it.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
> drivers/video/fbdev/o
On 28/03/18 18:12, Philipp Zabel wrote:
The driver helpfully resets the capture queue format and selection
rectangle whenever output format is changed. This only works while
the capture queue is not busy.
Signed-off-by: Philipp Zabel
---
drivers/media/platform/coda/coda-common.c | 28
87 matches
Mail list logo