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: Sun Nov 13 05:00:16 CET 2016
media-tree git hash:bd676c0c04ec94bd830b9192e2c33f2c4532278d
media_build git
On 11/11/2016 02:55 PM, Mauro Carvalho Chehab wrote:
Em Thu, 10 Nov 2016 12:15:39 +0100
Benjamin,
Could you please test it?
Thanks!
Mauro
Hi, I the device is in use now. Can't test it with a new tree. I am
using an old tree for it.
MvH
Benjamin Larsson
--
To unsubscribe from this list: se
From: Colin Ian King
Trivial fix to spelling mistake "unnsupported" to "unsupported"
in debug message.
Signed-off-by: Colin Ian King
---
drivers/media/pci/zoran/zoran_driver.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/pci/zoran/zoran_driver.c
b/drivers/
From: Mauro Carvalho Chehab
Changeset bc29131ecb10 ("[media] gp8psk: don't do DMA on stack")
fixed the usage of DMA on stack, but the memcpy was wrong
for gp8psk_usb_in_op(). Fix it.
>From Derek's email:
"Fix confirmed using 2 different Skywalker models with
HD mpeg4, SD mpeg2."
From: Mauro Carvalho Chehab
The data_mutex is initialized too late, as it is needed for
each device driver's power control, causing an OOPS:
dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in
warm state.
BUG: unable to handle kernel NULL pointer dereference at
From: Mauro Carvalho Chehab
The DVB binding schema at the DVB core assumes that the
frontend is a separate driver. Faling to do that causes
OOPS when the module is removed, as it tries to do a
symbol_put_addr on an internal symbol, causing craches like:
WARNING: CPU: 1 PID: 28102 at kernel/modu
Hi Linus,
This patch series contain two patches fixing problems with my
patch series meant to make USB drivers to work again after the
DMA on stack changes.
The last patch on this series is actually not related to DMA on
stack. It solves a longstanding bug affecting module unload,
causing module_
Em Sat, 12 Nov 2016 02:20:37 -0800
VDR User escreveu:
> Ok, I think I had too much patching going on (I switched from 4.8.4
> kernel drivers to media_build) so I started from scratch with a fresh
> update to kernel 4.8.7. First I applied the dma stuff in this order:
>
> (from https://patchwork.l
On 11/11/16 19:49, Arnd Bergmann wrote:
> On Friday, November 11, 2016 9:13:00 AM CET Linus Torvalds wrote:
>> On Thu, Nov 10, 2016 at 8:44 AM, Arnd Bergmann wrote:
>>>
>>> Please merge these directly if you are happy with the result.
>>
>> I will take this.
>
> Thanks a lot!
>
>> I do see two
From: Laurent Pinchart
This is a wrapper around the media entity has_route operation.
Signed-off-by: Laurent Pinchart
Signed-off-by: Michal Simek
Signed-off-by: Sakari Ailus
Signed-off-by: Niklas Söderlund
---
drivers/media/media-entity.c | 16
include/media/media-entity.h
Move the sink and source pad index from struct rvin_dev to struct
rvin_graph_entity. This is done in preparation of Gen3 support where the
active subdeivce can be changed during runtime. And if the subdevice is
changed the pad numbers are different so it's better to read them a
rvin_graph_entity th
Hi All,
This series enable Gen3 VIN support in rcar-vin driver for Renesas
r8a7795 and r8a7796. It is based on top of v4.9-rc1.
Parts of this series was previously part of an different series from me
which enabled Gen3 support in a different way (using s_input instead of
a media controller) but a
If the subdevice supports dv_timings_cap the driver should not fill in
the standard. Also don't use the standard from probe time ask the
subdevice each time, this is done in preparation for Gen3 support where
the source subdevice might change during runtime.
Signed-off-by: Niklas Söderlund
---
d
Update the driver to retrieve the code and mbus_cfg values from a
rvin_graph_entity retrieved from a wrapper function instead of directly
accessing the entity for the digital port. This is done to prepare for
Gen3 support where the subdeivce might change during runtime, so to
directly accesses a sp
The functionality provided by rvin_s_fmt_vid_cap() will be needed in
other places to add Gen3 support. Split it up in a function which do the
work and one which interface with the v4l2 API.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-v4l2.c | 12 +---
1 file
On Gen3 the CSI routing is controlled by the VnCSI_IFMD register. One
feature of this register is that it's only present in the VIN0 and VIN4
instances. The register in VIN0 controls the routing for VIN0-3 and the
register in VIN4 controls routing for VIN4-7.
To be able to control routing from a m
On Gen3 the max supported width and height will be different from Gen2.
Move the limits to the struct chip_info to prepare for Gen3 support.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-core.c | 6 ++
drivers/media/platform/rcar-vin/rcar-v4l2.c | 6 ++
drivers
Each Gen3 SoC have a limited set of predefined routing possibilities for
which CSI2 device and virtual channel can be routed to which VIN
instance. Prepare to store this information in the struct rvin_info.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-vin.h | 16
Use rvin_reset_format() in rvin_s_dv_timings() instead if just resetting
a few fields. This fixes an issue where the field format was not
properly set after S_DV_TIMINGS.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-v4l2.c | 8 ++--
1 file changed, 2 insertions(+)
The rcar-vin driver only uses one pad, pad number 0.
All v4l2 operations which did not check that the requested operation
was for pad 0 have been updated with a check to enforce this.
All v4l2 operations that stored (and later restore) the requested pad
before substituting it for the subdeivc
The rvin_v4l2_probe() handler will with Gen3 support need to handle more
then one subdevice. To prepare for this move the digital subdev pad
number discover to the digital specific async notification complete
function.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-core
The code to lookup which pad is source and sink can be broken out to a
helper function.
A bad check is also dropped in this refactoring. If the subdeivce don't
supply pad information the driver would not be able to use it if the
check is kept.
Signed-off-by: Niklas Söderlund
---
drivers/media/p
This is done to prepare for Gen3 support where there can be more then
one video pipeline which can terminate in a particular VIN instance.
Each pipeline have its own set of subdevices so to attach to a specific
subdevice at probe time is not possible. The pipelines will be
configured using the medi
The CSI2 bridge needs to know the video format, propagate it after the
video source have had its say on the format.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-v4l2.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/drivers/media/platform/rcar-vin
From: Laurent Pinchart
The optional operation can be used by entities to report whether two
pads are internally connected.
Signed-off-by: Laurent Pinchart
Signed-off-by: Michal Simek
Signed-off-by: Niklas Söderlund
Acked-by: Sakari Ailus
---
include/media/media-entity.h | 5 +
1 file ch
Add the ability to process media device link change request. Link
enablement are a bit complicated on Gen3, if it's possible to enable a
link depends on what other links already are enabled. On Gen3 the 8 VIN
are split into two subgroups (VIN0-3 and VIN4-7) and from a routing
perspective these two
On Gen3 all VIN instances which wish to interact with with the shared
CSI2 resource needs to be part of the same media device and share other
information, such as subdevices and be able to call routing operations
on other VIN instances.
This patch adds a group allocator which joins all VIN instanc
Attempt to attach to the subdevices pointed out by the routing from the
CSI2 group when the video device is opened. This is the last piece
missing to enable CSI2 groups on Gen3.
If the current CSI2 routing for the group points ta a set of subdevices
which are not present (not all routings are avai
Add the SoC specific information for Renesas r8a7795.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/Kconfig | 2 +-
drivers/media/platform/rcar-vin/rcar-core.c | 71 +
2 files changed, 72 insertions(+), 1 deletion(-)
diff --git a/drivers/me
Add the SoC specific information for Renesas r8a7796.
Signed-off-by: Niklas Söderlund
---
.../devicetree/bindings/media/rcar_vin.txt | 1 +
drivers/media/platform/rcar-vin/rcar-core.c| 63 ++
2 files changed, 64 insertions(+)
diff --git a/Documentation/devic
Add the register needed to work with Gen3 hardware. This patch adds
the logic for how to work with the Gen3 hardware. More work is required
to enable the subdevice structure needed to configure capturing.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-dma.c | 98 +++
Make the subdevice helpers look not only at the local digital subdevice
but also for the CSI2 group subdevices which can be present on Gen3.
Which CSI2 group subdevices are found depends on the CSI2 subgroup
routing which is stored in the CHSEL register of the subgroup master
(VIN0 for VIN0-3 and
Parse the VIN Gen3 OF graph and register all devices in the CSI2 group
common media device. Once a subdevice is added to the common media
device list as many links as possible are added and if possible enabled.
The links between the video source device and the CSI2 bridge are
enabled as immutable
Some of the parser functions previously only used by the digital
subdevice OF/V4L2 async code will be shared with the CSI2 group
notifiers. Clarify which notifier register error message and mark which
functions are generic helpers.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-
When Gen3 support is added to the driver more then chip id will be
different for the different Soc. To avoid a lot of if statements in the
code create a struct chip_info to contain this information.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-core.c | 49
These two fields where forgotten when refactoring the format reset code
path. If they are not also reset at the same time as width and hight the
format read using G_FMT will not match reality.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-v4l2.c | 3 +++
1 file changed
Document the Gen3 devicetree bindings. The new bindings are all handled
in the port@1 node, if an endpoint is described as on Gen2 in port@0 the
driver will work in Gen2 mode and this is supported on Gen3. The new
CSI-2 video sources are only supported on Gen3.
Signed-off-by: Niklas Söderlund
---
Refactor the probe code path to look for the digital subdevice, if one
is found use it just like the driver did before (Gen2 mode) but if it's
not found prepare for a Gen3 mode by registering a pad for the media
controller API to use.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rc
The rcar-vin driver needs to be part of a media controller to support
Gen3. Give each VIN instance a unique name so it can be referenced from
userspace.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-v4l2.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff -
On Gen3 there might be a CSI2 bridge between the video source and the
VIN. Add helpers to check for this and to fetch the bridge subdevice.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-core.c | 19 +++
drivers/media/platform/rcar-vin/rcar-vin.h | 2 +
On Gen3 the CSI2 bridge stream needs to be start/stop in conjunction
with the video source. Create helpers to deal with both the Gen2 single
subdevice case and the Gen3 CSI2 group case.
In the Gen3 case there might be other simultaneous users of the bridge
and source devices so examine each entity
Now that the pad information is present in struct rvin_graph_entity use
it when verifying the media bus format.
Signed-off-by: Niklas Söderlund
---
drivers/media/platform/rcar-vin/rcar-core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/platform/rcar-vin/rcar-core.c
b/drive
A V4L2 driver for Renesas R-Car MIPI CSI-2 interface. The driver
supports the rcar-vin driver on R-Car Gen3 SoCs where a separate driver
is needed to receive CSI-2.
Driver is based on a prototype by Koji Matsuoka in the Renesas BSP.
Signed-off-by: Niklas Söderlund
---
Changes since v3:
- Update
That tuner is integrated to demodulator and communicates via
demodulators address space. We cannot register both demodulator
and tuner having same address to same I2C bus, so better to change
it platform driver in order to implement I2C adapter correctly.
Signed-off-by: Antti Palosaari
---
drive
Read eeprom content to chip state and read values there when needed.
Also debug dump eeprom content.
Signed-off-by: Antti Palosaari
---
drivers/media/usb/dvb-usb-v2/af9035.c | 126 +++---
drivers/media/usb/dvb-usb-v2/af9035.h | 5 +-
2 files changed, 60 insertions(+
Use regmap to cover I2C register operations.
Signed-off-by: Antti Palosaari
---
drivers/media/dvb-frontends/Kconfig | 1 +
drivers/media/dvb-frontends/af9033.c | 420 ++
drivers/media/dvb-frontends/af9033_priv.h | 1 +
3 files changed, 145 insertions(+)
Replace Booth's binary division algo with 64-bit multiply and division.
Fix related IF calculations.
Signed-off-by: Antti Palosaari
---
drivers/media/dvb-frontends/af9033.c | 103 +-
drivers/media/dvb-frontends/af9033_priv.h | 1 +
2 files changed, 32 insertion
it913x tuner driver is changed to platform model so we need bind it
using platform_device_register_data().
Also remove hacks from I2C adapter where fake tuner driver address
(addr >> 1) were used as those are no longer needed.
Signed-off-by: Antti Palosaari
---
drivers/media/usb/dvb-usb-v2/af90
Chip uses so called 8-bit i2c addresses, but on bus there is of
course correct 7-bit addresses with rw bit as lsb - verified
with oscilloscope.
Lets still use correct addresses in driver.
Signed-off-by: Antti Palosaari
---
drivers/media/usb/dvb-usb-v2/af9035.c | 17 +
1 file cha
Fix coding style and other small issues.
Signed-off-by: Antti Palosaari
---
drivers/media/dvb-frontends/af9033.c | 313 +++---
drivers/media/dvb-frontends/af9033.h | 3 +-
drivers/media/dvb-frontends/af9033_priv.h | 82 +---
3 files changed, 211 insertion
IT9130 series contains integrated tuner driver, which uses that
demodulator address space. Return regmap in order to allow it913x
driver communication.
Signed-off-by: Antti Palosaari
---
drivers/media/dvb-frontends/af9033.c | 1 +
drivers/media/dvb-frontends/af9033.h | 6 ++
2 files changed,
Driver supports 2 different device versions, AX and BX. Use device
IDs to pass chip version information to driver.
Signed-off-by: Antti Palosaari
---
drivers/media/tuners/it913x.c | 11 ++-
drivers/media/tuners/it913x.h | 5 -
drivers/media/usb/dvb-usb-v2/af9035.c |
Ok, I think I had too much patching going on (I switched from 4.8.4
kernel drivers to media_build) so I started from scratch with a fresh
update to kernel 4.8.7. First I applied the dma stuff in this order:
(from https://patchwork.linuxtv.org/patch/37395/raw/)
v2-18-31-gp8psk-don-t-do-DMA-on-stack
Em Fri, 11 Nov 2016 20:45:31 -0800
VDR User escreveu:
> > Sorry, forgot to add one file to the patch.
> >
> > The right fix is this one.
>
> This patch seems to fix the unload crash but unfortunately now all I
> get is "frontend 0/0 timed out while tuning".
I don't see any reason why it shoul
54 matches
Mail list logo