+ cris/ia64/mn10300/openrisc maintainers
On 2017/12/25 9:09, Yisheng Xie wrote:
> hi Christophe and Greg,
>
> On 2017/12/24 16:55, christophe leroy wrote:
>>
>>
>> Le 23/12/2017 à 16:57, Guenter Roeck a écrit :
>>> On 12/23/2017 05:48 AM, Greg KH wrote:
On Sat, Dec 23, 2017 at 06:55:25PM +08
Hi Emmanuel,
>>> + int flags = 0;
>>> +
>>> + data = kmalloc(2, GFP_KERNEL);
>
> Isn't 1 byte enough ?
>
To quote from Kieran further up this thread:
>> kmalloc seems a bit of an overhead for 2 bytes (only one of which is used).
>> Can this use local stack storage?
>>
>> (Laurent, looks lik
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 Jan 3 05:00:15 CET 2018
media-tree git hash:d0c8f6ad8b381dd572576ac50b9696d4d31142bb
media_build git
Hi Tim,
Happy New Year! And pardon the delay.
On 12/28/2017 01:56 PM, Tim Harvey wrote:
Steve/Hans,
I'm trying to get interlaced capture working with the TDA1997x driver
I've been working on which is connected to an IMX6 CSI.
The particular board I'm currently testing on is an IMX6Q which has
Hi Edgar,
A few more comments.
On Tuesday, 2 January 2018 22:07:24 EET Laurent Pinchart wrote:
> On Thursday, 12 October 2017 10:54:17 EET Edgar Thier wrote:
> > Use flags the device exposes for UVC controls.
> > This allows the device to define which property flags are set.
> >
> > Since some c
On 01/02, Bryan O'Donoghue wrote:
> On 02/01/18 19:01, Stephen Boyd wrote:
> >On 12/31, Bryan O'Donoghue wrote:
> >>On 30/12/17 16:36, Mikko Perttunen wrote:
> >>>FWIW, we had this problem some years ago with the Tegra CPU clock
> >>>- then it was determined that a simpler solution was to have the
To be honest we should probably just drop this, I no longer have the
card in my machine so cannot re-test it if ever needed.
On 4 December 2017 at 12:01, Hans Verkuil wrote:
> Hi Nigel,
>
> Can you repost this as a proper patch? It doesn't apply (issues with tabs and
> whitespace: please use tabs
The ioctl change the current mode or return the current mode; they
do not tell you which modes are possible (use the lirc features
ioctl for that).
Signed-off-by: Sean Young
---
Documentation/media/uapi/rc/lirc-get-rec-mode.rst | 42 --
Documentation/media/uapi/rc/lirc-get-s
Since commit a60d64b15c20 ("media: lirc: lirc interface should not be
a raw decoder"), there is no lirc_dev module any more. On Ubuntu 16.10,
the /etc/init.d/lirc startup script attempts to load the lirc_dev module.
Since this module does not exist any more, this script fails. Add an alias
so the
Since commit 9b6192589be7 ("media: lirc: implement scancode sending"),
and commit de142c324106 ("media: lirc: implement reading scancode")
the lirc features ioctl for raw IR devices advertises two modes for
sending and receiving.
The lirc daemon now fails to detect a raw IR device, both for transm
On 02/01/18 19:01, Stephen Boyd wrote:
On 12/31, Bryan O'Donoghue wrote:
On 30/12/17 16:36, Mikko Perttunen wrote:
FWIW, we had this problem some years ago with the Tegra CPU clock
- then it was determined that a simpler solution was to have the
determine_rate callback support unsigned long rat
Hi Edgar,
Thank you for the patch.
On Thursday, 12 October 2017 10:54:17 EET Edgar Thier wrote:
> Use flags the device exposes for UVC controls.
> This allows the device to define which property flags are set.
>
> Since some cameras offer auto-adjustments for properties (e.g. auto-gain),
> the v
On 12/31, Bryan O'Donoghue wrote:
> On 30/12/17 16:36, Mikko Perttunen wrote:
> >FWIW, we had this problem some years ago with the Tegra CPU clock
> >- then it was determined that a simpler solution was to have the
> >determine_rate callback support unsigned long rates - so clock
> >drivers that ne
> Patch 0003-atomisp_gmin_platform-tweak-to-drive-axp288.patch gives a
> little confusion.
> The PMIC driver should work via ACPI OpRegion macro (and should be
> enabled in kernel configuration). That's how it supposed to work.
> The patch seems redundant.
I am fairly sure it is meant to work that
Hi Luc,
I have submitted a proposal for a talk in Graphics Dev Room, but haven’t heard
anything regarding the selection. Is there a timeline by which the
notifications will be sent so that the travel can be planned accordingly?
Has anyone else heard about the submissions?
Regards
Manasi
Hi,
Hi Jacopo,
Thank you for the patch.
On Thursday, 28 December 2017 16:01:21 EET Jacopo Mondi wrote:
> Remove soc_camera framework dependencies from tw9910 sensor driver.
> - Handle clock and gpios
> - Register async subdevice
> - Remove soc_camera specific g/s_mbus_config operations
> - Add kernel
Hi Jacopo,
Thank you for the patch.
On Thursday, 28 December 2017 16:01:19 EET Jacopo Mondi wrote:
> Remove soc_camera framework dependencies from ov772x sensor driver.
> - Handle clock and gpios
> - Register async subdevice
> - Remove soc_camera specific g/s_mbus_config operations
> - Change ima
Hi Jacopo,
Thank you for the patch.
As pointed out by the 0day bot, you should move this patch to the end of the
series to avoid breaking compilation.
On Thursday, 28 December 2017 16:01:17 EET Jacopo Mondi wrote:
> Migo-R platform uses sh_mobile_ceu camera driver, which is now being
> replaced
On Tue, 2 Jan 2018, Bart Van Assche wrote:
> On Tue, 2018-01-02 at 15:00 +0100, Julia Lawall wrote:
> > On Tue, 2 Jan 2018, Bob Peterson wrote:
> > > - Original Message -
> > > > - Original Message -
> > > >
> > > Still, the GFS2 and DLM code has a plethora of broken-up printk me
On Tue, 2018-01-02 at 15:00 +0100, Julia Lawall wrote:
> On Tue, 2 Jan 2018, Bob Peterson wrote:
> > - Original Message -
> > > - Original Message -
> > >
> > Still, the GFS2 and DLM code has a plethora of broken-up printk messages,
> > and I don't like the thought of re-combining t
ov7670 driver supports two optional properties supplied through platform
data, but currently does not support any standard video interface
property.
Add support through OF parsing for 2 generic properties (vsync and hsync
polarities) and for two custom properties already supported by platform
data
Hi Shunqian,
Thanks for the patchset.
On Fri, Dec 29, 2017 at 04:08:23PM +0800, Shunqian Zheng wrote:
> Add device tree binding documentation for the OV5695 sensor.
>
> Signed-off-by: Shunqian Zheng
> ---
> .../devicetree/bindings/media/i2c/ov5695.txt | 38
> ++
> 1
On Tue, 2 Jan 2018, Bob Peterson wrote:
> - Original Message -
> | - Original Message -
> | | Drop newline at the end of a message string when the printing function
> adds
> | | a newline.
> |
> | Hi Julia,
> |
> | NACK.
> |
> | As much as it's a pain when searching the source c
- Original Message -
| - Original Message -
| | Drop newline at the end of a message string when the printing function adds
| | a newline.
|
| Hi Julia,
|
| NACK.
|
| As much as it's a pain when searching the source code for output strings,
| this patch set goes against the accep
On Tue, 2 Jan 2018, Bob Peterson wrote:
> - Original Message -
> | Drop newline at the end of a message string when the printing function adds
> | a newline.
>
> Hi Julia,
>
> NACK.
>
> As much as it's a pain when searching the source code for output strings,
> this patch set goes agains
Hi Jacopo,
Thank you for the patch.
On Thursday, 28 December 2017 16:01:16 EET Jacopo Mondi wrote:
> Add Capture Engine Unit (CEU) node to device tree.
>
> Signed-off-by: Jacopo Mondi
> ---
> arch/arm/boot/dts/r7s72100.dtsi | 15 ---
> 1 file changed, 12 insertions(+), 3 deletions(
- Original Message -
| Drop newline at the end of a message string when the printing function adds
| a newline.
Hi Julia,
NACK.
As much as it's a pain when searching the source code for output strings,
this patch set goes against the accepted Linux coding style document. See:
https://ww
Hi Jacopo,
Thank you for the patch.
On Thursday, 28 December 2017 16:01:15 EET Jacopo Mondi wrote:
> Add driver for Renesas Capture Engine Unit (CEU).
>
> The CEU interface supports capturing 'data' (YUV422) and 'images'
> (NV[12|21|16|61]).
>
> This driver aims to replace the soc_camera-based
Hi Akinobu,
Thanks for the patchset.
On Thu, Dec 21, 2017 at 01:33:33AM +0900, Akinobu Mita wrote:
> The mt9m111 driver requires clocks property for the master clock to the
> sensor, but there is no description for that. This adds it.
>
> Cc: Rob Herring
> Cc: Sakari Ailus
> Cc: Mauro Carvalh
On Tue, Jan 02, 2018 at 02:20:46PM +0200, Sakari Ailus wrote:
> Hi Hugues,
>
> One more thing, please see below.
>
> On Wed, Dec 20, 2017 at 10:51:12AM +0100, Hugues Fruchet wrote:
> > Refine CSI-2 endpoint documentation and add bindings
> > for DVP parallel interface support.
> >
> > Signed-off
Hi Hugues,
One more thing, please see below.
On Wed, Dec 20, 2017 at 10:51:12AM +0100, Hugues Fruchet wrote:
> Refine CSI-2 endpoint documentation and add bindings
> for DVP parallel interface support.
>
> Signed-off-by: Hugues Fruchet
> ---
> .../devicetree/bindings/media/i2c/ov5640.txt
Hi Jacopo,
Thank you for the patch.
On Thursday, 28 December 2017 16:01:14 EET Jacopo Mondi wrote:
> Add renesas-ceu header file.
>
> Do not remove the existing sh_mobile_ceu.h one as long as the original
> driver does not go away.
>
> Signed-off-by: Jacopo Mondi
> ---
> include/media/drv-int
Hi Jacopo,
Thank you for the patch.
On Thursday, 28 December 2017 16:01:13 EET Jacopo Mondi wrote:
> Add bindings documentation for Renesas Capture Engine Unit (CEU).
>
> Signed-off-by: Jacopo Mondi
> ---
> .../devicetree/bindings/media/renesas,ceu.txt | 85 +++
> 1 file c
Hello,
On Tuesday, 2 January 2018 13:11:39 EET Sakari Ailus wrote:
> On Tue, Jan 02, 2018 at 11:02:37AM +0800, tian.shu@intel.com wrote:
> > From: Tianshu Qiu
> >
> > Add support for these pixel formats:
> >
> > V4L2_PIX_FMT_IPU3_SBGGR10
> > V4L2_PIX_FMT_IPU3_SGBRG10
> > V4L2_PIX_FMT_IPU3_S
The client field in driver's struct is redundant. Remove it.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/dw9714.c | 19 +--
1 file changed, 5 insertions(+), 14 deletions(-)
diff --git a/drivers/media/i2c/dw9714.c b/drivers/media/i2c/dw9714.c
index 7832210..57460da 100644
-
Call pm_runtime_idle() at the end of the driver's probe() function to
enable the device to reach low power state once probe() finishes.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/dw9714.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/i2c/dw9714.c b/drivers/media/i2c/dw
The client field in driver's struct is redundant. Remove it.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/dw9714.c | 19 +--
1 file changed, 5 insertions(+), 14 deletions(-)
diff --git a/drivers/media/i2c/dw9714.c b/drivers/media/i2c/dw9714.c
index 7832210..57460da 100644
-
Hi,
(Fixed Raj's e-mail.)
The two patches address a small bug in dw9714 driver and clean it up a
little, too.
Raj: could you let me know if they work for you? Thanks.
Sakari Ailus (2):
dw9714: Call pm_runtime_idle() at the end of probe()
dw9714: Remove client field in driver's struct
dri
Hi Tian Shu,
Thanks for the patch.
On Tue, Jan 02, 2018 at 11:02:37AM +0800, tian.shu@intel.com wrote:
> From: Tianshu Qiu
>
> Add support for these pixel formats:
>
> V4L2_PIX_FMT_IPU3_SBGGR10
> V4L2_PIX_FMT_IPU3_SGBRG10
> V4L2_PIX_FMT_IPU3_SGRBG10
> V4L2_PIX_FMT_IPU3_SRGGB10
>
> Signed-
Call pm_runtime_idle() at the end of the driver's probe() function to
enable the device to reach low power state once probe() finishes.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/dw9714.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/i2c/dw9714.c b/drivers/media/i2c/dw
Hi,
The two patches address a small bug in dw9714 driver and clean it up a
little, too.
Raj: could you let me know if they work for you? Thanks.
Sakari Ailus (2):
dw9714: Call pm_runtime_idle() at the end of probe()
dw9714: Remove client field in driver's struct
drivers/media/i2c/dw9714.c
On Tue, 2 Jan 2018, Dan Carpenter wrote:
> On Wed, Dec 20, 2017 at 11:30:01AM +0100, Julia Lawall wrote:
> >
> >
> > On Wed, 20 Dec 2017, Dan Carpenter wrote:
> >
> > > On Tue, Dec 19, 2017 at 10:59:52PM +0200, Andy Shevchenko wrote:
> > > > @@ -914,9 +904,7 @@ static int lm3554_probe(struct i2c
On Wed, Dec 20, 2017 at 11:30:01AM +0100, Julia Lawall wrote:
>
>
> On Wed, 20 Dec 2017, Dan Carpenter wrote:
>
> > On Tue, Dec 19, 2017 at 10:59:52PM +0200, Andy Shevchenko wrote:
> > > @@ -914,9 +904,7 @@ static int lm3554_probe(struct i2c_client *client)
> > > dev_err(&client->dev,
Hi Shunqian,
thank you for the patch
On Fri, Dec 29, 2017 at 04:08:22PM +0800, Shunqian Zheng wrote:
> This patch adds driver for Omnivision's ov5695 sensor,
> the driver supports following features:
> - supported resolutions
>+ 2592x1944 at 30fps
>+ 1920x1080 at 30fps
>+ 1296x972
On 01/02/2018 07:11 AM, Jasmin J. wrote:
> Hi!
>
> Maybe someone can apply:
> https://patchwork.linuxtv.org/patch/46252/
>
> BR,
>Jasmin
>
Applied, thanks!
Hans
A bugfix introduce a link failure in configurations without CONFIG_MODULES:
In file included from drivers/media/usb/dvb-usb/pctv452e.c:20:0:
drivers/media/usb/dvb-usb/pctv452e.c: In function 'pctv452e_frontend_attach':
drivers/media/dvb-frontends/stb0899_drv.h:151:36: error: weak declaration of
'
Hi Jacopo,
On Thu, Dec 28, 2017 at 3:01 PM, Jacopo Mondi wrote:
> Add Capture Engine Unit (CEU) node to device tree.
Thanks for your patch!
> Signed-off-by: Jacopo Mondi
With the issue below fixed:
Reviewed-by: Geert Uytterhoeven
> --- a/arch/arm/boot/dts/r7s72100.dtsi
> +++ b/arch/arm/boot
Hi Jacopo,
On Thu, Dec 28, 2017 at 3:01 PM, Jacopo Mondi wrote:
> Add bindings documentation for Renesas Capture Engine Unit (CEU).
Thanks for your patch!
> Signed-off-by: Jacopo Mondi
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/renesas,ceu.txt
> @@ -0,0 +1,85 @@
> +Renesa
Hello Shunqian,
On Fri, Dec 29, 2017 at 04:08:23PM +0800, Shunqian Zheng wrote:
> Add device tree binding documentation for the OV5695 sensor.
>
> Signed-off-by: Shunqian Zheng
> ---
> .../devicetree/bindings/media/i2c/ov5695.txt | 38
> ++
> 1 file changed, 38 inserti
Hi Philippe,
thanks for the comment,
On Fri, Dec 29, 2017 at 01:47:30PM +0100, Philippe Ombredanne wrote:
> Jacopo,
>
> On Thu, Dec 28, 2017 at 3:01 PM, Jacopo Mondi
> wrote:
> > Copy the soc_camera based driver in v4l2 sensor driver directory.
> > This commit just copies the original file wi
50 matches
Mail list logo
