On Wed, Jul 19, 2017 at 09:33:49AM +0300, Baruch Siach wrote:
> Hi Yong,
>
> On Wed, Jul 19, 2017 at 02:21:20PM +0800, Yong wrote:
> > On Wed, 19 Jul 2017 07:49:23 +0300
> > Baruch Siach wrote:
> > > On Wed, Jul 19, 2017 at 09:22:49AM +0800, Yong wrote:
> > > > I am waiting for more comments for
Hi Yong,
On Wed, Jul 19, 2017 at 02:21:20PM +0800, Yong wrote:
> On Wed, 19 Jul 2017 07:49:23 +0300
> Baruch Siach wrote:
> > On Wed, Jul 19, 2017 at 09:22:49AM +0800, Yong wrote:
> > > I am waiting for more comments for the sunxi-csi.h. It's pleasure if
> > > you have any suggestions about it.
>
Hi Baruch,
On Wed, 19 Jul 2017 07:49:23 +0300
Baruch Siach wrote:
> Hi Yong,
>
> On Wed, Jul 19, 2017 at 09:22:49AM +0800, Yong wrote:
> > On Tue, 18 Jul 2017 14:55:30 +0300
> > Baruch Siach wrote:
> > > I am trying to get this driver working on the Olimex A33 OLinuXino. I
> > > didn't get it
Hi Yong,
On Wed, Jul 19, 2017 at 09:22:49AM +0800, Yong wrote:
> On Tue, 18 Jul 2017 14:55:30 +0300
> Baruch Siach wrote:
> > I am trying to get this driver working on the Olimex A33 OLinuXino. I
> > didn't get it working yet, but I had some progress. See the comment below
> > on one issue I en
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 Jul 19 05:00:16 CEST 2017
media-tree git hash:0e6fd95802e25b2428749703f76ea9d54ea743a3
media_build gi
From: Fabio Estevam
clk_prepare_enable() may fail, so we should better check its return value
and propagate it in the case of error.
Signed-off-by: Fabio Estevam
---
drivers/media/i2c/ov7670.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/media/i2c/ov7670.c b/d
From: Fabio Estevam
When devm_clk_get() fails the real error code should be propagated,
instead of always returning -EPROBE_DEFER.
Signed-off-by: Fabio Estevam
---
drivers/media/i2c/ov7670.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/i2c/ov7670.c b/driver
A collection of routines that are mainly responsible
to calculate the acc parameters.
Signed-off-by: Yong Zhi
---
drivers/media/pci/intel/ipu3/ipu3-css-params.c | 3114
drivers/media/pci/intel/ipu3/ipu3-css-params.h | 105 +
drivers/media/pci/intel/ipu3/ipu3-css.h
The driver code that handles hw programming for
clock, irq and power etc.
Signed-off-by: Yong Zhi
Signed-off-by: Tomasz Figa
---
drivers/media/pci/intel/ipu3/ipu3-css.c | 521
drivers/media/pci/intel/ipu3/ipu3-css.h | 5 +
2 files changed, 526 insertions(+)
c
ipu3 imgu video device based on v4l2, vb2 and
media controller framework.
Signed-off-by: Yong Zhi
---
drivers/media/pci/intel/ipu3/ipu3-v4l2.c | 724 +++
1 file changed, 724 insertions(+)
create mode 100644 drivers/media/pci/intel/ipu3/ipu3-v4l2.c
diff --git a/drive
This patch adds support for the Intel IPU v3 as found
on Skylake and Kaby Lake SoCs. The driver has a dependency
on the firmware binary to function properly.
Signed-off-by: Yong Zhi
Signed-off-by: Tomasz Figa
---
drivers/media/pci/intel/ipu3/Kconfig | 14 +
drivers/media/pci/intel/ipu3/Makefi
Add css pipeline and v4l code.
Signed-off-by: Yong Zhi
Signed-off-by: Tomasz Figa
---
drivers/media/pci/intel/ipu3/ipu3-css.c | 1765 ++-
drivers/media/pci/intel/ipu3/ipu3-css.h | 84 ++
2 files changed, 1843 insertions(+), 6 deletions(-)
diff --git a/drivers/medi
Add the IPU3 specific processing parameter format
V4L2_META_FMT_IPU3_PARAMS and metadata formats
for 3A and other statistics:
V4L2_META_FMT_IPU3_PARAMS
V4L2_META_FMT_IPU3_STAT_3A
V4L2_META_FMT_IPU3_STAT_DVS
V4L2_META_FMT_IPU3_STAT_LACE
Signed-off-by: Yong Zhi
---
drivers/media/v4l2-core
The pools are used to store previous parameters set by
user with the parameter queue. Due to pipelining,
there needs to be multiple sets (up to four)
of parameters which are queued in a host-to-sp queue.
Signed-off-by: Yong Zhi
Signed-off-by: Tomasz Figa
---
drivers/media/pci/intel/ipu3/ipu3-cs
Functions to load and install imgu FW blobs
Signed-off-by: Yong Zhi
Signed-off-by: Tomasz Figa
---
drivers/media/pci/intel/ipu3/ipu3-abi.h| 1578
drivers/media/pci/intel/ipu3/ipu3-css-fw.c | 270 +
drivers/media/pci/intel/ipu3/ipu3-css-fw.h | 206
dri
The UAPI header defines the structures and macros
to be used by user space.
Signed-off-by: Yong Zhi
---
include/uapi/linux/intel-ipu3.h | 2182 +++
1 file changed, 2182 insertions(+)
create mode 100644 include/uapi/linux/intel-ipu3.h
diff --git a/include/uap
From: Tomasz Figa
This patch adds support for the IPU3 DMA mapping API.
Signed-off-by: Tomasz Figa
Signed-off-by: Yong Zhi
---
drivers/media/pci/intel/ipu3/Kconfig | 8 +
drivers/media/pci/intel/ipu3/Makefile | 2 +-
drivers/media/pci/intel/ipu3/ipu3-dmamap.c | 302
From: Tomasz Figa
This driver translates Intel IPU3 internal virtual
address to physical address.
Signed-off-by: Tomasz Figa
Signed-off-by: Yong Zhi
---
drivers/media/pci/intel/ipu3/Kconfig| 9 +
drivers/media/pci/intel/ipu3/Makefile | 15 +
drivers/media/pci/intel/ipu3/ipu3-mmu.c |
This patchset adds support for the Intel IPU3 (Image Processing Unit)
ImgU, which is essentially a modern memory-to-memory ISP. It implements
raw Bayer to YUV image format conversion as well as a large number of
other pixel processing algorithms for improving the image quality.
Meta data formats a
On Tue, 18 Jul 2017 14:55:30 +0300
Baruch Siach wrote:
> Hi Yong,
>
> I am trying to get this driver working on the Olimex A33 OLinuXino. I didn't
> get it working yet, but I had some progress. See the comment below on one
> issue I encountered.
>
> On Tue, Jun 27, 2017 at 07:07:34PM +0800, Y
Hans Verkuil writes:
> On 12/07/17 21:43, Hans Verkuil wrote:
>> On 12/07/17 21:02, Eric Anholt wrote:
+static int vc4_hdmi_cec_adap_transmit(struct cec_adapter *adap, u8
attempts,
+u32 signal_free_time, struct cec_msg *msg)
+{
+ struct v
Now that we have a custom printf format specifier, convert users of
full_name to use %pOF instead. This is preparation to remove storing
of the full path string for each node.
Signed-off-by: Rob Herring
Cc: Kyungmin Park
Cc: Andrzej Hajda
Cc: Mauro Carvalho Chehab
Cc: "Lad, Prabhakar"
Cc: Son
On Tue, Jul 18, 2017 at 11:27:12PM +0200, Pavel Machek wrote:
> Hi!
EHLO
>
> > > No idea really. I only have N900 working with linux at the moment. I'm
> > > trying to get N9 and N950 working, but no luck so far.
> >
> > Still no? :-(
> >
> > Do you know if you get the kernel booting? Do you h
Hi Sakari,
Just a heads up, I posted a new version of this patch today which
addresses a few short comings in v4l2_async_notifier_unregister() which
exists in this patch. With the latest patches the re-probing of
subdevices, disregarding if they are master or sub notifiers is
addressed.
Also
Hi!
> > No idea really. I only have N900 working with linux at the moment. I'm
> > trying to get N9 and N950 working, but no luck so far.
>
> Still no? :-(
>
> Do you know if you get the kernel booting? Do you have access to the serial
> console? I might have seen the e-mail chain but I lost the
Hi Sakari,
Thanks for your hard work!
On 2017-07-18 22:04:00 +0300, Sakari Ailus wrote:
> Add notifiers for sub-devices. The notifiers themselves are not visible for
> the sub-device drivers but instead are accessed through interface functions
I might be missing it, but I can't find a interface
On Tue, Jul 18, 2017 at 11:02:28PM +0200, Pavel Machek wrote:
> Hi!
>
> > > > > diff --git a/drivers/media/platform/omap3isp/ispccp2.c
> > > > > b/drivers/media/platform/omap3isp/ispccp2.c index
> > > > > 4f8fd0c00748..47210b102bcb 100644
> > > > > --- a/drivers/media/platform/omap3isp/ispccp2.c
>
Hi!
> > > > diff --git a/drivers/media/platform/omap3isp/ispccp2.c
> > > > b/drivers/media/platform/omap3isp/ispccp2.c index
> > > > 4f8fd0c00748..47210b102bcb 100644
> > > > --- a/drivers/media/platform/omap3isp/ispccp2.c
> > > > +++ b/drivers/media/platform/omap3isp/ispccp2.c
> > > > @@ -1140,6
On Tue, Jul 18, 2017 at 10:07 PM, Ard Biesheuvel
wrote:
> On 18 July 2017 at 21:01, Arnd Bergmann wrote:
>> On Tue, Jul 18, 2017 at 9:55 PM, Ard Biesheuvel
>
> Ah, now it makes sense. I was a bit surprised that
> -Wtautological-compare complains about symbolic constants that resolve
> to the same
On 18 July 2017 at 21:01, Arnd Bergmann wrote:
> On Tue, Jul 18, 2017 at 9:55 PM, Ard Biesheuvel
> wrote:
>> On 18 July 2017 at 20:53, Arnd Bergmann wrote:
>>> On Fri, Jul 14, 2017 at 2:28 PM, Ard Biesheuvel
>>> wrote:
On 14 July 2017 at 10:25, Arnd Bergmann wrote:
> gcc warns when MO
On Tue, Jul 18, 2017 at 9:55 PM, Ard Biesheuvel
wrote:
> On 18 July 2017 at 20:53, Arnd Bergmann wrote:
>> On Fri, Jul 14, 2017 at 2:28 PM, Ard Biesheuvel
>> wrote:
>>> On 14 July 2017 at 10:25, Arnd Bergmann wrote:
gcc warns when MODULES_VADDR/END is defined to the same value as
VMAL
On 18 July 2017 at 20:53, Arnd Bergmann wrote:
> On Fri, Jul 14, 2017 at 2:28 PM, Ard Biesheuvel
> wrote:
>> On 14 July 2017 at 10:25, Arnd Bergmann wrote:
>>> gcc warns when MODULES_VADDR/END is defined to the same value as
>>> VMALLOC_START/VMALLOC_END, e.g. on x86-32:
>>>
>>> fs/proc/kcore.c:
On Fri, Jul 14, 2017 at 2:28 PM, Ard Biesheuvel
wrote:
> On 14 July 2017 at 10:25, Arnd Bergmann wrote:
>> gcc warns when MODULES_VADDR/END is defined to the same value as
>> VMALLOC_START/VMALLOC_END, e.g. on x86-32:
>>
>> fs/proc/kcore.c: In function ‘add_modules_range’:
>> fs/proc/kcore.c:622:
On Tue, Jul 18, 2017 at 12:53:12PM +, Hugues FRUCHET wrote:
>
>
> On 07/18/2017 02:17 PM, H. Nikolaus Schaller wrote:
> > Hi,
> >
> >> Am 18.07.2017 um 13:59 schrieb Hans Verkuil :
> >>
> >> On 12/07/17 22:01, Sylwester Nawrocki wrote:
> >>> Hi Hugues,
> >>>
> >>> On 07/03/2017 11:16 AM, Hug
If the CSI-2 receiver isn't part of the pipeline (or isn't there to begin
with), skip its initialisation.
Signed-off-by: Sakari Ailus
---
since v1:
- Store the receiver entity per PHY. This way the function to obtain the
pipeline became redundant and was removed.
drivers/media/platform/omap3
Hi Laurent,
On Tue, Jul 18, 2017 at 11:54:21AM +0300, Laurent Pinchart wrote:
> Hi Sakari,
>
> Thank you for the patch.
>
> On Tuesday 18 Jul 2017 01:01:16 Sakari Ailus wrote:
> > If the CSI-2 receiver isn't part of the pipeline (or isn't there to begin
> > with), skip its initialisation.
> >
>
On Tue, Jul 18, 2017 at 11:40:22AM +0300, Laurent Pinchart wrote:
> Hi Sakari,
>
> Thank you for the patch.
>
> On Tuesday 18 Jul 2017 01:01:15 Sakari Ailus wrote:
> > Put the last endpoint fwnode if there are too many endpoints to handle.
> > Also tell the user about about the condition.
> >
>
On Tue, Jul 18, 2017 at 01:03:33AM +0200, Sebastian Reichel wrote:
> Hi,
>
> On Tue, Jul 18, 2017 at 01:01:10AM +0300, Sakari Ailus wrote:
> > If endpoint has an invalid configuration, ignore it instead of happily
> > proceeding to use it nonetheless. Ignoring such an endpoint is better than
> > f
Hi Sakari,
Thanks for the patch.
On 07/18/2017 08:41 PM, Sakari Ailus wrote:
> The V4L2 flash interface allows controlling multiple LEDs through a single
> sub-devices if, and only if, these LEDs are of different types. This
> approach scales badly for flash controllers that drive multiple flash
On Tue, Jul 18, 2017 at 10:03:50PM +0300, Sakari Ailus wrote:
> From: Sakari Ailus
>
> Add the as3645a flash controller to the DT source as well as the flash
> property with the as3645a device phandle to the sensor DT node.
>
> Signed-off-by: Sakari Ailus
> Reviewed-by: Sebastian Reichel
> ---
The lens-focus property contains a phandle to the lens voice coil driver
that is associated to the sensor; typically both are contained in the same
camera module.
Signed-off-by: Sakari Ailus
Acked-by: Pavel Machek
Reviewed-by: Sebastian Reichel
Acked-by: Rob Herring
---
Documentation/devicetr
To be merged to the as3645a driver patch.
Signed-off-by: Sakari Ailus
---
drivers/leds/leds-as3645a.c | 64 +
1 file changed, 42 insertions(+), 22 deletions(-)
diff --git a/drivers/leds/leds-as3645a.c b/drivers/leds/leds-as3645a.c
index b1dc32a3c620..
Add function v4l2_fwnode_reference_count() for counting external
references and v4l2_fwnode_reference_parse() for parsing them as async
sub-devices.
This can be done on e.g. flash or lens async sub-devices that are not part
of but are associated with a sensor.
struct v4l2_async_notifier.max_subde
From: Sakari Ailus
Add a LED flash class driver for the as3654a flash controller. A V4L2 flash
driver for it already exists (drivers/media/i2c/as3645a.c), and this driver
is based on that.
Signed-off-by: Sakari Ailus
---
MAINTAINERS | 6 +
drivers/leds/Kconfig| 8 +
From: Niklas Söderlund
When the registered() callback of v4l2_subdev_internal_ops is called the
subdevice has access to the master devices v4l2_dev and it's called with
the async frameworks list_lock held. In this context the subdevice can
register its own notifiers to allow for incremental disco
The current practice is that drivers iterate over their endpoints and
parse each endpoint separately. This is very similar in a number of
drivers, implement a generic function for the job. Driver specific matters
can be taken into account in the driver specific callback.
Convert the omap3isp as an
Parse async sub-devices by using
v4l2_subdev_fwnode_reference_parse_sensor_common().
These types devices aren't directly related to the sensor, but are
nevertheless handled by the smiapp driver due to the relationship of these
component to the main part of the camera module --- the sensor.
This d
Add v4l2_fwnode_parse_reference_sensor_common for parsing common
sensor properties that refer to adjacent devices such as flash or lens
driver chips.
As this is an association only, there's little a regular driver needs to
know about these devices as such.
Signed-off-by: Sakari Ailus
---
driver
Just like video devices, V4L2 sub-device nodes can and should be registered
as soon as possible. Support this by providing
v4l2_device_register_subdev_node() function.
v4l2_device_register_subdev_nodes() continues to work just as it used to.
Signed-off-by: Sakari Ailus
---
drivers/media/v4l2-cor
From: Sakari Ailus
Add the as3645a flash controller to the DT source as well as the flash
property with the as3645a device phandle to the sensor DT node.
Signed-off-by: Sakari Ailus
Reviewed-by: Sebastian Reichel
---
arch/arm/boot/dts/omap3-n9.dts | 1 +
arch/arm/boot/dts/omap3-n950-n9
Signed-off-by: Sakari Ailus
---
drivers/media/v4l2-core/v4l2-device.c | 146 --
include/media/v4l2-device.h | 12 ---
2 files changed, 67 insertions(+), 91 deletions(-)
diff --git a/drivers/media/v4l2-core/v4l2-device.c
b/drivers/media/v4l2-core/v4l2-d
The external sub-device links may well be created from the bound callback.
Don't postpone creation to the complete callback.
Signed-off-by: Sakari Ailus
---
drivers/media/platform/omap3isp/isp.c | 20 ++--
1 file changed, 6 insertions(+), 14 deletions(-)
diff --git a/drivers/med
Camera flash drivers (and LEDs) are separate from the sensor devices in
DT. In order to make an association between the two, provide the
association information to the software.
Signed-off-by: Sakari Ailus
Acked-by: Rob Herring
Acked-by: Pavel Machek
Reviewed-by: Sebastian Reichel
---
Documen
The new fwnode_property_get_reference_args() interface amends the fwnode
property API with the functionality of both of_parse_phandle_with_args()
and __acpi_node_get_property_reference().
The semantics is slightly different: the cells property is ignored on ACPI
as the number of arguments can be e
Hi folks,
This RFC patchset achieves a number of things which I've put to the same
patchset for they need to be show together to demonstrate the use cases.
I don't really intend this to compete with Niklas's patchset but much of
the problem area addressed by the two is the same.
Comments would b
Initialise the struct isp_device.crashed media entity enum field when the
ISP's local media entities have been registered, in probe. This is to make
sure that the enumeration is initialised and large enough when the media
device is made visible.
Signed-off-by: Sakari Ailus
---
drivers/media/plat
v4l2_device_register_subdev_nodes() is now nop and can be dropped without
side effects. Do so.
Signed-off-by: Sakari Ailus
---
drivers/media/platform/omap3isp/isp.c | 13 -
1 file changed, 13 deletions(-)
diff --git a/drivers/media/platform/omap3isp/isp.c
b/drivers/media/platform/o
Register the media device in probe, thus making the omap3isp device usable
once the driver is registered.
Signed-off-by: Sakari Ailus
---
drivers/media/platform/omap3isp/isp.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/drivers/media/platform/omap3isp/isp.c
The async notifier supports three callbacks to the notifier: bound, unbound
and complete. The complete callback has been traditionally used for
creating the sub-device nodes.
This approach has an inherent weakness: if registration of a single
sub-device fails for whatever reason, it renders the en
Add notifiers for sub-devices. The notifiers themselves are not visible for
the sub-device drivers but instead are accessed through interface functions
v4l2_subdev_fwnode_endpoints_parse() and
v4l2_subdev_fwnode_reference_parse_sensor_common().
Signed-off-by: Sakari Ailus
---
drivers/media/v4l2-
Hi folks,
The original design decision in the V4L2 flash API allows controlling a two
LEDs (an indicator and a flash) through a single sub-device. This covered
virtually all flash driver chips back then but this no longer holds as
there are many LED driver chips with multiple flash LED outputs. Th
Memory for struct v4l2_flash_config is allocated in
gb_lights_light_v4l2_register() for no gain and yet the allocated memory is
leaked; the struct isn't used outside the function. Fix this.
Signed-off-by: Sakari Ailus
---
drivers/staging/greybus/light.c | 17 ++---
1 file changed, 6
The V4L2 flash interface allows controlling multiple LEDs through a single
sub-devices if, and only if, these LEDs are of different types. This
approach scales badly for flash controllers that drive multiple flash LEDs
or for LED specific associations. Essentially, the original assumption of a
LED
None of the flash operations are mandatory and therefore there should be
no need for the flash ops structure either. Accept NULL.
Signed-off-by: Sakari Ailus
Reviewed-by: Sebastian Reichel
Reviewed-by: Jacek Anaszewski
---
Hi folks,
I'm planning to get this one plus "v4l2-flash: Use led_classd
Hi Hans,
On 2017-07-18 17:06:15 +0200, Hans Verkuil wrote:
> On 18/07/17 16:47, Niklas Söderlund wrote:
> >>> void v4l2_async_notifier_unregister(struct v4l2_async_notifier *notifier)
> >>> {
> >>> - struct v4l2_subdev *sd, *tmp;
> >>> + struct v4l2_subdev *sd, *tmp, **subdev;
> >>> unsigned i
Hi,
On Tue, Jul 11, 2017 at 11:06:52PM +0200, Hans Verkuil wrote:
> On 11/07/17 22:39, Maxime Ripard wrote:
> > On Tue, Jul 11, 2017 at 08:30:33AM +0200, Hans Verkuil wrote:
> >> From: Hans Verkuil
> >>
> >> This patch series adds CEC support for the sun4i HDMI controller.
> >>
> >> The CEC hardw
git://git.ragnatech.se/linux media-tree
a3db9d60a118571e696b684a6e8c692a2b064941 Merge tag 'v4.13-rc1' into patchwork
TIMEOUT after 1349m
Sorry we cannot finish the testset for your branch within a reasonable time.
It's our fault -- either some build server is down or some build worker is busy
The OMAP3 ISP supports both external and embedded BT.656 synchronization
for parallel buses. It currently gets the bus type information from the
source subdev through the .g_mbus_config() operation, but should instead
get it from DT as that's the authoritative source of bus configuration
informatio
Mauro, feel free to cherry-pick from this series if needed.
Regards,
Hans
The following changes since commit a3db9d60a118571e696b684a6e8c692a2b064941:
Merge tag 'v4.13-rc1' into patchwork (2017-07-17 11:17:36 -0300)
are available in the git repository at:
git://linuxtv.org/hverkui
On 2017-07-18 16:50:15 +0200, Hans Verkuil wrote:
> On 18/07/17 16:39, Niklas Söderlund wrote:
> > Hi Hans,
> >
> > Thanks for your feedback.
> >
> > On 2017-07-18 16:22:14 +0200, Hans Verkuil wrote:
> >> On 17/07/17 18:59, Niklas Söderlund wrote:
> >>> There is no good reason to hold the list_lo
On 18/07/17 16:47, Niklas Söderlund wrote:
>>> void v4l2_async_notifier_unregister(struct v4l2_async_notifier *notifier)
>>> {
>>> - struct v4l2_subdev *sd, *tmp;
>>> + struct v4l2_subdev *sd, *tmp, **subdev;
>>> unsigned int notif_n_subdev = notifier->num_subdevs;
>>> unsigned int n_
On 18/07/17 16:39, Niklas Söderlund wrote:
> Hi Hans,
>
> Thanks for your feedback.
>
> On 2017-07-18 16:22:14 +0200, Hans Verkuil wrote:
>> On 17/07/17 18:59, Niklas Söderlund wrote:
>>> There is no good reason to hold the list_lock when reprobing the devices
>>> and it prevents a clean implemen
Hi Hans,
Thanks for your feedback.
On 2017-07-18 16:22:43 +0200, Hans Verkuil wrote:
> On 17/07/17 18:59, Niklas Söderlund wrote:
> > Add a subdevice specific notifier which can be used by a subdevice
> > driver to compliment the master device notifier to extend the subdevice
>
> compliment -> c
Hi Hans,
Thanks for your feedback.
On 2017-07-18 16:22:14 +0200, Hans Verkuil wrote:
> On 17/07/17 18:59, Niklas Söderlund wrote:
> > There is no good reason to hold the list_lock when reprobing the devices
> > and it prevents a clean implementation of subdevice notifiers. Move the
> > actual rel
Hi Niklas,
Small spelling error discovered in here:
On 15/06/17 10:17, Niklas Söderlund wrote:
> This is a wrapper around the media entity get_fwnode_pad operation.
>
> Signed-off-by: Niklas Söderlund
> Acked-by: Sakari Ailus
> ---
> drivers/media/media-entity.c | 36 +
Hi Adam,
Thank you for the patch.
On Tuesday 18 Jul 2017 09:00:54 Adam Ford wrote:
> From: Adam Ford
>
> By default the camera driver only supports monochrome or color at 12-bit.
> This patch will allow the camera to choose between 12-bit or 8-bit
> resolution. Tested on Logic PD DM3730 Torpedo
Attention:Beneficiary
I am Meliana Trump, and I am writing to inform you about your Bank
Check Draft brought back 16/07/2017 by the United Embassy Mr John
Moore from the government of Benin Republic in the white house
Washington DC been mandated to be deliver to your home address once
you reconfi
On 17/07/17 18:59, Niklas Söderlund wrote:
> Add a subdevice specific notifier which can be used by a subdevice
> driver to compliment the master device notifier to extend the subdevice
compliment -> complement
Just one character difference, but a wildly different meaning :-)
Although it was ver
On 17/07/17 18:59, Niklas Söderlund wrote:
> There is no good reason to hold the list_lock when reprobing the devices
> and it prevents a clean implementation of subdevice notifiers. Move the
> actual release of the devices outside of the loop which requires the
> lock to be held.
>
> Signed-off-b
From: Adam Ford
By default the camera driver only supports monochrome or color at 12-bit.
This patch will allow the camera to choose between 12-bit or 8-bit resolution.
Tested on Logic PD DM3730 Torpedo Development Kit.
Signed-off-by: Adam Ford
diff --git a/Documentation/devicetree/bindings/me
Now that the multiplexer framework is merged, drop the temporary
mmio-mux implementation from the video-mux driver and convert it to use
the multiplexer API.
Signed-off-by: Philipp Zabel
---
Changes since v1:
- Select CONFIG_MULTIPLEXER.
---
drivers/media/platform/Kconfig | 1 +
drivers/me
On Tue, 2017-07-18 at 12:03 +0200, Hans Verkuil wrote:
> On 17/07/17 12:55, Philipp Zabel wrote:
> > Now that the multiplexer framework is merged, drop the temporary
> > mmio-mux implementation from the video-mux driver and convert it to use
> > the multiplexer API.
> >
> > Signed-off-by: Philipp
On 26/06/17 20:12, Laurent Pinchart wrote:
> Hello,
>
> This patch series implements support for the R-Car H3 ES2.0 SoC in the VSP
> and DU drivers.
>
> Compared to the H3 ES1.1, the H3 ES2.0 has a new VSP2-DL instance that
> includes two blending units, a BRU and a BRS. The BRS is similar to th
On 07/18/2017 02:17 PM, H. Nikolaus Schaller wrote:
> Hi,
>
>> Am 18.07.2017 um 13:59 schrieb Hans Verkuil :
>>
>> On 12/07/17 22:01, Sylwester Nawrocki wrote:
>>> Hi Hugues,
>>>
>>> On 07/03/2017 11:16 AM, Hugues Fruchet wrote:
This patchset enables OV9655 camera support.
OV9655
Hi,
> Am 18.07.2017 um 13:59 schrieb Hans Verkuil :
>
> On 12/07/17 22:01, Sylwester Nawrocki wrote:
>> Hi Hugues,
>>
>> On 07/03/2017 11:16 AM, Hugues Fruchet wrote:
>>> This patchset enables OV9655 camera support.
>>>
>>> OV9655 support has been tested using STM32F4DIS-CAM extension board
>>>
On 12/07/17 22:01, Sylwester Nawrocki wrote:
> Hi Hugues,
>
> On 07/03/2017 11:16 AM, Hugues Fruchet wrote:
>> This patchset enables OV9655 camera support.
>>
>> OV9655 support has been tested using STM32F4DIS-CAM extension board
>> plugged on connector P1 of STM32F746G-DISCO board.
>> Due to lack
Hi Yong,
I am trying to get this driver working on the Olimex A33 OLinuXino. I didn't
get it working yet, but I had some progress. See the comment below on one
issue I encountered.
On Tue, Jun 27, 2017 at 07:07:34PM +0800, Yong Deng wrote:
> Add binding documentation for Allwinner CSI.
>
> Sig
On 08/07/17 15:31, Konstantin Kozhevnikov wrote:
> Hello all,
>
> the sample is made publicly available, and can be taken from
> https://github.com/CogentEmbedded/imr-sv-utest/blob/master/utest/utest-imr.c.
>
> It doesn't show how luminance/chrominance correction actually works, however.
> That
Hi Sakari, thks for review.
On 07/09/2017 01:06 AM, Sakari Ailus wrote:
> Hi Hugues,
>
> On Mon, Jul 03, 2017 at 11:16:04AM +0200, Hugues Fruchet wrote:
>> Allows use of device tree configuration data.
>> If no device tree data is there, configuration is taken from platform data.
>> In order to k
This ensures that we fall back to PIO if the buffer is too small for DMA
being useful. Otherwise, we use DMA. A bounce buffer might be applied if
the original message buffer is not DMA safe
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-sh_mobile.c | 8 ++--
1 file changed, 6 inserti
One helper checks if DMA is suitable and optionally creates a bounce
buffer, if not. The other function returns the bounce buffer and makes
sure the data is properly copied back to the message.
Signed-off-by: Wolfram Sang
---
Changes since v2:
* rebased to v4.13-rc1
* helper functions are not in
Hi!
> I rebased the ccp2 branch and went through the patches. I didn't find
> anything really alarming there; I changed one commit description of
> "omap3isp: Correctly set IO_OUT_SEL and VP_CLK_POL for CCP2 mode" that had
> some junk in it as well as in the last patch changed the condition in
> o
Handling this is special for this driver. Because the hardware needs to
initialize the next message in interrupt context, we cannot use the
i2c_check_msg_for_dma() directly. This helper only works reliably in
process context. So, we need to check during initial preparation of the
whole transfer and
So, after revisiting old mail threads and taking part in a similar discussion
on the USB list, here is what I cooked up to document and ease DMA handling for
I2C within Linux. Please have a look at the documentation introduced in patch 2
for further details.
All patches have been tested with a Ren
Signed-off-by: Wolfram Sang
---
Changes since v2:
* documentation updates. Hopefully better wording now
Documentation/i2c/DMA-considerations | 38
1 file changed, 38 insertions(+)
create mode 100644 Documentation/i2c/DMA-considerations
diff --git a/Documen
Hi Pavel,
On Tue, Jul 18, 2017 at 12:03:52PM +0200, Pavel Machek wrote:
> Hi!
>
> > > diff --git a/drivers/media/platform/omap3isp/ispccp2.c
> > > b/drivers/media/platform/omap3isp/ispccp2.c index
> > > 4f8fd0c00748..47210b102bcb 100644
> > > --- a/drivers/media/platform/omap3isp/ispccp2.c
> > >
Hi Pavel,
On Tuesday 18 Jul 2017 12:03:52 Pavel Machek wrote:
> Hi!
>
> >> diff --git a/drivers/media/platform/omap3isp/ispccp2.c
> >> b/drivers/media/platform/omap3isp/ispccp2.c index
> >> 4f8fd0c00748..47210b102bcb 100644
> >> --- a/drivers/media/platform/omap3isp/ispccp2.c
> >> +++ b/drivers/m
Hi!
> > diff --git a/drivers/media/platform/omap3isp/ispccp2.c
> > b/drivers/media/platform/omap3isp/ispccp2.c index
> > 4f8fd0c00748..47210b102bcb 100644
> > --- a/drivers/media/platform/omap3isp/ispccp2.c
> > +++ b/drivers/media/platform/omap3isp/ispccp2.c
> > @@ -1140,6 +1140,11 @@ int omap3isp
On 17/07/17 12:55, Philipp Zabel wrote:
> Now that the multiplexer framework is merged, drop the temporary
> mmio-mux implementation from the video-mux driver and convert it to use
> the multiplexer API.
>
> Signed-off-by: Philipp Zabel
> ---
> drivers/media/platform/video-mux.c | 53
> +---
On Tue 2017-07-18 11:27:53, Pavel Machek wrote:
> Hi!
>
> > On Tue, Feb 14, 2017 at 02:40:19PM +0100, Pavel Machek wrote:
> > > Probably something fun happening in userspace.
> >
> > What's the status of this one?
> >
> > I don't think it has a chance to be merged in the foreseeable future. Why
1 - 100 of 112 matches
Mail list logo