Hi Mauro,
This pull request updates the s2255 driver with the usual v4l2-compliance and
big-endian fixes.
Tested on my s2255 device, generously supplied by Sensoray.
The patches in this pull request are unchanged from my review patch series
posted Tuesday.
Regards,
Hans
The following
On Thu, Feb 28, 2013 at 5:12 AM, Vikas Sajjan vikas.saj...@linaro.org wrote:
Adds support for pinctrl to drm fimd
Signed-off-by: Leela Krishna Amudala l.kris...@samsung.com
Signed-off-by: Vikas Sajjan vikas.saj...@linaro.org
(...)
+ pctrl = devm_pinctrl_get_select_default(dev);
Hi Linus,
On Fri, Mar 1, 2013 at 2:49 PM, Linus Walleij linus.wall...@linaro.org wrote:
On Thu, Feb 28, 2013 at 5:12 AM, Vikas Sajjan vikas.saj...@linaro.org wrote:
Adds support for pinctrl to drm fimd
Signed-off-by: Leela Krishna Amudala l.kris...@samsung.com
Signed-off-by: Vikas Sajjan
Hi All,
On Fri, Mar 1, 2013 at 11:04 AM, Vikas Sajjan vikas.saj...@linaro.org wrote:
Adds support for pinctrl to drm fimd
Signed-off-by: Leela Krishna Amudala l.kris...@samsung.com
Signed-off-by: Vikas Sajjan vikas.saj...@linaro.org
---
drivers/gpu/drm/exynos/exynos_drm_fimd.c |9
(Retry: the first pull request didn't end up in patchwork for some reason,
let's see if this works better)
Hi Mauro,
This pull request updates the s2255 driver with the usual v4l2-compliance and
big-endian fixes.
Tested on my s2255 device, generously supplied by Sensoray.
The patches in this
Hi Hans,
Thank you for the patches.
I applied the patchset on the top of SPRC's 3.8-rc4 kernel.
I tested the s5p-tv dv-timings using 0.9.3 using v4l-utils.
The test platform was Universal C210 (based on Exynos 4210 SoC).
Every timing mode worked correctly so do not hesitate to add:
Tested-by:
Hi Hans,
Please refer to the comments below.
On 02/16/2013 10:28 AM, Hans Verkuil wrote:
From: Hans Verkuil hans.verk...@cisco.com
This just adds dv_timings support without modifying existing dv_preset
support.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
Cc: Tomasz Stanislawski
Hi Hans,
Please refer to the comments below.
On 02/16/2013 10:28 AM, Hans Verkuil wrote:
From: Hans Verkuil hans.verk...@cisco.com
This just adds dv_timings support without modifying existing dv_preset
support, although I had to refactor a little bit in order to share
hdmiphy_find_conf()
Hi Hans,
Please refer to the comments below.
On 02/16/2013 10:28 AM, Hans Verkuil wrote:
From: Hans Verkuil hans.verk...@cisco.com
The dv_preset API is deprecated and is replaced by the much improved
dv_timings
API. Remove the dv_preset support from this driver as this will allow us to
On Fri March 1 2013 12:02:14 Tomasz Stanislawski wrote:
Hi Hans,
Please refer to the comments below.
On 02/16/2013 10:28 AM, Hans Verkuil wrote:
From: Hans Verkuil hans.verk...@cisco.com
This just adds dv_timings support without modifying existing dv_preset
support, although I had to
On Fri March 1 2013 12:01:09 Tomasz Stanislawski wrote:
Hi Hans,
Thank you for the patches.
I applied the patchset on the top of SPRC's 3.8-rc4 kernel.
I tested the s5p-tv dv-timings using 0.9.3 using v4l-utils.
The test platform was Universal C210 (based on Exynos 4210 SoC).
Every timing
Hi all,
This patch is based on an idea from Federico:
http://www.mail-archive.com/davinci-linux-open-source@linux.davincidsp.com/msg24669.html
While working on converting the solo6x10 driver to vb2 I realized that the
same thing was needed for the dma-sg case: the solo6x10 has 32-bit PCI DMA,
Hi Cristiano,
Em Fri, 1 Mar 2013 19:47:19 +
H. Cristiano Alves Machado heberto.mach...@gmail.com escreveu:
Hello.
I believe that this might already have been reported...
The problem can only be solved by physically removing the usb-dvb
plug, and plugging it back again... :(
Well,
Citeren Mauro Carvalho Chehab mche...@redhat.com:
Em Mon, 25 Feb 2013 12:01:17 +0100
jande...@dommel.be escreveu:
Hi,
To get analog tv working on a hauppauge hvr-930c, I started sniffing usb and
parsing.
you can see a sample here :
https://dl.dropbox.com/u/93775123/grphCable22.txt
The first 3 patches clean up / simplify the debugging and info messages a bit.
Patches 4, 5 and 6 fix two bugs I've noticed while working on the eeprom stuff.
Patches 7-10 add support for the newer eeproms with 16 bit address width.
This allows us to display the eeprom content, to calculate the
Reduces the number of characters/lines, unifies the code and improves
readability.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-i2c.c | 55 ++---
1 Datei geändert, 24 Zeilen hinzugefügt(+), 31 Zeilen entfernt(-)
The current code uses only a single debug level and all debug messages are
printed for i2c_debug = 2 only. So debug level 1 is actually the same as
level 0, which is odd.
Users expect debugging messages to become enabled for anything else than
debug level 0.
Fix it and simplify the code a bit by
There is only a single place where the dprintk2 macro is used, so get rid of it.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-i2c.c | 17 ++---
1 Datei geändert, 6 Zeilen hinzugefügt(+), 11 Zeilen entfernt(-)
diff --git
If the eeprom key isn't valid, either a different (currently unknown) format
is used or the eeprom is corrupted.
In both cases it doesn't make sense to interpret the data.
Also print an error message.
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
The data is stored as little endian in the eeprom.
Hence the correct data types should be used and the data should be converted
to the machine endianess before using it.
The eeprom id (key) also isn't a 32 bit value but 4 separate bytes instead.
Signed-off-by: Frank Schäfer
The current code first configures register EM28XX_R06_I2C_CLK, which includes
i2c speed, ack, wait and (on some devices) i2c bus selection.
The register value usually comes from the board definition.
em28xx_i2c_register() is called afterwards, which also tries to read the eeprom.
If the device
Newer devices (em2874, em2884, em28174, em25xx, em27[6,7,8]x) use eeproms with
16 bit instead of 8 bit address width.
The used eeprom type depends on the chip type, which makes sure eeproms can't
be damaged.
This patch adds basic support for 16 bit eeproms only, which includes
- reading the
Add a helper function for reading data blocks from i2c devices with 8 or 16 bit
address width and 8 bit register width.
This allows us to reduce the size of new code added by the following patches.
Works only for devices with activated register auto incrementation.
Signed-off-by: Frank Schäfer
We currently reserve an array of 256 bytes for the eeprom content in the device
struct. For eeproms with 16 bit address width it might even be necessary to
increase the buffer size further.
Having such a big chunk of memory reserved even if the device has no eeprom and
keeping it after it has
The new eeproms with 16 address width still have the the device config dataset
(the content of the old 8 bit eeproms) embedded.
Hauppauge also continues to include the tveeprom data structure inside this
dataset in their devices.
The start address of the dataset depends on the start address of the
Signed-off-by: Frank Schäfer fschaefer@googlemail.com
---
drivers/media/usb/em28xx/em28xx-cards.c |1 +
1 Datei geändert, 1 Zeile hinzugefügt(+)
diff --git a/drivers/media/usb/em28xx/em28xx-cards.c
b/drivers/media/usb/em28xx/em28xx-cards.c
index 2e3d3ad..5a5b637 100644
---
Thanks for the response, I have done as you suggested.
Below is an updated patch for the OTG102 device against
http://git.linuxtv.org/hverkuil/media_tree.git/shortlog/refs/heads/cx231xx,
kernel version 3.8.
With further testing it appears the extra clauses in cx231xx-cards.c were not
Hi everybody,
Here's a summary of the CDF BoF that took place at the ELC 2013.
I'd like to start by thanking all the participants who provided valuable
feedback (and those who didn't, but who now know a bit more about CDF and
will, I have no doubt about that, contribute in the future :-)).
Hi,
I tested the MFC decode example v4l2_decode from
http://git.infradead.org/users/kmpark/public-apps and meet some problems
as following:
# ./v4l2_decode -f /dev/video5 -m /dev/video9 -d /dev/fb0 -c mpeg4 -i
shrek.m4v
V4L2 Codec decoding example application
Kamil Debski k.deb...@samsung.com
Hi,
can someone please add the following device to imon.c?
lsusb:
Bus 001 Device 004: ID 15c2:30c0 SoundGraph Inc
It is a: Thermaltake DH202 Touch (VM90051N2Z) Case.
Regards
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to
Hi,
can someone please add the following device to imon.c?
lsusb:
Bus 001 Device 004: ID 15c2:30c0 SoundGraph Inc
It is a: Thermaltake DH202 Touch (VM90051N2Z) Case.
Regards
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to
31 matches
Mail list logo
