cron job: media_tree daily build: OK
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 Jul 17 04:00:27 CEST 2014 git branch: test git hash: 3c0d394ea7022bb9666d9df97a5776c4bcc3045c gcc version:i686-linux-gcc (GCC) 4.8.2 sparse version: v0.5.0-14-gf11dd94 host hardware: x86_64 host os:3.14-5.slh.5-amd64 linux-git-arm-at91: OK linux-git-arm-davinci: OK linux-git-arm-exynos: OK linux-git-arm-mx: OK linux-git-arm-omap: OK linux-git-arm-omap1: OK linux-git-arm-pxa: OK linux-git-blackfin: OK linux-git-i686: OK linux-git-m32r: OK linux-git-mips: OK linux-git-powerpc64: OK linux-git-sh: OK linux-git-x86_64: OK linux-2.6.31.14-i686: OK linux-2.6.32.27-i686: OK linux-2.6.33.7-i686: OK linux-2.6.34.7-i686: OK linux-2.6.35.9-i686: OK linux-2.6.36.4-i686: OK linux-2.6.37.6-i686: OK linux-2.6.38.8-i686: OK linux-2.6.39.4-i686: OK linux-3.0.60-i686: OK linux-3.1.10-i686: OK linux-3.2.37-i686: OK linux-3.3.8-i686: OK linux-3.4.27-i686: OK linux-3.5.7-i686: OK linux-3.6.11-i686: OK linux-3.7.4-i686: OK linux-3.8-i686: OK linux-3.9.2-i686: OK linux-3.10.1-i686: OK linux-3.11.1-i686: OK linux-3.12.23-i686: OK linux-3.13.11-i686: OK linux-3.14.9-i686: OK linux-3.15.2-i686: OK linux-3.16-rc1-i686: OK linux-2.6.31.14-x86_64: OK linux-2.6.32.27-x86_64: OK linux-2.6.33.7-x86_64: OK linux-2.6.34.7-x86_64: OK linux-2.6.35.9-x86_64: OK linux-2.6.36.4-x86_64: OK linux-2.6.37.6-x86_64: OK linux-2.6.38.8-x86_64: OK linux-2.6.39.4-x86_64: OK linux-3.0.60-x86_64: OK linux-3.1.10-x86_64: OK linux-3.2.37-x86_64: OK linux-3.3.8-x86_64: OK linux-3.4.27-x86_64: OK linux-3.5.7-x86_64: OK linux-3.6.11-x86_64: OK linux-3.7.4-x86_64: OK linux-3.8-x86_64: OK linux-3.9.2-x86_64: OK linux-3.10.1-x86_64: OK linux-3.11.1-x86_64: OK linux-3.12.23-x86_64: OK linux-3.13.11-x86_64: OK linux-3.14.9-x86_64: OK linux-3.15.2-x86_64: OK linux-3.16-rc1-x86_64: OK apps: OK spec-git: OK sparse: WARNINGS Detailed results are available here: http://www.xs4all.nl/~hverkuil/logs/Thursday.log Full logs are available here: http://www.xs4all.nl/~hverkuil/logs/Thursday.tar.bz2 The Media Infrastructure API from this daily build is here: http://www.xs4all.nl/~hverkuil/spec/media.html -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH/RFC v4 07/21] of: add of_node_ncmp wrapper
On Fri, Jul 11, 2014 at 04:04:10PM +0200, Jacek Anaszewski wrote: > The wrapper for strnicmp is required for checking whether a node has > expected prefix. Acked-by: Sakari Ailus -- Sakari Ailus e-mail: sakari.ai...@iki.fi XMPP: sai...@retiisi.org.uk -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH/RFC v4 06/21] leds: add API for setting torch brightness
Hi Jacek,
Jacek Anaszewski wrote:
...
diff --git a/include/linux/leds.h b/include/linux/leds.h
index 1a130cc..9bea9e6 100644
--- a/include/linux/leds.h
+++ b/include/linux/leds.h
@@ -44,11 +44,21 @@ struct led_classdev {
#define LED_BLINK_ONESHOT_STOP(1 << 18)
#define LED_BLINK_INVERT (1 << 19)
#define LED_SYSFS_LOCK(1 << 20)
+#define LED_DEV_CAP_TORCH (1 << 21)
/* Set LED brightness level */
/* Must not sleep, use a workqueue if needed */
void(*brightness_set)(struct led_classdev *led_cdev,
enum led_brightness brightness);
+ /*
+* Set LED brightness immediately - it is required for flash led
+* devices as they require setting torch brightness to have immediate
+* effect. brightness_set op cannot be used for this purpose because
+* the led drivers schedule a work queue task in it to allow for
+* being called from led-triggers, i.e. from the timer irq context.
+*/
Do we need to classify actual devices based on this? I think it's rather
a different API behaviour between the LED and the V4L2 APIs.
On devices that are slow to control, the behaviour should be asynchronous
over the LED API and synchronous when accessed through the V4L2 API. How
about implementing the work queue, as I have suggested, in the framework, so
that individual drivers don't need to care about this and just implement the
synchronous variant of this op? A flag could be added to distinguish devices
that are fast so that the work queue isn't needed.
It'd be nice to avoid individual drivers having to implement multiple ops to
do the same thing, just for differing user space interfacs.
--
Kind regards,
Sakari Ailus
e-mail: sakari.ai...@iki.fi XMPP: sai...@retiisi.org.uk
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH/RFC v4 00/21] LED / flash API integration
On Wed, Jul 16, 2014 at 10:19 AM, Bryan Wu wrote: > On Fri, Jul 11, 2014 at 7:04 AM, Jacek Anaszewski > wrote: >> This is is the fourth version of the patch series being a follow up >> of the discussion on Media summit 2013-10-23, related to the >> LED / flash API integration (the notes from the discussion were >> enclosed in the message [1], paragraph 5). >> The series is based on linux-next-20140707 >> > > I really apologize that I missed your discussion email in my Gmail > inbox, it was archived some where. Even in this series some of these > patches are archived in different tab. > > I will start to review and help to push this. > In the mean time, could you please provide an git tree for me to pull? It's much easier for me to review in my git. -Bryan > > >> Description of the proposed modifications according to >> the kernel components they are relevant to: >> - LED subsystem modifications >> * added led_flash module which, when enabled in the config, >> registers flash specific sysfs attributes, if the driver >> declares related features: >> - flash_brightness >> - max_flash_brightness >> - indicator_brightness >> - max_indicator_brightness >> - flash_timeout >> - max_flash_timeout >> - flash_strobe >> - external_strobe >> - flash_fault >> and exposes kernel internal API: >> - led_classdev_flash_register >> - led_classdev_flash_unregister >> - led_set_flash_strobe >> - led_get_flash_strobe >> - led_set_flash_brightness >> - led_update_flash_brightness >> - led_set_indicator_brightness >> - led_update_indicator_brightness >> - led_set_flash_timeout >> - led_get_flash_fault >> - led_set_external_strobe >> - led_sysfs_lock >> - led_sysfs_unlock >> * added Flash Manager functionality, available when >> led_flash module is enable in the config; >> if the device tree node of a flash led device contains >> relevant subnodes, it registers following sysfs attributes: >> - strobe_provider >> - strobe_providerN >> - blocking_strobe >> following kernel internal API is exposed by the flash manager: >> - led_flash_manager_register_flash >> - led_flash_manager_unregister_flash >> - led_flash_manager_setup_strobe >> - led_flash_manager_bind_async_mux >> - led_flash_manager_unbind_async_mux >> - Addition of a V4L2 Flash sub-device registration helpers >> * added v4l2-flash.c and v4l2-flash.h files with helper >> functions that facilitate registration/unregistration >> of a subdevice, which wrapps a LED subsystem device and >> exposes V4L2 Flash control interface >> - Addition of a LED Flash Class driver for the flash cell of >> the MAX77693 mfd >> - Addition of a LED Flash Class driver for the AAT1290 current >> regulator for flash leds along with its DT binding for the >> exynos4412-trats2 board, where standalone multiplexer is >> used for modifying strobe signal routing - either from the SoC >> GPIO or from a camera sensor. This arrangment is handled >> by the newly introduced Flash Manager functionality. >> - Update of the max77693.txt DT bindings documentation >> - Update of the common leds DT bindings documentation >> >> >> Changes since v2 >> >> >> - refactored the code so that it is possible to build >> led-core without led-flash module >> - added v4l2-flash ops which slackens dependency from >> the led-flash module >> - implemented led_clamp_align_val function and led_ctrl >> structure which allows to align led control values >> in the manner compatible with V4L2 Flash controls; >> the flash brightness and timeout units have been defined >> as microamperes and microseconds respectively to properly >> support devices which define current and time levels >> as fractions of 1/1000. >> - added support for the flash privacy leds >> - modified LED sysfs locking mechanism - now it locks/unlocks >> the interface on V4L2 Flash sub-device file open/close >> - changed hw_triggered attribute name to external_strobe, >> which maps on the V4L2_FLASH_STROBE_SOURCE_EXTERNAL name >> more intuitively >> - made external_strobe and indicator related sysfs attributes >> created optionally only if related features are declared >> by the led device driver >> - removed from the series patches modifying exynos4-is media >> controller - a proposal for "flash manager" which will take >> care of flash devices registration is due to be submitted
Re: [PATCH/RFC v4 00/21] LED / flash API integration
On Fri, Jul 11, 2014 at 7:04 AM, Jacek Anaszewski wrote: > This is is the fourth version of the patch series being a follow up > of the discussion on Media summit 2013-10-23, related to the > LED / flash API integration (the notes from the discussion were > enclosed in the message [1], paragraph 5). > The series is based on linux-next-20140707 > I really apologize that I missed your discussion email in my Gmail inbox, it was archived some where. Even in this series some of these patches are archived in different tab. I will start to review and help to push this. Thanks, -Bryan > Description of the proposed modifications according to > the kernel components they are relevant to: > - LED subsystem modifications > * added led_flash module which, when enabled in the config, > registers flash specific sysfs attributes, if the driver > declares related features: > - flash_brightness > - max_flash_brightness > - indicator_brightness > - max_indicator_brightness > - flash_timeout > - max_flash_timeout > - flash_strobe > - external_strobe > - flash_fault > and exposes kernel internal API: > - led_classdev_flash_register > - led_classdev_flash_unregister > - led_set_flash_strobe > - led_get_flash_strobe > - led_set_flash_brightness > - led_update_flash_brightness > - led_set_indicator_brightness > - led_update_indicator_brightness > - led_set_flash_timeout > - led_get_flash_fault > - led_set_external_strobe > - led_sysfs_lock > - led_sysfs_unlock > * added Flash Manager functionality, available when > led_flash module is enable in the config; > if the device tree node of a flash led device contains > relevant subnodes, it registers following sysfs attributes: > - strobe_provider > - strobe_providerN > - blocking_strobe > following kernel internal API is exposed by the flash manager: > - led_flash_manager_register_flash > - led_flash_manager_unregister_flash > - led_flash_manager_setup_strobe > - led_flash_manager_bind_async_mux > - led_flash_manager_unbind_async_mux > - Addition of a V4L2 Flash sub-device registration helpers > * added v4l2-flash.c and v4l2-flash.h files with helper > functions that facilitate registration/unregistration > of a subdevice, which wrapps a LED subsystem device and > exposes V4L2 Flash control interface > - Addition of a LED Flash Class driver for the flash cell of > the MAX77693 mfd > - Addition of a LED Flash Class driver for the AAT1290 current > regulator for flash leds along with its DT binding for the > exynos4412-trats2 board, where standalone multiplexer is > used for modifying strobe signal routing - either from the SoC > GPIO or from a camera sensor. This arrangment is handled > by the newly introduced Flash Manager functionality. > - Update of the max77693.txt DT bindings documentation > - Update of the common leds DT bindings documentation > > > Changes since v2 > > > - refactored the code so that it is possible to build > led-core without led-flash module > - added v4l2-flash ops which slackens dependency from > the led-flash module > - implemented led_clamp_align_val function and led_ctrl > structure which allows to align led control values > in the manner compatible with V4L2 Flash controls; > the flash brightness and timeout units have been defined > as microamperes and microseconds respectively to properly > support devices which define current and time levels > as fractions of 1/1000. > - added support for the flash privacy leds > - modified LED sysfs locking mechanism - now it locks/unlocks > the interface on V4L2 Flash sub-device file open/close > - changed hw_triggered attribute name to external_strobe, > which maps on the V4L2_FLASH_STROBE_SOURCE_EXTERNAL name > more intuitively > - made external_strobe and indicator related sysfs attributes > created optionally only if related features are declared > by the led device driver > - removed from the series patches modifying exynos4-is media > controller - a proposal for "flash manager" which will take > care of flash devices registration is due to be submitted > - removed modifications to the LED class devices documentation, > it will be covered after the whole functionality is accepted > > > Changes since v3 > > > - added Flash Manager feature > - added generic LED Flash
Re: [PATCH/RFC v4 05/21] leds: avoid using deprecated DEVICE_ATTR macro
Hi Jacek, Jacek Anaszewski wrote: Make the sysfs attributes definition consistent in the whole file. The modification entails change of the function name: led_max_brightness_show -> max_brightness_show I'm not sure whether DEVICE_ATTR() is really deprecated but nevertheless this is cleaner. Acked-by: Sakari Ailus -- Kind regards, Sakari Ailus e-mail: sakari.ai...@iki.fi XMPP: sai...@retiisi.org.uk -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH/RFC v4 04/21] leds: Reorder include directives
Hi Jacek, Jacek Anaszewski wrote: Reorder include directives so that they are arranged in alphabetical order. Signed-off-by: Jacek Anaszewski Acked-by: Kyungmin Park Cc: Bryan Wu Cc: Richard Purdie --- drivers/leds/led-class.c | 13 +++-- drivers/leds/led-core.c |3 ++- include/linux/leds.h |2 +- 3 files changed, 10 insertions(+), 8 deletions(-) diff --git a/drivers/leds/led-class.c b/drivers/leds/led-class.c index da79bbb..0127783 100644 --- a/drivers/leds/led-class.c +++ b/drivers/leds/led-class.c @@ -9,16 +9,17 @@ * published by the Free Software Foundation. */ -#include -#include +#include +#include +#include #include +#include +#include #include +#include +#include Do you also need slab.h? #include -#include #include -#include -#include -#include #include "leds.h" static struct class *leds_class; diff --git a/drivers/leds/led-core.c b/drivers/leds/led-core.c index 0ac06ed..d156fb6 100644 --- a/drivers/leds/led-core.c +++ b/drivers/leds/led-core.c @@ -12,10 +12,11 @@ */ #include +#include #include #include +#include And mutex.h here? With that fixed, if there are some other patches that are essentially cleanups that could go in well before the rest of the set. Some of the patches will take a little longer, I presume. I'll let you know if/when there's an update regarding the compound controls patchset. -- Kind regards, Sakari Ailus e-mail: sakari.ai...@iki.fi XMPP: sai...@retiisi.org.uk -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH/RFC v4 02/21] leds: implement sysfs interface locking mechanism
Hi Jacek,
Thank you for the update!
Jacek Anaszewski wrote:
...
diff --git a/drivers/leds/led-core.c b/drivers/leds/led-core.c
index 71b40d3..4d7cb31 100644
--- a/drivers/leds/led-core.c
+++ b/drivers/leds/led-core.c
@@ -126,3 +126,21 @@ void led_set_brightness(struct led_classdev *led_cdev,
__led_set_brightness(led_cdev, brightness);
}
EXPORT_SYMBOL(led_set_brightness);
+
+/* Caller must ensure led_cdev->led_lock held */
+void led_sysfs_lock(struct led_classdev *led_cdev)
+{
+ WARN_ON(!mutex_is_locked(&led_cdev->led_lock));
How about lockdep_assert_held() instead?
--
Sakari Ailus
e-mail: sakari.ai...@iki.fi XMPP: sai...@retiisi.org.uk
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
[GIT PULL FOR v3.17] Add support for compound controls, use in solo/go7007
Hi Mauro, This is the revised pull request for the compound control patch series that you wanted. The only change made since the previous pull request is that the max dimensions is reduced to 4. The previous pull request is here: https://patchwork.linuxtv.org/patch/24546/ I have added support for getting/setting multidimensional arrays to v4l2-ctl here: http://git.linuxtv.org/cgit.cgi/hverkuil/v4l-utils.git/log/?h=compound I've also tested this with the solo and go7007 driver. Regards, Hans (1) https://www.mail-archive.com/linux-media@vger.kernel.org/msg75929.html (2) http://www.spinics.net/lists/linux-media/msg77233.html [GIT PULL FOR v3.17] The following changes since commit 3c0d394ea7022bb9666d9df97a5776c4bcc3045c: [media] dib8000: improve the message that reports per-layer locks (2014-07-07 09:59:01 -0300) are available in the git repository at: git://linuxtv.org/hverkuil/media_tree.git propapi-part5 for you to fetch changes up to a0199b540f53413f37fe5a511762b897a5a3630a: go7007: add motion detection support. (2014-07-16 16:41:49 +0200) Hans Verkuil (34): v4l2-ctrls: increase internal min/max/step/def to 64 bit v4l2-ctrls: use pr_info/cont instead of printk. videodev2.h: add initial support for compound controls. videodev2.h: add struct v4l2_query_ext_ctrl and VIDIOC_QUERY_EXT_CTRL. v4l2-ctrls: add support for compound types. v4l2: integrate support for VIDIOC_QUERY_EXT_CTRL. v4l2-ctrls: create type_ops. v4l2-ctrls: rewrite copy routines to operate on union v4l2_ctrl_ptr. v4l2-ctrls: compare values only once. v4l2-ctrls: use ptrs for all but the s32 type. v4l2-ctrls: prepare for array support v4l2-ctrls: prepare for array support. v4l2-ctrls: type_ops can handle array elements. v4l2-ctrls: add array support. v4l2-ctrls: return elem_size instead of strlen v4l2-ctrl: fix error return of copy_to/from_user. DocBook media: document VIDIOC_QUERY_EXT_CTRL. DocBook media: update VIDIOC_G/S/TRY_EXT_CTRLS. DocBook media: fix coding style in the control example code DocBook media: improve control section. DocBook media: update control section. v4l2-controls.txt: update to the new way of accessing controls. v4l2-ctrls/videodev2.h: add u8 and u16 types. DocBook media: document new u8 and u16 control types. v4l2-ctrls: fix comments v4l2-ctrls/v4l2-controls.h: add MD controls DocBook media: document new motion detection controls. v4l2: add a motion detection event. DocBook: document new v4l motion detection event. solo6x10: implement the new motion detection controls. solo6x10: implement the motion detection event. solo6x10: fix 'dma from stack' warning. solo6x10: check dma_map_sg() return value go7007: add motion detection support. Documentation/DocBook/media/v4l/controls.xml | 278 -- Documentation/DocBook/media/v4l/vidioc-dqevent.xml | 44 Documentation/DocBook/media/v4l/vidioc-g-ext-ctrls.xml | 51 +++- Documentation/DocBook/media/v4l/vidioc-queryctrl.xml | 232 +++--- Documentation/DocBook/media/v4l/vidioc-subscribe-event.xml | 8 + Documentation/video4linux/v4l2-controls.txt| 63 +++-- drivers/media/i2c/mt9v032.c| 4 +- drivers/media/i2c/smiapp/smiapp-core.c | 8 +- drivers/media/pci/ivtv/ivtv-controls.c | 4 +- drivers/media/platform/vivi.c | 9 +- drivers/media/radio/si4713/si4713.c| 4 +- drivers/media/v4l2-core/v4l2-common.c | 6 +- drivers/media/v4l2-core/v4l2-ctrls.c | 847 + drivers/media/v4l2-core/v4l2-dev.c | 2 + drivers/media/v4l2-core/v4l2-ioctl.c | 33 +++ drivers/media/v4l2-core/v4l2-subdev.c | 3 + drivers/staging/media/go7007/go7007-driver.c | 127 +++--- drivers/staging/media/go7007/go7007-fw.c | 28 ++- drivers/staging/media/go7007/go7007-priv.h | 16 ++ drivers/staging/media/go7007/go7007-v4l2.c | 317 drivers/staging/media/go7007/go7007.h | 40 drivers/staging/media/go7007/saa7134-go7007.c | 1 - drivers/staging/media/msi3101/msi001.c | 2 +- drivers/staging/media/rtl2832u_sdr/rtl2832_sdr.c | 6 +- drivers/staging/media/solo6x10/solo6x10-disp.c | 14 +- drivers/staging/media/solo6x10/solo6x10-v4l2-enc.c | 183 +++--- drivers/staging/media/solo6x10/solo6x10.h | 26 +- include/med
RE: [PATCH] s5p-mfc: limit the size of the CPB
Hi Panpan, I merged your patch to my tree. However, next time please base the patch on the newest branch from Mauro. Please mind the whitespaces, I had to manually correct them. Also, please add version number to the [PATCH] part of subject e.g. [PATCH v10]. Best wishes, -- Kamil Debski Samsung R&D Institute Poland > -Original Message- > From: panpan liu [mailto:panpan1@samsung.com] > Sent: Wednesday, July 16, 2014 3:52 AM > To: kyungmin.p...@samsung.com; k.deb...@samsung.com; > jtp.p...@samsung.com; mche...@redhat.com > Cc: linux-arm-ker...@lists.infradead.org; linux-media@vger.kernel.org > Subject: [PATCH] s5p-mfc: limit the size of the CPB > > The CPB size is limited by the hardware. Add this limit to the s_fmt. > > Signed-off-by: panpan liu > --- > drivers/media/platform/s5p-mfc/s5p_mfc_dec.c |9 ++--- > 1 file changed, 6 insertions(+), 3 deletions(-) > > diff --git a/drivers/media/platform/s5p-mfc/s5p_mfc_dec.c > b/drivers/media/platform/s5p-mfc/s5p_mfc_dec.c > index 0bae907..0621ed8 100644 > --- a/drivers/media/platform/s5p-mfc/s5p_mfc_dec.c > +++ b/drivers/media/platform/s5p-mfc/s5p_mfc_dec.c > @@ -413,6 +413,7 @@ static int vidioc_s_fmt(struct file *file, void > *priv, struct v4l2_format *f) > int ret = 0; > struct s5p_mfc_fmt *fmt; > struct v4l2_pix_format_mplane *pix_mp; > + struct s5p_mfc_buf_size *buf_size = dev->variant->buf_size; > > mfc_debug_enter(); > ret = vidioc_try_fmt(file, priv, f); > @@ -466,11 +467,13 @@ static int vidioc_s_fmt(struct file *file, void > *priv, struct v4l2_format *f) > mfc_debug(2, "The codec number is: %d\n", ctx->codec_mode); > pix_mp->height = 0; > pix_mp->width = 0; > - if (pix_mp->plane_fmt[0].sizeimage) > - ctx->dec_src_buf_size = pix_mp->plane_fmt[0].sizeimage; > - else > + if (pix_mp->plane_fmt[0].sizeimage == 0) > pix_mp->plane_fmt[0].sizeimage = ctx->dec_src_buf_size = > DEF_CPB_SIZE; > + else if (pix_mp->plane_fmt[0].sizeimage > buf_size->cpb) > + ctx->dec_src_buf_size = buf_size->cpb; > + else > + ctx->dec_src_buf_size = pix_mp->plane_fmt[0].sizeimage; > pix_mp->plane_fmt[0].bytesperline = 0; > ctx->state = MFCINST_INIT; > out: > -- > 1.7.9.5 -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Siano Rio problems (idVendor=187f, idProduct=0600)
Dear all, I hope this is the right place to ask for help / clarification (linuxtv.org/ suggests it). I saw that Siano does indeed contribute to the media drivers in the kernel (so I hope somebody relevant is reading this). I have some questions about the Siano Rio chip that I could not answer by asking google... First of all, the chip seems to be supported by the kernel (modules load), but the firmware isdbt_rio.inp is not distributed by Ubuntu. I could find a package at http://repo.huayra.conectarigualdad.gob.ar/huayra/pool/non-free/f/firmware-siano-rio/ and this contains a file with this name. This is the only place I could find it on the interwebs. Anyway, below is the actual problem (assuming the firmware mentioned above is correct). I hope to get some hints on what I could try. I am not afraid of building kernels, but haven't done so in a while... Should I write a bug report? (where)? Thanks in advance, Jo Description: Changes to the siano driver between 3.11 and 3.13 removed TERRESTRIAL support for Siano Rio chipset from the driver. Report: On my Netbook (Ubuntu 14.04, kernel 3.13) inserting the USB stick results in -- dmesg output -- [] usb 1-1: new high-speed USB device number 5 using ehci-pci [] usb 1-1: New USB device found, idVendor=187f,idProduct=0600 [] usb 1-1: New USB device strings: Mfr=1,Product=2, SerialNumber=0 [] usb 1-1: Product: MDTV Receiver [] usb 1-1: Manufacturer: MDTV Receiver [] DVB: registering new adapter (Siano Rio Digital Receiver) [] usb 1-1: DVB: registering adapter 0 frontend 0 (Siano Mobile Digital MDTV Receiver)... -- end dmesg -- and the modules being loaded. -- lsmod output smsdvb 18071 0 dvb_core 101206 1 smsdvb smsusb 17531 0 smsmdtv48244 2 smsdvb,smsusb rc_core26724 1 smsmdtv -- end lsmod -- This looks promising. When trying to scan for station using w_scan however: -- w_scan output -- w_scan version 20130331 (compiled for DVB API 5.10) guessing country 'DE', use -c to override using settings for GERMANY DVB aerial DVB-T Europe scan type TERRESTRIAL, channellist 4 output format vdr-2.0 output charset 'UTF-8', use -C to override Info: using DVB adapter auto detection. /dev/dvb/adapter0/frontend0 -> "Siano Mobile Digital MDTV Receiver" doesnt support TERRESTRIAL -> SEARCH NEXT ONE. main:3228: FATAL: * NO USEABLE TERRESTRIAL CARD FOUND. * Please check wether dvb driver is loaded and verify that no dvb application (i.e. vdr) is running. -- end w_scan -- even though this is a DVB-T receiver stick. Trying it on another machine (where I cannot install the firmware) using Ubuntu 12.04.4, kernel 3.11 w_scan does indeed scan (but cannot find a signal because the firmware is not loaded), see below. REMARK: even when not loading a firmware the behaviour above (TERRESTRIAL not supported) persists. -- wscan output on other machine -- w_scan version 20111203 (compiled for DVB API 5.4) WARNING: could not guess your country. Falling back to 'DE' guessing country 'DE', use -c to override using settings for GERMANY DVB aerial DVB-T Europe frontend_type DVB-T, channellist 4 output format vdr-1.6 WARNING: could not guess your codepage. Falling back to 'UTF-8' output charset 'UTF-8', use -C to override Info: using DVB adapter auto detection. /dev/dvb/adapter0/frontend0 -> DVB-T "Siano Mobile Digital MDTV Receiver": good :-) Using DVB-T frontend (adapter /dev/dvb/adapter0/frontend0) -_-_-_-_ Getting frontend capabilities-_-_-_-_ Using DVB API 5.a frontend 'Siano Mobile Digital MDTV Receiver' supports INVERSION_AUTO QAM_AUTO TRANSMISSION_MODE_AUTO GUARD_INTERVAL_AUTO HIERARCHY_AUTO FEC_AUTO FREQ (44.25MHz ... 867.25MHz) [...] -- end truncated wscan output -- -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[GIT PULL for 3.17] mem2mem changes
The following changes since commit 3c0d394ea7022bb9666d9df97a5776c4bcc3045c: [media] dib8000: improve the message that reports per-layer locks (2014-07-07 09:59:01 -0300) are available in the git repository at: git://linuxtv.org/kdebski/media_tree_2.git for-3.17 for you to fetch changes up to 3c3fe0e7e3d8702680b8a7dd2e3f11d7c6ebe798: s5p-mfc: limit the size of the CPB (2014-07-16 12:16:40 +0200) Jacek Anaszewski (1): s5p-mfc: Fix selective sclk_mfc init Maurizio Lombardi (1): s5p: fix error code path when failing to allocate DMA memory Michael Olbrich (2): v4l2-mem2mem: export v4l2_m2m_try_schedule coda: try to schedule a decode run after a stop command Philipp Zabel (30): coda: fix decoder I/P/B frame detection coda: fix readback of CODA_RET_DEC_SEQ_FRAME_NEED coda: fix h.264 quantization parameter range coda: fix internal framebuffer allocation size coda: simplify IRAM setup coda: Add encoder/decoder support for CODA960 coda: remove BUG() in get_q_data coda: add selection API support for h.264 decoder coda: add workqueue to serialize hardware commands coda: Use mem-to-mem ioctl helpers coda: use ctx->fh.m2m_ctx instead of ctx->m2m_ctx coda: Add runtime pm support coda: split firmware version check out of coda_hw_init coda: select GENERIC_ALLOCATOR coda: add h.264 min/max qp controls coda: add h.264 deblocking filter controls coda: add cyclic intra refresh control coda: add decoder timestamp queue coda: alert userspace about macroblock errors coda: add sequence counter offset coda: rename prescan_failed to hold and stop stream after timeout coda: add reset control support coda: add bytesperline to queue data coda: allow odd width, but still round up bytesperline coda: round up internal frames to multiples of macroblock size for h.264 coda: increase frame stride to 16 for h.264 coda: export auxiliary buffers via debugfs coda: store per-context work buffer size in struct coda_devtype coda: store global temporary buffer size in struct coda_devtype coda: store IRAM size in struct coda_devtype panpan liu (1): s5p-mfc: limit the size of the CPB drivers/media/platform/Kconfig|1 + drivers/media/platform/coda.c | 1505 + drivers/media/platform/coda.h | 115 +- drivers/media/platform/s5p-mfc/s5p_mfc_ctrl.c |5 +- drivers/media/platform/s5p-mfc/s5p_mfc_dec.c |9 +- drivers/media/platform/s5p-mfc/s5p_mfc_pm.c | 24 + drivers/media/v4l2-core/v4l2-mem2mem.c|3 +- include/media/v4l2-mem2mem.h |2 + 8 files changed, 1195 insertions(+), 469 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
