From: Lad, Prabhakar
export the symbols which are used by two modules vpif_capture and
vpif_display. renamed "ch_params" to "vpif_ch_params" so as to avoid
name collision.
This patch fixes following error:
ERROR: "ch_params" [drivers/media/platform/davinci/vpif_display.ko] undefined!
ERROR: "vpi
Hi Mauro,
On Wed, Mar 20, 2013 at 12:00 AM, Mauro Carvalho Chehab
wrote:
> Em Fri, 8 Mar 2013 16:19:07 +0530
> Prabhakar lad escreveu:
>
>> From: Lad, Prabhakar
>>
>> export the symbols which are used by two modules vpif_capture and
>> vpif_display.
>>
>> This patch fixes following error:
>> E
better to treate them as NUL terminated string.
Signed-off-by: Chen Gang
---
drivers/staging/media/go7007/go7007-v4l2.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/media/go7007/go7007-v4l2.c
b/drivers/staging/media/go7007/go7007-v4l2.c
index cb
for NUL terminated string, need always set '\0' in the end.
Signed-off-by: Chen Gang
---
drivers/staging/media/go7007/snd-go7007.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/media/go7007/snd-go7007.c
b/drivers/staging/media/go7007/snd-go7007
On Mon, Mar 18, 2013 at 1:11 PM, Mauro Carvalho Chehab
wrote:
> Em Tue, 26 Feb 2013 22:06:45 -0800
> Andrey Smirnov escreveu:
>
>> This patch adds all the functions used for exchanging commands with
>> the chip.
>
> Please run checkpatch.pl over those patches. There are a number of compliants
> o
Hi Anvesh,
On 03/19/2013 03:41 PM, Anvesh Manne wrote:
Hello,
Cc linux-media mailing list.
I am trying to get the OV7670 module to work with Mini2440. Despite my
best efforts, i am ending with the following image.
OK, what kernel version and drivers are you currently using. Is it some
cust
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: Tue Mar 19 19:00:25 CET 2013
git branch: test
git hash: cab3e1ffbe1b9c7a607506338f590dc1e6ca9909
gcc versio
Em Fri, 8 Mar 2013 16:19:07 +0530
Prabhakar lad escreveu:
> From: Lad, Prabhakar
>
> export the symbols which are used by two modules vpif_capture and
> vpif_display.
>
> This patch fixes following error:
> ERROR: "ch_params" [drivers/media/platform/davinci/vpif_display.ko] undefined!
> ERROR
On Tuesday 19 March 2013, Fabio Porcedda wrote:
> On Tue, Mar 19, 2013 at 5:48 PM, Arnd Bergmann wrote:
> > On Tuesday 19 March 2013, Geert Uytterhoeven wrote:
> >> Hmm, so we may have drivers that (now) work perfectly fine with
> >> module_platform_driver_probe()/platform_driver_probe(), but will
Those attributes will be used by the newer sms2xxx cards.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/sms-cards.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/media/common/siano/sms-cards.h
b/drivers/media/common/siano/sms-cards.h
index d8cdf75..60d2
There are two ways to specify firmware for siano devices: a
per-device ID and a per-device type.
The per-device type logic is currently made by a 11x9 string
table, sparsely filled. It is very hard to read the table at
the source code, as there are too much "none" filling there
("none" there is a
Put this function earlier in the code, to avoid the need of
defining a function stub.
No functional changes.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smscoreapi.c | 172
1 file changed, 84 insertions(+), 88 deletions(-)
diff --git a/d
It was expected that the bandwidth would be following the defines
at smscoreapi.h. However, this doesn't work. Instead, this field
brings just the bandwidth in MHz. Convert it to Hertz.
It should be noticed that, on ISDB, using the _EX request, the
field TuneBW seems to show the value that matches
Those new definitions came from this patch, from Doron Cohen:
http://patchwork.linuxtv.org/patch/7882/
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smscoreapi.h | 12
1 file changed, 12 insertions(+)
diff --git a/drivers/media/common/siano/smscoreapi.
As there are some changes that seem to be firmware-dependent,
we need to store the firmware version, as we don't want to break
support for existing cards that use a legacy (and sometimes
custom) firmware.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smscoreapi.c | 2 ++
dr
This is an hybrid board. However, for analog, it requires
a new driver for saa7136. So, for now, let's just add
support for Digital TV.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/video4linux/CARDLIST.em28xx | 1 +
drivers/media/usb/em28xx/Kconfig | 1 +
drivers/media/usb/e
On Tue, Mar 19, 2013 at 5:48 PM, Arnd Bergmann wrote:
> On Tuesday 19 March 2013, Geert Uytterhoeven wrote:
>> Hmm, so we may have drivers that (now) work perfectly fine with
>> module_platform_driver_probe()/platform_driver_probe(), but will start
>> failing suddenly in the future?
>
> They will
Implement poll() method for debugfs and be sure that the
debug_data won't be freed on ir or on read().
With this change, poll() will return POLLIN if either data was
filled or if data was read. That allows read() to return 0
to indicate EOF in the latter case.
As poll() is now provided, fix suppo
sms_debug() and sms_info() already adds a '\n' at the printed
strings. No need to add more.
That helps to cleanup stuff like:
[ 4868.205648] smscore_onresponse: message not handled.
[ 4868.205898] smscore_onresponse: message not handled.
and:
[ 5467.959769] smscore_onresp
There are a number of small issues with the stats refactoring:
- InBandPwr better represents the signal strength;
- Don't zero signal strength /cnr if no lock;
- Fix signal strength/cnr scale;
- Don't need to fill PER/BER if not locked, as the
code will dis
When the driver is tuned into chanel, and it is removed/reinserted,
the message stream data may be arriving during device probe:
[ 5680.162004] smscore_set_device_mode: set device mode to 6
[ 5680.162267] smscore_onresponse: message MSG_SMS_DVBT_BDA_DATA(693)
not handled.
Add the remaining new defines/enums from Doron Cohen's patch:
http://patchwork.linuxtv.org/patch/7882/
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smscoreapi.h | 39 -
1 file changed, 33 insertions(+), 6 deletions(-)
diff --git a/d
Newer firmwares seem to require an init device message. Apply
such change from Doron Cohen's patch:
http://patchwork.linuxtv.org/patch/7889/
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smscoreapi.c | 43 -
1 file changed, 42 inserti
Those fields help to identify the version of the ISDB stats.
Useful while debuging the driver.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smsdvb-debugfs.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/media/common/siano/smsdvb-debugfs.c
b/drive
As each DVBv3 call may generate an stats overhead, prevent doing
it too fast. This is specially useful if a burst of get stats
DVBv3 call is sent.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smsdvb-main.c | 5 +
drivers/media/common/siano/smsdvb.h | 2 ++
2 files
Instead of displaying this:
[ 61.869415] smscore_load_firmware_family2: rc=0, postload=0x
(null)
Display, instead:
[ 1348.441160] smscore_load_firmware_family2: rc=0
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smscoreapi.c | 13 -
Nobody is maintaining this driver. The project started by a
developer that used to work at Hauppauge. A Siano developer
assumed its maintainership after that, but he left the company.
Another Siano developer sent several patches updating it, but,
after upstream feedback, it seems he gave up merging
While this frontend provides a nice set of statistics, the
way it is currently reported to userspace is poor. Worse than
that, instead of using quality indicators that range from 0 to 65535,
as expected by userspace, most indicators range from 0 to 100.
Improve it by using DVBv5 statistics API. Th
Instead of handling both DVB-T and ISDB-T at the same get_frontend
function, break it intow one function per-delivery system.
That makes the code clearer as we start to add support for DVBv5
statistics, and for ISDB-T get frontend stuff.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/co
The old statistics request don't work with newer firmwares.
Add a logic to use the newer stats if firmware major is 8.
Note that I have only 2 devices here, one with firmware 2.1
(Hauppauge model 55009 Rev B1F7) and another one with
firmware 8.1. We may need to adjust the firmware minimal
version
Currently, every time a message is sent or received, the endiannes
need to be fixed on big endian machines. This is currently done
on every call to the send API, and on every msg reception logic.
Instead of doing that, move it to the send/receive functions.
That simplifies the logic and avoids th
The same GPIO config struct was declared twice at the
driver, with different names and different macros:
struct smscore_config_gpio
struct smscore_config_gpio
Remove the one that uses CamelCase and fix the references to
its attributes/macros.
No functional changes.
Signed-off-by:
This patch is based on Doron Cohen's patches:
http://patchwork.linuxtv.org/patch/7881/
http://patchwork.linuxtv.org/patch/7888/
http://patchwork.linuxtv.org/patch/7883/
It basically merges the above patches, rebasing them to
the macro definitions used upstream, with are dif
Backported from Doron Cohen's patch:
http://patchwork.linuxtv.org/patch/7889/
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smscoreapi.c | 56 +
1 file changed, 56 insertions(+)
diff --git a/drivers/media/common/siano/smscoreapi.c
b
There are new firmwares for sms2xxx devices. Change the firmware
load logic to handle those newer firmwares and devices.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smscoreapi.c | 348
drivers/media/common/siano/smscoreapi.h | 8 +-
2 fi
Right now, the driver sends DVB data even before tunning.
It was noticed that this may lead into some mistakes at DVB
decode, as the PIDs from wrong channels may be associated with
another frequency, as they may already be inside the PID buffers.
So, prevent it by not feeding DVB demux with data
Without smsdvb, the driver actually does nothing, as it
lacks the userspace API.
While I wrote it independently, in order to make a sms2270 board
I have here to work, this patch is functionally identical to this
patch from Doron Cohen:
http://patchwork.linuxtv.org/patch/7894/
Signed-off-b
Instead of using hardcoded descriptors, detect them from the
USB descriptors.
This patch is rebased form Doron Cohen's patch:
http://patchwork.linuxtv.org/patch/7883/
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/usb/siano/smsusb.c | 99 +---
Fix the DVBv5 API handling for ISDB-T and add support
for 13 segments.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smsdvb.c | 46 ++---
1 file changed, 17 insertions(+), 29 deletions(-)
diff --git a/drivers/media/common/siano/smsdvb.c
b/d
Instead of printing a message for some random messages, print
it for all sent/received ones. That helps a lot to debug
what's going on.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smscoreapi.c | 351 +++-
drivers/media/common/siano/smscoreapi.h
It seems that the first u32 after the header for some stats are used by
something not documented.
The stats struct starts after it.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smsdvb.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/medi
Convert from #define into an enum and add the newer message
macros as found on this patch from Doron Cohen:
http://patchwork.linuxtv.org/patch/7882/
No messages got supressed.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smscoreapi.h | 374
Instead of re-use tune_done also for stats, the better is to use
a different completion.
Also, it was noticed that sometimes, the driver answers with
MSG_SMS_SIGNAL_DETECTED_IND for status request. Fix the code to
also handle those other signal indicators.
Signed-off-by: Mauro Carvalho Chehab
--
Outputs the result of the statistics responses via debugfs.
That can help to track bugs at the stats filling.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smsdvb.c | 464 +++-
1 file changed, 355 insertions(+), 109 deletions(-)
diff --git a
Back in September, 2011, Doron Cohen submitted
a series of patches meant to add support for newer siano chipsets.
That series of patches had several pointed issues:
- It were just a diff from Siano's internal git tree and
upstreamed one. Due to that, applying it would cause
It is confusing to merge both status updates with debug stuff.
Also, it is a better idea to move those status updates to
debugfs, instead of doing a large amount of printk's like that.
So, break them into a separate block of routines.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/commo
Some cleanups at smscoreapi. Most are just CodingStyle.
Also, use kzalloc when allocating a new buffer, as it initializes
the allocated space with zero.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smscoreapi.c | 25 -
drivers/media/common/siano/sm
The very same code also exists for DVB-T. Add it for ISDB-T.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smsdvb.c | 19 ++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/drivers/media/common/siano/smsdvb.c
b/drivers/media/common/siano/smsd
Don't keep in the dark: report the firmware file name after
lookup. That helps to debug what's happening when a firmware is not
found.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smscoreapi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/common/siano/s
The check for lock logic is broken. Due to that, no PER/BER
stats will ever be showed, and the DVBV3 events will be wrong.
Also, the per-layer PER/BER stats for ISDB-T are filled with
the wrong index.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smsdvb-main.c | 46 +++
There is an special lookup code that is called when
SMS_BOARD_UNKNOWN. The logic there is bogus and will cause
an oops, as .type is SMS_UNKNOWN_TYPE (-1).
As the code would do:
return smscore_fw_lkup[type][mode];
That would mean that it would try to go past the
smscore_fw_lkup table.
So,
Instead of using a global default_mode, passed via modprobe
parameter, use the one defined inside the cards struct.
That will prevent the need of manually specify it for each
board, except, of course, if the user wants to do something
different, on boards that accept multiple types.
Signed-off-by
This seems to be ever broken. That's the status report with
Firmware 2.1, before adding support for sms2270 is:
[22273.787218] smsdvb_onresponse: MSG_SMS_GET_STATISTICS_RES
[22273.792592] IsRfLocked = 1
[22273.792592] IsDemodLocked = 1
...
[22273.792598] TransmissionMode = -64
...
(all unshown fie
The logic that detects the types of sms devices is bogus. It returns
[ 4645.187790] smsusb_init_device: line: 372: Unspecified sms device
type!
For several devices, including the one I have (SMS_RIO). In a matter
of fact, the right thing to do there is to print an error only if
the device
Based on Doron Cohen's patch:
http://patchwork.linuxtv.org/patch/7887/
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smscoreapi.c | 16
1 file changed, 16 insertions(+)
diff --git a/drivers/media/common/siano/smscoreapi.c
b/drivers/media/common/si
Siano changed the namespace on more recent API, and re-used some
of the old names. In order to be able to update the API to support
newer chips, the better is to follow this change.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/sms-cards.c | 2 +-
drivers/media/common/sian
Board #0 is an existing one. Instead of initializing the driver
with it, use a different value to detect if board is unknown.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/common/siano/smscoreapi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/common/siano/smscoreapi
On Tuesday 19 March 2013, Geert Uytterhoeven wrote:
> Hmm, so we may have drivers that (now) work perfectly fine with
> module_platform_driver_probe()/platform_driver_probe(), but will start
> failing suddenly in the future?
They will fail if someone changes the initialization order. That would
al
Add MODULE_ALIAS entry for radio-si4713 platform driver.
Signed-off-by: Eduardo Valentin
---
drivers/media/radio/radio-si4713.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/media/radio/radio-si4713.c
b/drivers/media/radio/radio-si4713.c
index ae70930..9dda9c3
As per code header comment, changing the driver license entry
to match the correct version.
Signed-off-by: Eduardo Valentin
---
drivers/media/radio/radio-si4713.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/media/radio/radio-si4713.c
b/drivers/media/radio/r
Simple addition of platform_driver->driver->owner for radio-si4713.
Signed-off-by: Eduardo Valentin
---
drivers/media/radio/radio-si4713.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/media/radio/radio-si4713.c
b/drivers/media/radio/radio-si4713.c
index cd30a
Minor changes to make alignment match on open parenthesis.
Signed-off-by: Eduardo Valentin
---
drivers/media/radio/radio-si4713.c | 53 +--
1 files changed, 26 insertions(+), 27 deletions(-)
diff --git a/drivers/media/radio/radio-si4713.c
b/drivers/media/radio
Hello Mauro and Hans,
Here are a couple of minor changes for si4713 FM transmitter driver.
These changes are also available here:
https://git.gitorious.org/si4713/si4713.git
All best,
Eduardo Valentin (4):
media: radio: CodingStyle changes on si4713
media: radio: correct module license (==>
Hi Dear
USB memory sticks /USb flash disks for promotion solutions
64MB -64GB
logo printed for free.
free samples can be sent
thanks
John
--
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
On 19 March 2013 15:29, Vikas Sajjan wrote:
> While migrating to common clock framework (CCF), found that the FIMD clocks
> were pulled down by the CCF.
> If CCF finds any clock(s) which has NOT been claimed by any of the
> drivers, then such clock(s) are PULLed low by CCF.
>
> By calling clk_prep
On 3/12/2013 1:46 PM, Sekhar Nori wrote:
> On 3/12/2013 10:44 AM, Prabhakar Lad wrote:
>> BTW this patch still is not present in media list.
> Not sure what is happening there. Its an open list as far as I can see
> and there is no message I am getting back from list. Most probably vger
> thinks
On Tue, 19 Mar 2013, Sylwester Nawrocki wrote:
> >>> + if (!IS_ERR(clk)&& !try_module_get(clk->ops->owner))
> >>> + clk = ERR_PTR(-ENODEV);
> >>> + mutex_unlock(&clk_lock);
> >>> +
> >>> + if (!IS_ERR(clk)) {
> >>> + clk->subdev = sd;
> >>
> >> Why is this needed ? It seems a stra
On 19 March 2013 15:29, Vikas Sajjan wrote:
> While migrating to common clock framework (CCF), found that the FIMD clocks
> were pulled down by the CCF.
> If CCF finds any clock(s) which has NOT been claimed by any of the
> drivers, then such clock(s) are PULLed low by CCF.
>
> By calling clk_prep
While migrating to common clock framework (CCF), found that the FIMD clocks
were pulled down by the CCF.
If CCF finds any clock(s) which has NOT been claimed by any of the
drivers, then such clock(s) are PULLed low by CCF.
By calling clk_prepare_enable() for FIMD clocks fixes the issue.
Signed-of
Hi Guennadi,
On 03/19/2013 08:32 AM, Guennadi Liakhovetski wrote:
> On Mon, 18 Mar 2013, Sylwester Nawrocki wrote:
>> On 03/15/2013 10:27 PM, Guennadi Liakhovetski wrote:
[...]
>>> diff --git a/drivers/media/v4l2-core/v4l2-clk.c
>>> b/drivers/media/v4l2-core/v4l2-clk.c
>>> new file mode 100644
>>>
On Tue, Mar 19, 2013 at 9:55 AM, Fabio Porcedda
wrote:
> On Mon, Mar 18, 2013 at 12:28 PM, Arnd Bergmann wrote:
>> On Monday 18 March 2013, Fabio Porcedda wrote:
>>> On Mon, Mar 18, 2013 at 11:58 AM, Arnd Bergmann wrote:
>>> > On Monday 18 March 2013, Fabio Porcedda wrote:
>>> >> Since by using
On Mon, Mar 18, 2013 at 12:28 PM, Arnd Bergmann wrote:
> On Monday 18 March 2013, Fabio Porcedda wrote:
>>
>> On Mon, Mar 18, 2013 at 11:58 AM, Arnd Bergmann wrote:
>> > On Monday 18 March 2013, Fabio Porcedda wrote:
>> >> Since by using platform_driver_probe() the function
>> >> ep93xx_pwm_prob
On Tue, 19 Mar 2013, Alexey Klimov wrote:
> > Or Mauro, as the original patch went in through your tree, are you
> > handling that?
>
> I think we really need to revert it before final release. It's already -rc3.
If Mauro is currently too busy to handle this, I will take it. Please send
it to m
Hi Sylwester
Thanks for reviewing.
On Mon, 18 Mar 2013, Sylwester Nawrocki wrote:
> Hi Guennadi,
>
> On 03/15/2013 10:27 PM, Guennadi Liakhovetski wrote:
> > Typical video devices like camera sensors require an external clock source.
> > Many such devices cannot even access their hardware regis
On Tue March 19 2013 00:17:32 Laurent Pinchart wrote:
> Hi Hans,
>
> Thanks for the patch.
>
> On Monday 18 March 2013 15:12:00 Hans Verkuil wrote:
> > From: Hans Verkuil
> >
> > This ioctl is defined as IOW, so pass the argument as const.
> >
> > Signed-off-by: Hans Verkuil
> > ---
>
> [sni
On Tue March 19 2013 00:20:00 Laurent Pinchart wrote:
> Hi Hans,
>
> Thanks for the patch.
>
> On Monday 18 March 2013 15:12:03 Hans Verkuil wrote:
> > From: Hans Verkuil
> >
> > This ioctl is defined as IOW, so pass the argument as const.
> >
> > Signed-off-by: Hans Verkuil
> > Acked-by: Gue
76 matches
Mail list logo