Add V4L2 definition for HEVC compressed format
Signed-off-by: Smitha T Murthy
Reviewed-by: Andrzej Hajda
---
include/uapi/linux/videodev2.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/uapi/linux/videodev2.h b/include/uapi/linux/videodev2.h
index 316be62..03d4765 100644
--- a/inc
Add support for codec definition and corresponding buffer
requirements for VP9 decoder.
Signed-off-by: Smitha T Murthy
Reviewed-by: Andrzej Hajda
---
drivers/media/platform/s5p-mfc/regs-mfc-v10.h | 6 ++
drivers/media/platform/s5p-mfc/s5p_mfc_cmd_v6.c | 3 +++
drivers/media/platform/s5p
Add V4L2 definition for HEVC compressed format which is also
known as H.265.
Signed-off-by: Smitha T Murthy
Reviewed-by: Andrzej Hajda
---
Documentation/media/uapi/v4l/pixfmt-013.rst | 5 +
1 file changed, 5 insertions(+)
diff --git a/Documentation/media/uapi/v4l/pixfmt-013.rst
b/Document
Added V4l2 controls for HEVC encoder
Signed-off-by: Smitha T Murthy
---
Documentation/media/uapi/v4l/extended-controls.rst | 391 +
1 file changed, 391 insertions(+)
diff --git a/Documentation/media/uapi/v4l/extended-controls.rst
b/Documentation/media/uapi/v4l/extended-cont
Add v4l2 controls for HEVC encoder
Signed-off-by: Smitha T Murthy
Reviewed-by: Andrzej Hajda
---
drivers/media/v4l2-core/v4l2-ctrls.c | 104 +++
include/uapi/linux/v4l2-controls.h | 132 +++
2 files changed, 236 insertions(+)
diff --git
Add HEVC encoder support and necessary registers, V4L2 CIDs,
and hevc encoder parameters
Signed-off-by: Smitha T Murthy
---
drivers/media/platform/s5p-mfc/regs-mfc-v10.h | 28 +-
drivers/media/platform/s5p-mfc/s5p_mfc.c| 1 +
drivers/media/platform/s5p-mfc/s5p_mfc_cmd_v6.c | 3 +
Aligning the luma_dpb_size, chroma_dpb_size, mv_size and me_buffer_size
for MFCv10.10.
Signed-off-by: Smitha T Murthy
Reviewed-by: Andrzej Hajda
---
drivers/media/platform/s5p-mfc/regs-mfc-v10.h | 19 +
drivers/media/platform/s5p-mfc/s5p_mfc_opr_v6.c | 95 +++--
driver
HEVC is a video coding format
Signed-off-by: Smitha T Murthy
---
drivers/media/v4l2-core/v4l2-ioctl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/v4l2-core/v4l2-ioctl.c
b/drivers/media/v4l2-core/v4l2-ioctl.c
index 0c3f238..529d1f8 100644
--- a/drivers/media/v4l2-core/v4l2-
Add support for codec definition and corresponding buffer
requirements for HEVC decoder.
Signed-off-by: Smitha T Murthy
Reviewed-by: Andrzej Hajda
---
drivers/media/platform/s5p-mfc/regs-mfc-v10.h | 1 +
drivers/media/platform/s5p-mfc/s5p_mfc_cmd_v6.c | 3 +++
drivers/media/platform/s5p-mfc
After MFC v8.0, mfc f/w lets the driver know how much scratch buffer
size is required for decoder. If mfc f/w has the functionality,
E_MIN_SCRATCH_BUFFER_SIZE, driver can know how much scratch buffer size
is required for encoder too.
Signed-off-by: Smitha T Murthy
Reviewed-by: Andrzej Hajda
---
Adding the support for MFC v10.10, with new register file and
necessary hw control, decoder, encoder and structural changes.
CC: Rob Herring
CC: devicet...@vger.kernel.org
Signed-off-by: Smitha T Murthy
Reviewed-by: Andrzej Hajda
Acked-by: Rob Herring
---
.../devicetree/bindings/media/s5p-mfc
This patch series adds MFC v10.10 support. MFC v10.10 is used in some
of Exynos7 variants.
This adds support for following:
* Add support for HEVC encoder and decoder
* Add support for VP9 decoder
* Update Documentation for control id definitions
* Update computation of min scratch buffer size re
This patch renames macro IS_MFCV8 to IS_MFCV8_PLUS so that the MFCv8
code can be resued for MFCv10.10 support. Since the MFCv8 specific code
holds good for MFC v10.10 also.
Signed-off-by: Smitha T Murthy
Acked-by: Andrzej Hajda
---
drivers/media/platform/s5p-mfc/s5p_mfc_common.h | 2 +-
driver
Hi Shuah,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.11-rc5]
[cannot apply to next-20170405]
[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/commits/Shuah-Khan/arm-dma-fix
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: Thu Apr 6 05:00:16 CEST 2017
media-tree git hash:2f65ec0567f77b75f459c98426053a3787af356a
media_build gi
On Wed, Apr 05, 2017 at 10:02:42AM -0600, Shuah Khan wrote:
> When coherent DMA memory without struct page is shared, importer
> fails to find the page and runs into kernel page fault when it
> tries to dmabuf_ops_attach/map_sg/map_page the invalid page found
> in the sg_table. Please see www.spini
Hi Gustavo,
On Wed, Apr 05, 2017 at 05:24:57PM +0200, Gustavo Padovan wrote:
> Hi Sakari,
>
> 2017-04-04 Sakari Ailus :
>
> > Hi Gustavo,
> >
> > Thank you for the patchset. Please see my comments below.
> >
> > On Mon, Mar 13, 2017 at 04:20:25PM -0300, Gustavo Padovan wrote:
> > > From: Gusta
Changeset 1f862a68df24 ("[media] dvb_frontend: move kref to struct
dvb_frontend") added a kref to the struct dvb_frontend, but it
didn't document it.
Fixes: 1f862a68df24 ("[media] dvb_frontend: move kref to struct dvb_frontend")
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/dvb-core/dv
Changeset 446aba663b82 ("[media] tveeprom: get rid of unused arg
on tveeprom_hauppauge_analog()") removed the now unused I2C adapter
struct from struct tveeprom. Remove the corresponding kernel-doc
tag.
Fixes: 446aba663b82 ("[media] tveeprom: get rid of unused arg on
tveeprom_hauppauge_analog()")
On Wed 2017-04-05 13:58:39, Lucas Stach wrote:
> Am Mittwoch, den 05.04.2017, 13:18 +0200 schrieb Pavel Machek:
> > Hi!
> >
> > > + * video stream multiplexer controlled via gpio or syscon
> > > + *
> > > + * Copyright (C) 2013 Pengutronix, Sascha Hauer
> > > + * Copyright (C) 2016 Pengutronix, P
Hi Sean,
Em Sat, 25 Mar 2017 21:31:46 +
Sean Young escreveu:
> Hi Mauro,
>
> This pull promotes lirc_sir out of staging and removes lirc_sasem;
Applied, thanks!
> this
> only leaves lirc_zilog in staging. I'm attempting to write a new driver for
> this,
> maybe we should keep lirc_zil
Em Wed, 5 Apr 2017 13:02:52 -0400
Devin Heitmueller escreveu:
> > I remember I looked on this when I wrote the driver, but I was
> > unable to find a way for em28xx to parse (or forward) such
> > data packets.
>
> I'm pretty sure it's possible, but I haven't looked at the datasheets
> in a num
Hello Gustavo,
On 04/05/2017 11:09 AM, Gustavo Padovan wrote:
> 2017-04-03 Javier Martinez Canillas :
>
>> Hello Mauro and Gustavo,
>>
>> On 04/03/2017 07:16 AM, Mauro Carvalho Chehab wrote:
>>> Hi Gustavo,
>>>
>>> Em Mon, 13 Mar 2017 16:20:25 -0300
>>> Gustavo Padovan escreveu:
>>>
From: G
When the kernel is running in secure boot mode, we lock down the kernel to
prevent userspace from modifying the running kernel image. Whilst this
includes prohibiting access to things like /dev/mem, it must also prevent
access by means of configuring driver modules in such a way as to cause a
devi
>> For what it's worth, I doubt most of the em28xx designs have the
>> tvp5150 interrupt request line connected in any way.
>
> True. But, on embedded hardware, such line may be connected into the
> SoC. Actually, from the IGEPv3 expansion diagram:
>
>
> https://www.isee.biz/support/downlo
When the kernel is running in secure boot mode, we lock down the kernel to
prevent userspace from modifying the running kernel image. Whilst this
includes prohibiting access to things like /dev/mem, it must also prevent
access by means of configuring driver modules in such a way as to cause a
devi
Em Wed, 5 Apr 2017 11:39:06 -0400
Devin Heitmueller escreveu:
> > Currently, the driver doesn't support (2), because, at the time
> > I wrote the driver, I didn't find a way to read the interrupts generated
> > by tvp5150 at em28xx[1], due to the lack of em28xx documentation,
> > but adding suppo
When coherent DMA memory without struct page is shared, importer
fails to find the page and runs into kernel page fault when it
tries to dmabuf_ops_attach/map_sg/map_page the invalid page found
in the sg_table. Please see www.spinics.net/lists/stable/msg164204.html
for more information on this prob
> Currently, the driver doesn't support (2), because, at the time
> I wrote the driver, I didn't find a way to read the interrupts generated
> by tvp5150 at em28xx[1], due to the lack of em28xx documentation,
> but adding support for it shoudn't be hard. I may eventually do it
> when I have some ti
Hi Sakari,
2017-04-04 Sakari Ailus :
> Hi Gustavo,
>
> Thank you for the patchset. Please see my comments below.
>
> On Mon, Mar 13, 2017 at 04:20:25PM -0300, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > Hi,
> >
> > This RFC adds support for Explicit Synchronization of shared buf
2017-04-03 Javier Martinez Canillas :
> Hello Mauro and Gustavo,
>
> On 04/03/2017 07:16 AM, Mauro Carvalho Chehab wrote:
> > Hi Gustavo,
> >
> > Em Mon, 13 Mar 2017 16:20:25 -0300
> > Gustavo Padovan escreveu:
> >
> >> From: Gustavo Padovan
> >>
> >> Hi,
> >>
> >> This RFC adds support for E
Em Wed, 05 Apr 2017 11:34:19 +0200
Philipp Zabel escreveu:
> On Wed, 2017-04-05 at 09:21 +0100, Russell King - ARM Linux wrote:
> [...]
> > > Actually what was I thinking, the TVP5150 is already an example of
> > > such a device.
> > >
> > > All of this could be solved if there was some directio
On Wed, 2017-04-05 at 15:09 +0200, Lucas Stach wrote:
> As long as only one CODA context is running we get alternating device_run()
> and wait_for_completion() calls, but when more then one CODA context is
> active, other VDOA slots can be inserted between those calls for one context.
>
> Make sur
Hi Philipp,
2017-04-03 Philipp Zabel :
> Hi Gustavo,
>
> On Mon, 2017-03-13 at 16:20 -0300, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > Turn the reserved2 field into fence_fd that we will use to send
> > an in-fence to the kernel return an out-fence from the kernel to
> > userspac
Hello Philipp,
On Wed, Apr 5, 2017 at 5:34 AM, Philipp Zabel wrote:
> On Wed, 2017-04-05 at 09:21 +0100, Russell King - ARM Linux wrote:
[snip]
> I think the output part is accurate, as the audio pad is an artifact of
> an unrelated change. I'm not so sure about the VBI pad, but I think that
>
Several host controllers, commonly found on ARM, like dwc2,
require buffers that are CPU-word aligned for they to work.
Failing to do that will cause buffer overflows at the caller
drivers, with could cause data corruption.
Such data corruption was found, in practice, with the uvcdriver.
Documen
Hi Lucas,
On Wed, 2017-04-05 at 15:09 +0200, Lucas Stach wrote:
> This implements a simple handler for the case where decode did not finish
> sucessfully. This might be helpful during normal streaming, but for now it
> only handles the case where the context would deadlock with userspace,
> i.e. u
On Wed, 2017-04-05 at 15:11 +0200, Lucas Stach wrote:
> The h.264 standard allows up to 16 reference frame for the high profile
> and we need one additional internal framebuffer when the VDOA is in use.
>
> Lift the current maximum of 8 internal framebuffers to allow playback
> of those video stre
On Wed, 2017-04-05 at 15:09 +0200, Lucas Stach wrote:
> The mvcol buffer needs to be placed behind the chroma plane(s), so
> use the real offset including any required rounding.
>
> Signed-off-by: Lucas Stach
Reviewed-by: Philipp Zabel
regards
Philipp
> ---
> drivers/media/platform/coda/coda
The pandoc conversion is not perfect. Do handwork in order to:
- add a title to this chapter;
- use the proper warning and note markups;
- use kernel-doc to include Kernel header and c files;
- remove legacy notes with regards to DocBook;
- some other minor adjustments to make it better to read in
As some USB documentation files got moved, adjust their
cross-references to their new place.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/ABI/stable/sysfs-bus-usb| 2 +-
Documentation/driver-api/usb/URB.rst | 2 ++
Documentation/driver-api/usb/callbacks.rst
The URB doc describes the Kernel mechanism that do USB transfers.
While the functions are already described at urb.h, there are a
number of concepts and theory that are important for USB driver
developers.
Convert it to ReST and use C ref links to point to the places
at usb.h where each function a
This document describe some USB core features. Add it to the
driver-api book.
Signed-off-by: Mauro Carvalho Chehab
---
.../{usb/dma.txt => driver-api/usb/dma.rst}| 51 --
Documentation/driver-api/usb/index.rst | 1 +
2 files changed, 28 insertions(+), 24
Currently, there are several USB core documents that are at either
written in plain text or in DocBook format. Convert them to ReST
and add to the driver-api book.
Mauro Carvalho Chehab (21):
tmplcvt: make the tool more robust
driver-api/basics.rst: add device table header
docs-rst: convert
This document describe some USB core functions. Add it to the
driver-api book.
Signed-off-by: Mauro Carvalho Chehab
---
.../anchors.txt => driver-api/usb/anchors.rst} | 36 --
Documentation/driver-api/usb/index.rst | 1 +
2 files changed, 21 insertions(+), 16
- use the proper warning and note markups;
- add references for parts of the document that will be
cross-referenced on other USB docs;
- some minor adjustments to make it better to read in
text mode and in html.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/driver-api/usb/usb.rst |
Get rid of those warnings:
Documentation/driver-api/usb/usb.rst:615: ERROR: Unknown target name:
"usb_type".
Documentation/driver-api/usb/usb.rst:615: ERROR: Unknown target name:
"usb_dir".
Documentation/driver-api/usb/usb.rst:615: ERROR: Unknown target name:
"usb_recip".
Docume
We need an space before a numbered list to avoid those warnings:
./drivers/usb/core/message.c:478: ERROR: Unexpected indentation.
./drivers/usb/core/message.c:479: WARNING: Block quote ends without a blank
line; unexpected unindent.
./include/linux/usb/composite.h:455: ERROR: Unexpected indentati
This document describe some USB core features. Add it to the
driver-api book.
Signed-off-by: Mauro Carvalho Chehab
---
.../hotplug.txt => driver-api/usb/hotplug.rst} | 66 --
Documentation/driver-api/usb/index.rst | 1 +
2 files changed, 37 insertions(+), 30
This document describe some USB core functions. Add it to the
driver-api book.
Signed-off-by: Mauro Carvalho Chehab
---
.../callbacks.txt => driver-api/usb/callbacks.rst} | 61 +++---
Documentation/driver-api/usb/index.rst | 1 +
2 files changed, 43 insertions(+), 19
By definition, we use /* private: */ tag when we won't be documenting
a parameter. However, those two parameters are documented:
./include/linux/usb/composite.h:510: warning: Excess struct/union/enum/typedef
member 'setup_pending' description in 'usb_composite_dev'
./include/linux/usb/composite.h
This document describe some USB core features. Add it to the
driver-api book.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/driver-api/usb/index.rst | 1 +
.../persist.txt => driver-api/usb/persist.rst} | 22 +-
2 files changed, 14 insertions(+), 9 d
Currently, the script just assumes to be called at
Documentation/sphinx/. Change it to work on any directory,
and make it abort if something gets wrong.
Also, be sure that both parameters are specified.
That should avoid troubles like this:
$ Documentation/sphinx/tmplcvt Documentation/DocBook/wr
There's one value that use spaces instead of tabs to ident.
That causes the following warning:
./include/linux/usb/gadget.h:193: ERROR: Unexpected indentation.
Signed-off-by: Mauro Carvalho Chehab
---
include/linux/usb/gadget.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a
This document describe some USB core functions. Add it to the
driver-api book.
Signed-off-by: Mauro Carvalho Chehab
---
.../bulk-streams.txt => driver-api/usb/bulk-streams.rst}| 13 +
Documentation/driver-api/usb/index.rst | 1 +
2 files changed, 10 insertio
The structs there at device table are used by other documentation
at the Kernel. So, add it to the driver API.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/driver-api/basics.rst | 6 ++
1 file changed, 6 insertions(+)
diff --git a/Documentation/driver-api/basics.rst
b/Documentati
This file is actually quite complex, and required several
manual handwork:
- add a title for the document;
- use the right tags for monospaced fonts;
- use c references where needed;
- adjust cross-reference to writing_usb_driver.rst
- hightlight cross-referenced lines.
With regards to C code sni
The pandoc conversion is not perfect. Do handwork in order to:
- add a title to this chapter;
- adjust function and struct references;
- use monospaced fonts for C code names;
- some other minor adjustments to make it better to read in
text mode and in html.
Signed-off-by: Mauro Carvalho Chehab
This document describe some USB core features. Add it to the
driver-api book.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/driver-api/usb/error-codes.rst | 205 +++
Documentation/driver-api/usb/index.rst | 1 +
Documentation/usb/error-codes.txt
This document describe some USB core functions. Add it to the
driver-api book.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/driver-api/usb/index.rst | 1 +
.../usb/power-management.rst} | 404 +++--
2 files changed, 214 insertions(+),
Hi Ricky,
On Mon, Dec 26, 2016 at 03:58:07PM +0800, Ricky Liang wrote:
> Hi Laurent,
>
> On Fri, Dec 16, 2016 at 9:24 AM, Laurent Pinchart
> wrote:
> > From: Sakari Ailus
> >
> > The desirable DMA attributes are not generic for all devices using
> > Videobuf2 contiguous DMA ops. Let the drivers
The h.264 standard allows up to 16 reference frame for the high profile
and we need one additional internal framebuffer when the VDOA is in use.
Lift the current maximum of 8 internal framebuffers to allow playback
of those video streams.
Signed-off-by: Lucas Stach
---
drivers/media/platform/co
As long as only one CODA context is running we get alternating device_run()
and wait_for_completion() calls, but when more then one CODA context is
active, other VDOA slots can be inserted between those calls for one context.
Make sure to wait on job completion before running a different context a
The mvcol buffer needs to be placed behind the chroma plane(s), so
use the real offset including any required rounding.
Signed-off-by: Lucas Stach
---
drivers/media/platform/coda/coda-bit.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/media/platform/coda/co
This implements a simple handler for the case where decode did not finish
sucessfully. This might be helpful during normal streaming, but for now it
only handles the case where the context would deadlock with userspace,
i.e. userspace issued DEC_CMD_STOP and waits for EOS, but after the failed
deco
Em Sun, 2 Apr 2017 15:32:31 -0600
Jonathan Corbet escreveu:
> On Thu, 30 Mar 2017 07:45:35 -0300
> Mauro Carvalho Chehab wrote:
>
> > Currently, the script just assumes to be called at
> > Documentation/sphinx/. Change it to work on any directory,
> > and make it abort if something gets wrong.
Am Mittwoch, den 05.04.2017, 13:18 +0200 schrieb Pavel Machek:
> Hi!
>
> > + * video stream multiplexer controlled via gpio or syscon
> > + *
> > + * Copyright (C) 2013 Pengutronix, Sascha Hauer
> > + * Copyright (C) 2016 Pengutronix, Philipp Zabel
>
> This is actually quite interesting. Same e
Hi!
> +https://boundarydevices.com/products/nit6x_5mp
I'd use /product/ in url, as it redirects there.
> +https://boundarydevices.com/product/nit6x_5mp_mipi
..and for consistency.
> +The following example configures a direct conversion pipeline to capture
> +from the OV5640, transmitting on M
Hi!
> +References
> +--
> +
> +[1] "i.MX 6Dual/6Quad Applications Processor Reference Manual"
> +[2] "i.MX 6Solo/6DualLite Applications Processor Reference Manual"
[2] is not present in the text above. [1] is there many times. What is
purpose of this section?
Hi!
> + * video stream multiplexer controlled via gpio or syscon
> + *
> + * Copyright (C) 2013 Pengutronix, Sascha Hauer
> + * Copyright (C) 2016 Pengutronix, Philipp Zabel
This is actually quite interesting. Same email address for two
people...
Plus, I believe this wants to say that copyrigh
On Wed, 2017-04-05 at 18:54 +0800, Minghsiu Tsai wrote:
> Driver is stable. Remove DEBUG definition from driver.
>
> There are debug message in /var/log/messages if DEBUG is defined,
> such as:
> [MTK_V4L2] level=0 fops_vcodec_open(),170: decoder capability 0
> [MTK_V4L2] level=0 fops_vcodec_open(
Driver is stable. Remove DEBUG definition from driver.
There are debug message in /var/log/messages if DEBUG is defined,
such as:
[MTK_V4L2] level=0 fops_vcodec_open(),170: decoder capability 0
[MTK_V4L2] level=0 fops_vcodec_open(),177: 1600.vcodec decoder [0]
[MTK_V4L2] level=0 fops_vcodec_re
Currently users have to use all sorts of ugly #ifery within
their drivers in order to avoid linking issues at build time.
This patch allows users to safely call these functions when
!CONFIG_RC_CORE and make decisions based on the return value
instead. This is a much more common and clean way of do
If a user specifies the use of RC as a capability, they should
really be enabling RC Core code. If they do not we WARN() them
of this and disable the capability for them.
Once we know RC Core code has not been enabled, we can update
the user's capabilities and use them as a term of reference for
On Tue, 2017-04-04 at 15:11 -0700, Steve Longerbeam wrote:
>
> On 03/30/2017 10:25 AM, Philipp Zabel wrote:
> > The TVP5150 DT bindings specify a single output port (port 0) that
> > corresponds to the video output pad (pad 1, DEMOD_PAD_VID_OUT).
> >
> > Signed-off-by: Philipp Zabel
> > ---
> > I
On Wed, 2017-04-05 at 09:21 +0100, Russell King - ARM Linux wrote:
[...]
> > Actually what was I thinking, the TVP5150 is already an example of
> > such a device.
> >
> > All of this could be solved if there was some direction information
> > in port nodes.
>
> I disagree.
>
> Philipp identified
On Tue, 04 Apr 2017, Russell King - ARM Linux wrote:
> On Tue, Apr 04, 2017 at 05:10:05PM +0100, Lee Jones wrote:
> > @@ -237,7 +241,6 @@ struct cec_adapter *cec_allocate_adapter(const struct
> > cec_adap_ops *ops,
> > if (!(caps & CEC_CAP_RC))
> > return adap;
> >
> > -#if IS_R
On Tue, 04 Apr 2017, Russell King - ARM Linux wrote:
> On Tue, Apr 04, 2017 at 04:19:39PM +0100, Lee Jones wrote:
> > On Tue, 04 Apr 2017, Hans Verkuil wrote:
> >
> > > On 04/04/2017 04:43 PM, Lee Jones wrote:
> > > > If a user specifies the use of RC as a capability, they should
> > > > really b
On Tue, 04 Apr 2017, Hans Verkuil wrote:
> On 04/04/2017 05:36 PM, Russell King - ARM Linux wrote:
> > On Tue, Apr 04, 2017 at 04:19:39PM +0100, Lee Jones wrote:
> >> On Tue, 04 Apr 2017, Hans Verkuil wrote:
> >>
> >>> On 04/04/2017 04:43 PM, Lee Jones wrote:
> If a user specifies the use of
On Tue, Apr 04, 2017 at 05:44:05PM -0700, Steve Longerbeam wrote:
>
>
> On 04/04/2017 05:40 PM, Steve Longerbeam wrote:
> >
> >
> >On 04/04/2017 04:10 PM, Russell King - ARM Linux wrote:
> >>On Thu, Mar 30, 2017 at 07:25:49PM +0200, Philipp Zabel wrote:
> >>>The TVP5150 DT bindings specify a sing
80 matches
Mail list logo
