From: Rob Clark
For devices which have constraints about maximum number of segments in
an sglist. For example, a device which could only deal with contiguous
buffers would set max_segment_count to 1.
The initial motivation is for devices sharing buffers via dma-buf,
to allow the buffer exporter
Add some helpers to share the constraints of devices while attaching
to the dmabuf buffer.
At each attach, the constraints are calculated based on the following:
- dma_mask, coherent_dma_mask from struct device,
- max_segment_size, max_segment_count, segment_boundary_mask from
device_dma_parame
Hello Everyone,
Based on review comments received, I've split my earlier patchset on
'dma-buf constraints-enabled allocation' [1] into 2 sets:
- first one is this one, to use dma_parms and related parameters from
struct device to share constraints, and then to use these constraints in
dma-bu
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 21 04:00:16 CET 2015
git branch: test
git hash: 99f3cd52aee21091ce62442285a68873e3be833f
gcc versio
Hi.
On Mon, 2015-01-19 at 17:25 +0900, Daniel Jeong wrote:
This patch adds the driver for the single string flash products of TI.
Several single string flash controllers of TI have similar register map
and bit data. This driver supports four products,lm3556, lm3561, lm3642
and lm3648.
Why not t
Hi Mauro,
The following changes since commit ec6f34e5b552fb0a52e6aae1a5afbbb1605cc6cc:
Linux 3.19-rc5 (2015-01-18 18:02:20 +1200)
are available in the git repository at:
git://linuxtv.org/gliakhovetski/v4l-dvb.git 3.19-rc5-fixes
for you to fetch changes up to 52e83770291eb575fec552396a63e9
Hello,
I'm running Linux 3.18.2. I have a "generic" Easycap device that I
would like to use, however it appears that my particular revision of
this device is not supported. The VID/PID of the device is 05e1:0408,
in fact the whole USB descriptor is the same as the "reference" one
available on the L
Hi,
Thanks for the patch.
On Wed, Jan 14, 2015 at 9:46 PM, Aya Mahfouz
wrote:
> This patch fixes the following checkpatch.pl warning:
>
> space prohibited before semicolon
>
> Signed-off-by: Aya Mahfouz
Acked-by: Lad, Prabhakar
Regards,
--Prabhakar Lad
> ---
> v1: This patch applies to Greg
Hi,
On Wed, Jan 21, 2015 at 4:52 AM, Ahmad Hassan wrote:
> This patch fixes the following checkpatch.pl error:
> fix space prohibited before that ',' at line 904
Thanks for the patch, but there already exists a patch [1] fixing this.
[1] https://patchwork.linuxtv.org/patch/27912/
Thanks,
--Pra
This patch fixes the following checkpatch.pl error:
fix space prohibited before that ',' at line 904
Signed-off-by: Ahmad Hassan
---
drivers/staging/media/davinci_vpfe/dm365_ipipe.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/media/davinci_vpfe/dm365_ipipe.
On Tue 2015-01-20 11:29:16, Rob Herring wrote:
> On Tue, Jan 20, 2015 at 10:09 AM, Jacek Anaszewski
> wrote:
> > On 01/16/2015 04:52 PM, Jacek Anaszewski wrote:
> >>
> >> On 01/16/2015 02:48 PM, Rob Herring wrote:
>
> [...]
>
> >>> You may want to add something like led-output-cnt or led-driver-
On Tue, Jan 20, 2015 at 10:09 AM, Jacek Anaszewski
wrote:
> On 01/16/2015 04:52 PM, Jacek Anaszewski wrote:
>>
>> On 01/16/2015 02:48 PM, Rob Herring wrote:
[...]
>>> You may want to add something like led-output-cnt or led-driver-cnt in
>>> the parent so you know the max list size.
>>
>>
>> Why
On Tue, 20 Jan 2015, Pavel Machek wrote:
> On Tue 2015-01-20 15:40:29, Lee Jones wrote:
> > On Tue, 20 Jan 2015, Jacek Anaszewski wrote:
> >
> > > On 01/20/2015 02:01 PM, Jacek Anaszewski wrote:
> > > >On 01/20/2015 12:17 PM, Lee Jones wrote:
> > > >>On Fri, 09 Jan 2015, Jacek Anaszewski wrote:
>
On 01/16/2015 04:52 PM, Jacek Anaszewski wrote:
On 01/16/2015 02:48 PM, Rob Herring wrote:
On Fri, Jan 16, 2015 at 3:07 AM, Jacek Anaszewski
wrote:
On 01/15/2015 03:24 PM, Rob Herring wrote:
On Tue, Jan 13, 2015 at 2:42 AM, Jacek Anaszewski
wrote:
On 01/12/2015 05:55 PM, Rob Herring wrote
On Tue 2015-01-20 15:40:29, Lee Jones wrote:
> On Tue, 20 Jan 2015, Jacek Anaszewski wrote:
>
> > On 01/20/2015 02:01 PM, Jacek Anaszewski wrote:
> > >On 01/20/2015 12:17 PM, Lee Jones wrote:
> > >>On Fri, 09 Jan 2015, Jacek Anaszewski wrote:
> > >>
> > >>>Modify FLASH_EN_SHIFT and TORCH_EN_SHIFT
On Tue, 20 Jan 2015, Jacek Anaszewski wrote:
> On 01/20/2015 12:13 PM, Lee Jones wrote:
> >On Fri, 09 Jan 2015, Jacek Anaszewski wrote:
> >
> >>Change flash cell identifiers from max77693-flash to max77693-led
> >>to avoid confusion with NOR/NAND Flash.
> >
> >This is okay by me, but aren't these
On Tue, 20 Jan 2015, Jacek Anaszewski wrote:
> On 01/20/2015 02:01 PM, Jacek Anaszewski wrote:
> >On 01/20/2015 12:17 PM, Lee Jones wrote:
> >>On Fri, 09 Jan 2015, Jacek Anaszewski wrote:
> >>
> >>>Modify FLASH_EN_SHIFT and TORCH_EN_SHIFT macros to work properly
> >>>when passed enum max77693_fled
On Tue, 20 Jan 2015, Jacek Anaszewski wrote:
> On 01/20/2015 12:21 PM, Lee Jones wrote:
> >On Fri, 09 Jan 2015, Jacek Anaszewski wrote:
> >
> >>This patch adds device tree binding documentation for
> >>the flash cell of the Maxim max77693 multifunctional device.
> >>
> >>Signed-off-by: Jacek Anasz
Re-add Ismael Luceno as co-maintainer (with personal email address).
Signed-off-by: Ismael Luceno
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index ddb9ac8..b012411 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8892,6 +8892,7 @@ SOFTLOGIC 6x10 M
On 01/20/2015 12:21 PM, Lee Jones wrote:
On Fri, 09 Jan 2015, Jacek Anaszewski wrote:
This patch adds device tree binding documentation for
the flash cell of the Maxim max77693 multifunctional device.
Signed-off-by: Jacek Anaszewski
Signed-off-by: Andrzej Hajda
Acked-by: Kyungmin Park
Cc: L
On 01/20/2015 02:01 PM, Jacek Anaszewski wrote:
On 01/20/2015 12:17 PM, Lee Jones wrote:
On Fri, 09 Jan 2015, Jacek Anaszewski wrote:
Modify FLASH_EN_SHIFT and TORCH_EN_SHIFT macros to work properly
when passed enum max77693_fled values (0 for FLED1 and 1 for FLED2)
from leds-max77693 driver.
Hi Hans,
On Tuesday 20 January 2015 14:03:00 Hans Verkuil wrote:
> On 01/20/15 13:59, Laurent Pinchart wrote:
> > On Tuesday 20 January 2015 10:30:07 Hans Verkuil wrote:
> >> On 01/20/15 10:24, Florian Echtler wrote:
> >>> On 19.01.2015 11:38, Hans Verkuil wrote:
> Sorry for the delay.
> >>>
On 01/20/15 13:59, Laurent Pinchart wrote:
> Hello,
>
> On Tuesday 20 January 2015 10:30:07 Hans Verkuil wrote:
>> On 01/20/15 10:24, Florian Echtler wrote:
>>> On 19.01.2015 11:38, Hans Verkuil wrote:
Sorry for the delay.
>>>
>>> No problem, thanks for your feedback.
>>>
> Note: I'm inte
On 01/20/2015 12:17 PM, Lee Jones wrote:
On Fri, 09 Jan 2015, Jacek Anaszewski wrote:
Modify FLASH_EN_SHIFT and TORCH_EN_SHIFT macros to work properly
when passed enum max77693_fled values (0 for FLED1 and 1 for FLED2)
from leds-max77693 driver.
Off-by-one ay? Wasn't the original code tested
Hello,
On Tuesday 20 January 2015 10:30:07 Hans Verkuil wrote:
> On 01/20/15 10:24, Florian Echtler wrote:
> > On 19.01.2015 11:38, Hans Verkuil wrote:
> >> Sorry for the delay.
> >
> > No problem, thanks for your feedback.
> >
> >>> Note: I'm intentionally using dma-contig instead of vmalloc, a
On 01/20/2015 12:13 PM, Lee Jones wrote:
On Fri, 09 Jan 2015, Jacek Anaszewski wrote:
Change flash cell identifiers from max77693-flash to max77693-led
to avoid confusion with NOR/NAND Flash.
This is okay by me, but aren't these ABI yet?
No, the led driver using it hasn't been merged yet.
On 01/20/2015 12:12 PM, Lee Jones wrote:
On Fri, 09 Jan 2015, Jacek Anaszewski wrote:
Add macros for max77693 led part related binding.
Signed-off-by: Jacek Anaszewski
Acked-by: Kyungmin Park
Cc: Lee Jones
Cc: Chanwoo Choi
---
include/dt-bindings/mfd/max77693.h | 21 +++
On Mon, 19 Jan 2015, Guennadi Liakhovetski wrote:
On Mon, 19 Jan 2015, William Towle wrote:
in the patchset Ben linked to above we think
we have the appropriate loops: a for loop for queue_buf[], and
list_for_each_safe() for anything left in priv->capture; this is
consistent with rcar_vin_fi
On Fri, 09 Jan 2015, Jacek Anaszewski wrote:
> This patch adds device tree binding documentation for
> the flash cell of the Maxim max77693 multifunctional device.
>
> Signed-off-by: Jacek Anaszewski
> Signed-off-by: Andrzej Hajda
> Acked-by: Kyungmin Park
> Cc: Lee Jones
> Cc: Chanwoo Choi
On Fri, 09 Jan 2015, Jacek Anaszewski wrote:
> Modify FLASH_EN_SHIFT and TORCH_EN_SHIFT macros to work properly
> when passed enum max77693_fled values (0 for FLED1 and 1 for FLED2)
> from leds-max77693 driver.
Off-by-one ay? Wasn't the original code tested?
> Signed-off-by: Jacek Anaszewski
>
On Fri, 09 Jan 2015, Jacek Anaszewski wrote:
> 1. Rename max77693_led_platform_data to max77693_led_config_data to
>avoid making impression that the led driver expects a board file -
>it relies on Device Tree data.
> 2. Remove fleds array, as the DT binding design has changed
> 3. Add "lab
On Fri, 09 Jan 2015, Jacek Anaszewski wrote:
> Change flash cell identifiers from max77693-flash to max77693-led
> to avoid confusion with NOR/NAND Flash.
This is okay by me, but aren't these ABI yet?
> Signed-off-by: Jacek Anaszewski
> Acked-by: Kyungmin Park
> Cc: Chanwoo Choi
> Cc: Lee Jon
On Fri, 09 Jan 2015, Jacek Anaszewski wrote:
> Add macros for max77693 led part related binding.
>
> Signed-off-by: Jacek Anaszewski
> Acked-by: Kyungmin Park
> Cc: Lee Jones
> Cc: Chanwoo Choi
> ---
> include/dt-bindings/mfd/max77693.h | 21 +
> 1 file changed, 21 inse
On Mon, Jan 19, 2015 at 01:45:44PM +0100, Hans Verkuil wrote:
> On 01/19/2015 01:32 PM, Vincent McIntyre wrote:
> > Hi
> >
> > I am seeing build failures since 11 January.
> > A build I did on 22 December worked fine.
> > My build procedure and the error are shown below.
>
> I've just updated med
Hi Hans,
On Mon, Jan 19, 2015 at 5:45 PM, Hans Verkuil wrote:
> On 01/19/2015 04:13 AM, Hao Liang wrote:
>> Hi Hans,
>>
>> Thank you for your reply.
>> This change comes largely from a non-blackfin architecture dsp processor of
>> ADI want to reuse this driver.
>> And i have tested common read/w
Hi Guennadi,
On Mon, Jan 19, 2015 at 11:19 PM, Guennadi Liakhovetski
wrote:
> The V4L2 API requires both .capabilities and .device_caps fields of
> struct v4l2_capability to be set. Otherwise the compliance checker
> complains and since commit "v4l2-ioctl: WARN_ON if querycap didn't fill
> device
On 01/20/15 10:24, Florian Echtler wrote:
> Hello Hans,
>
> On 19.01.2015 11:38, Hans Verkuil wrote:
>> Sorry for the delay.
> No problem, thanks for your feedback.
>
>>> Note: I'm intentionally using dma-contig instead of vmalloc, as the USB
>>> core apparently _will_ try to use DMA for larger b
Hello Hans,
On 19.01.2015 11:38, Hans Verkuil wrote:
> Sorry for the delay.
No problem, thanks for your feedback.
>> Note: I'm intentionally using dma-contig instead of vmalloc, as the USB
>> core apparently _will_ try to use DMA for larger bulk transfers.
> As far as I can tell from looking thr
Tested again, works now.
Thanks!
Op 20-01-15 om 08:35 schreef Hans Verkuil:
On 01/19/2015 08:06 PM, Tycho Lürsen wrote:
Hi Hans,
tested this update in media_build against a Debian 3.16 kernel.
It still tries to build SMIAPP. So sadly it still gives the same error.
Try again. I missed a duplica
39 matches
Mail list logo
