On 06/03/2015 10:08 PM, Olli Salonen wrote:
I cold booted my number cruncher after a hiatus of a couple of weeks,
applied a couple of extra dev_dbg printouts in the si2168_cmd_execute
and installed the newly built module. The results:
[ 663.147757] si2168 2-0066: Silicon Labs Si2168
Em Wed, 03 Jun 2015 12:14:09 -0600
Shuah Khan shua...@osg.samsung.com escreveu:
On 06/03/2015 11:42 AM, Mauro Carvalho Chehab wrote:
Em Wed, 03 Jun 2015 09:12:53 -0600
Shuah Khan shua...@osg.samsung.com escreveu:
Add new media controller API to allocate media device as a
device
I cold booted my number cruncher after a hiatus of a couple of weeks,
applied a couple of extra dev_dbg printouts in the si2168_cmd_execute
and installed the newly built module. The results:
[ 663.147757] si2168 2-0066: Silicon Labs Si2168 successfully attached
[ 663.151735] si2157 1-0060:
Hi together, I just installed my new DVR-Card. Therefor I had to clone
the linuxtv.org/media_build.git and get a text for my distro. I can't
write a patch, but with this part of the log I think it will be easy
for you to extend the dependency-administration.
Greatings!
$ git clone
Hi Jacek,
On Wed, Jun 03, 2015 at 09:56:39AM +0200, Jacek Anaszewski wrote:
Hi Sakari,
On 06/02/2015 05:32 PM, Sakari Ailus wrote:
Hi, Jacek!
On Tue, Jun 02, 2015 at 11:13:54AM +0200, Jacek Anaszewski wrote:
Hi Sakari,
On 06/01/2015 10:59 PM, Sakari Ailus wrote:
Hi Jacek,
On Mon,
Em Wed, 03 Jun 2015 09:12:54 -0600
Shuah Khan shua...@osg.samsung.com escreveu:
Change ALSA driver to use media controller API to share tuner
with DVB and V4L2 drivers that control AU0828 media device.
Media device is created based on a newly added field value
in the struct
I have a working solution (workaround) for the HVR2205/HVR2215 firmware
loading issue.
In the file:
dvb-frontends/si2168.c
change:
#define SI2168_B40 ('B' 24 | 68 16 | '4' 8 | '0' 0)
to:
#define SI2168_B40 (68 16 | '4' 8 | '0' 0)
I do not know why this works, but this is
Steven Toth stoth at kernellabs.com writes:
Many thanks to the developers for all of your hard work.
Let me guess they have changed Si2168 chip to latest C version. Driver
supports only A and B (A20, A30 and B40). I have never seen C version.
I'll look in detail and report back
Hi,
Just thought I'd clarify that in my case I haven't ever used this board with
Windows. See a more detailed dmesg output below for saa7168 and si21xx
messages. From what I am seeing the firmware is loading correctly. However I
may be wrong.
dmesg | grep 'saa7164\|si21'
[ 18.112439]
Copy the loop_through setting from the ts2020_config struct to the internal
ts2020_priv struct so that it can actually be used.
Whilst we're at it, group the bitfields together in the same order in both
structs so that the compiler has a good chance to copy them in one go.
Signed-off-by: David
Malcolm Priestley tvbox...@gmail.com wrote:
Yes, also, the workqueue appears not to be initialized when using the dvb
attached method.
I'm not sure what you're referring to. It's initialised in ts2020_probe()
just after the ts2020_priv struct is allocated - the only place it is
allocated.
On 06/03/2015 06:55 AM, Stephen Allan wrote:
I am aware that there is some development going on for the saa7164 driver to support the
Hauppauge WinTV-HVR2205. I thought I would post some feedback. I have recently compiled
the driver as at 2015-05-31 using media build tree. I am unable to
On 05/28/2015 11:07 PM, Malcolm Priestley wrote:
On 28/05/15 11:08, David Howells wrote:
Malcolm Priestley tvbox...@gmail.com wrote:
Statistics polling can not be done by lmedm04 driver's implementation of
M88RS2000/TS2020 because I2C messages stop the devices demuxer.
I did make tests
Statistics polling can not be done by lmedm04 driver's implementation of
M88RS2000/TS2020 because I2C messages stop the device's demuxer, so allow
polling for statistics to be suppressed in the ts2020 driver by setting
dont_poll in the ts2020_config struct.
Reported-by: Malcolm Priestley
Hi Sakari,
On 06/02/2015 05:32 PM, Sakari Ailus wrote:
Hi, Jacek!
On Tue, Jun 02, 2015 at 11:13:54AM +0200, Jacek Anaszewski wrote:
Hi Sakari,
On 06/01/2015 10:59 PM, Sakari Ailus wrote:
Hi Jacek,
On Mon, May 25, 2015 at 05:13:57PM +0200, Jacek Anaszewski wrote:
This patch adds helper
On 06/03/2015 10:55 AM, Antti Palosaari wrote:
On 06/03/2015 06:55 AM, Stephen Allan wrote:
I am aware that there is some development going on for the saa7164
driver to support the Hauppauge WinTV-HVR2205. I thought I would post
some feedback. I have recently compiled the driver as at
On Wed, Jun 03, 2015 at 08:39:55AM +0200, Hans Verkuil wrote:
Hi Sumit,
On 05/05/2015 04:41 PM, Sumit Semwal wrote:
Hi Russell, everyone,
First up, sincere apologies for being awol for sometime; had some
personal / medical things to take care of, and then I thought I'd wait
for the
On Tue 02-06-15 15:29:12, Andrew Morton wrote:
On Tue, 2 Jun 2015 17:23:00 +0200 Jan Kara j...@suse.cz wrote:
That's a lump of new code which many kernels won't be needing. Can we
put all this in a new .c file and select it within drivers/media
Kconfig?
So the attached patch
On 06/03/15 10:41, Russell King - ARM Linux wrote:
On Wed, Jun 03, 2015 at 08:39:55AM +0200, Hans Verkuil wrote:
Hi Sumit,
On 05/05/2015 04:41 PM, Sumit Semwal wrote:
Hi Russell, everyone,
First up, sincere apologies for being awol for sometime; had some
personal / medical things to take
I'm seeing the same issue as well. I thought that maybe some recent
Si2168 changes did impact this, but it does not seem to be the case.
I made a quick test myself. I reverted the latest si2168 patches one
by one, but that did not remedy the situation. Anyway, the kernel log
does not seem to
Hi Sumit, Rob,
Is there any reason why this patch hasn't been merged yet? It makes perfect
sense to me and I would really like to use this in the media drivers.
Many DMA engines do have a limit to the number of segments (obviously
a max count of 1 being the most common limitation, but other
Hi Sumit,
On 05/05/2015 04:41 PM, Sumit Semwal wrote:
Hi Russell, everyone,
First up, sincere apologies for being awol for sometime; had some
personal / medical things to take care of, and then I thought I'd wait
for the merge window to get over before beginning to discuss this
again.
alloc_dev_context_buffer method might fail, so add proper return value
check.
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
---
drivers/media/platform/s5p-mfc/s5p_mfc_cmd_v6.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
MFC hardware is known to trash random memory if one tries to use a
buffer buffer, which has lower DMA addresses than the configured DMA
base address. This patch adds a check for this case and proper error
handling.
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
---
Hello,
On 2015-06-03 03:22, Laurent Pinchart wrote:
On Monday 01 June 2015 14:14:17 Marek Szyprowski wrote:
If device has no DMA max_seg_size set, we assume that there is no limit
and it is safe to force it to use DMA_BIT_MASK(32) as max_seg_size to
let DMA-mapping API always create contiguous
Many thanks to the developers for all of your hard work.
Let me guess they have changed Si2168 chip to latest C version. Driver
supports only A and B (A20, A30 and B40). I have never seen C version.
I'll look in detail and report back shortly.
--
Steven Toth - Kernel Labs
From: Rob Taylor rob.tay...@codethink.co.uk
Fix calls to subdev try_fmt to use correct pad. Fixes failures with
subdevs that care about having the right pad number set.
Signed-off-by: William Towle william.to...@codethink.co.uk
Reviewed-by: Rob Taylor rob.tay...@codethink.co.uk
---
Add detection of source pad number for drivers aware of the media
controller API, so that the combination of soc_camera and rcar_vin
can create device nodes to support modern drivers such as adv7604.c
(for HDMI on Lager) and the converted adv7180.c (for composite)
underneath.
Building rcar_vin
On Wed, Jun 3, 2015 at 5:29 AM, Olli Salonen olli.salo...@iki.fi wrote:
I'm seeing the same issue as well. I thought that maybe some recent
Si2168 changes did impact this, but it does not seem to be the case.
We've had a couple of people raise this so its highly likely we have an issue.
I had
Add support for the ADV7612 chip as implemented on Renesas' Lager
board to adv7604.c, including lists for formats/colourspace/timing
selection and an IRQ handler.
Signed-off-by: William Towle william.to...@codethink.co.uk
---
drivers/media/i2c/adv7604.c | 91
Set 'default-input' property for ADV7612. Enables image/video capture
without the need to have userspace specifying routing.
Signed-off-by: Ian Molton ian.mol...@codethink.co.uk
Tested-by: William Towle william.to...@codethink.co.uk
---
arch/arm/boot/dts/r8a7790-lager.dts |1 +
1 file
From: Ben Dooks ben.do...@codethink.co.uk
Add a proper of match id for use when the device is being bound via
device tree, to avoid having to use the i2c old-style binding of the
device.
Signed-off-by: Ben Dooks ben.do...@codethink.co.uk
Signed-off-by: William.Towle william.to...@codethink.co.uk
From: Rob Taylor rob.tay...@codethink.co.uk
Adapt soc_camera_querycap() so that cap-bus_info is populated in
addition to cap-driver.
Signed-off-by: Rob Taylor rob.tay...@codethink.co.uk
Reviewed-by: William Towle william.to...@codethink.co.uk
---
drivers/media/platform/soc_camera/soc_camera.c |
Version 3. Obsoletes version 2, as seen at:
http://permalink.gmane.org/gmane.linux.drivers.video-input-infrastructure/91668
Key changes in this version: this has some reworking of the adv7604
driver probe and soc_camera initialisation functions. In addition,
we give rcar_vin.c a
Fix rcar_vin_try_fmt to use the correct pad number when calling the
subdev set_fmt. Previously pad number 0 was always used, resulting in
EINVAL if the subdev cares about the pad number (e.g. ADV7612).
Signed-off-by: William Towle william.to...@codethink.co.uk
Reviewed-by: Rob Taylor
Add DT entries for vin0, vin0_pins, and adv7612
Signed-off-by: William Towle william.to...@codethink.co.uk
Signed-off-by: Rob Taylor rob.tay...@codethink.co.uk
---
arch/arm/boot/dts/r8a7790-lager.dts | 41 ++-
1 file changed, 40 insertions(+), 1 deletion(-)
From: Rob Taylor rob.tay...@codethink.co.uk
In videobuf_setup reject buffers that are too small for the configured
format. Fixes v4l2-complience issue.
Signed-off-by: Rob Taylor rob.tay...@codethink.co.uk
Reviewed-by: William Towle william.to...@codethink.co.uk
---
From: Ian Molton ian.mol...@codethink.co.uk
Adds support to the adv7604 driver for specifying the default input
port in the Device tree. If no value is provided, the driver will be
unable to select an input without help from userspace.
Tested-by: William Towle william.to...@codethink.co.uk
From: Hans Verkuil hans.verk...@cisco.com
Fill in the std field from the video_device tvnorms field in
enum_input.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
Signed-off-by: Rob Taylor rob.tay...@codethink.co.uk
---
drivers/media/platform/soc_camera/soc_camera.c |3 +++
1 file
This adds V4L2_MBUS_FMT_RGB888_1X24 input format support
which is used by the ADV7612 chip.
Signed-off-by: Koji Matsuoka koji.matsuoka...@renesas.com
Signed-off-by: Simon Horman horms+rene...@verge.net.au
Signed-off-by: Yoshihiro Kaneko ykaneko0...@gmail.com
Modified to use MEDIA_BUS_FMT_*
From: Hans Verkuil hans.verk...@cisco.com
Remove unnecessary check and fix the error code for vb1 drivers.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
Signed-off-by: Rob Taylor rob.tay...@codethink.co.uk
---
drivers/media/platform/soc_camera/soc_camera.c |8 ++--
1 file changed,
From: Ian Molton ian.mol...@codethink.co.uk
This documentation accompanies the patch adding support for the ADV7612
dual HDMI decoder / repeater chip.
Signed-off-by: Ian Molton ian.mol...@codethink.co.uk
Reviewed-by: William Towle william.to...@codethink.co.uk
---
From: Laurent Pinchart laurent.pinch...@linaro.org
Add a new subdev operation to initialize a subdev pad config array, and
a helper function to allocate and initialize the array. This can be used
by bridge drivers to implement try format based on subdev pad
operations.
Signed-off-by: Laurent
Nicolas Antonio Corrarello ncorrare at gmail.com writes:
Hey Everyone,
I just bought this new dongle, and while the parts seem to be
supported, the usb id is not recognised.
It seems to be based on the dibcom 0700 IC and it identifies itself as
STK8096-PVR.
I tried the patch in
On 03/06/15 11:17, David Howells wrote:
Malcolm Priestley tvbox...@gmail.com wrote:
Yes, also, the workqueue appears not to be initialized when using the dvb
attached method.
I'm not sure what you're referring to. It's initialised in ts2020_probe()
just after the ts2020_priv struct is
Change ALSA driver to use media controller API to share tuner
with DVB and V4L2 drivers that control AU0828 media device.
Media device is created based on a newly added field value
in the struct snd_usb_audio_quirk. Using this approach, the
media controller API usage can be added for a specific
This patch series updates ALSA driver to use media controller
API to share tuner with DVB and V4L2 drivers that control AU0828
media device. Two new interfaces are added to media controller
API to enable creating media device as a device resource. This
allows creating media device as a device
Add new media controller API to allocate media device as a
device resource. When a media device is created on the main
struct device which is the parent device for the interface
device, it will be available to all drivers associated with
that interface. For example, if a usb media device driver
On 03/06/15 12:13, Antti Palosaari wrote:
On 05/28/2015 11:07 PM, Malcolm Priestley wrote:
On 28/05/15 11:08, David Howells wrote:
Malcolm Priestley tvbox...@gmail.com wrote:
Statistics polling can not be done by lmedm04 driver's
implementation of
M88RS2000/TS2020 because I2C messages stop
On 06/03/2015 12:29 PM, Olli Salonen wrote:
I'm seeing the same issue as well. I thought that maybe some recent
Si2168 changes did impact this, but it does not seem to be the case.
I made a quick test myself. I reverted the latest si2168 patches one
by one, but that did not remedy the
On 06/03/2015 07:37 PM, David Howells wrote:
Malcolm Priestley tvbox...@gmail.com wrote:
Yes, also, the workqueue appears not to be initialized when using the dvb
attached method.
I'm not sure what you're referring to. It's initialised in ts2020_probe()
just after the ts2020_priv struct is
Antti Palosaari cr...@iki.fi wrote:
Malcolm misses some pending patches where attach() is wrapped to I2C model
probe().
http://git.linuxtv.org/cgit.cgi/anttip/media_tree.git/log/?h=ts2020
Aha! That explains it.
ts2020: register I2C driver from legacy media attach
removes the
Malcolm Priestley tvbox...@gmail.com wrote:
Yes, also, the workqueue appears not to be initialized when using the dvb
attached method.
I'm not sure what you're referring to. It's initialised in ts2020_probe()
just after the ts2020_priv struct is allocated - the only place it is
On 03/06/15 17:43, Antti Palosaari wrote:
On 06/03/2015 07:37 PM, David Howells wrote:
Malcolm Priestley tvbox...@gmail.com wrote:
Yes, also, the workqueue appears not to be initialized when using
the dvb
attached method.
I'm not sure what you're referring to. It's initialised in
On 03/06/15 17:37, David Howells wrote:
Malcolm Priestley tvbox...@gmail.com wrote:
Yes, also, the workqueue appears not to be initialized when using the dvb
attached method.
I'm not sure what you're referring to. It's initialised in ts2020_probe()
just after the ts2020_priv struct is
On 3 June 2015 at 15:07, Hans Verkuil hverk...@xs4all.nl wrote:
On 06/03/15 10:41, Russell King - ARM Linux wrote:
On Wed, Jun 03, 2015 at 08:39:55AM +0200, Hans Verkuil wrote:
Hi Sumit,
On 05/05/2015 04:41 PM, Sumit Semwal wrote:
Hi Russell, everyone,
First up, sincere apologies for being
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 Jun 4 04:00:17 CEST 2015
git branch: test
git hash: c1c3c85ddf60a6d97c122d57d385b4929fcec4b3
gcc
The board has multiple chips, each of which are detected and
configured as part of the driver loading.
saa7164
This chip requires firmware which appears to load correctly at 20.240637
si2168
This chip requires firmware
The chip is detected and loaded but the chip version is not
identified,
On 03/06/15 12:35, David Howells wrote:
Statistics polling can not be done by lmedm04 driver's implementation of
M88RS2000/TS2020 because I2C messages stop the device's demuxer, so allow
polling for statistics to be suppressed in the ts2020 driver by setting
dont_poll in the ts2020_config
Em Wed, 03 Jun 2015 09:12:53 -0600
Shuah Khan shua...@osg.samsung.com escreveu:
Add new media controller API to allocate media device as a
device resource. When a media device is created on the main
struct device which is the parent device for the interface
device, it will be available to all
On 06/03/2015 11:42 AM, Mauro Carvalho Chehab wrote:
Em Wed, 03 Jun 2015 09:12:53 -0600
Shuah Khan shua...@osg.samsung.com escreveu:
Add new media controller API to allocate media device as a
device resource. When a media device is created on the main
struct device which is the parent
61 matches
Mail list logo
