Bug#994050: linux-image-5.10.0-8-amd64: Hauppauge WinTV-HVR1110 DVB-T/Hybrid bug 125 ms polling on ir-kbd-i2c.ko bad DEFAULT_POLLING_INTERVAL
Thanks for the aclarations, this misunderstanding are for English isn't my mother language. I really apreciate your guide. I just contacted to Upstream main mantainers (as you sugested) and let's see how this develop. See ya! From: Salvatore Bonaccorso on behalf of Salvatore Bonaccorso Sent: Saturday, September 11, 2021 08:58 To: Joaquín Alberto Calderón Pozo Cc: 994...@bugs.debian.org <994...@bugs.debian.org> Subject: Re: Bug#994050: linux-image-5.10.0-8-amd64: Hauppauge WinTV-HVR1110 DVB-T/Hybrid bug 125 ms polling on ir-kbd-i2c.ko bad DEFAULT_POLLING_INTERVAL Hi! On Sat, Sep 11, 2021 at 02:18:30AM +, Joaquín Alberto Calderón Pozo wrote: > Hi Salvatore. > > As I mentioned early, I am newbie in reporting bugs and your help is > much appreciated. > > It is the first time I report a bug, and as you noticed I don't know > where to start, this is the reason I read the debian documentation > and using the reportbug program. > > As after what you've told me it doesn't seem to be a downstream > issue, I will investigate and further report in upstream and sorry > for the inconveniences. First of all, don't worry it was not to "push back" you in any way. Thinking of what you reported I was just stating that this should be turned directly to upstream. You did already a good analysis tracking down where you see the problem, and even if the patch you apply might not be the "real" solution it gives the maintainers maybe th right hint. You did already a great start on this trying to track down hwere you see the issue. The get_maintainers.pl script in the linux (upstream) sources gives the possibility to find the "correct" persons to contact. So this would be my suggestion to contact Mauro Carvalho Chehab and the respective linux-media lists. Thanks for reporting! Regards, Salvatore
Bug#994050: linux-image-5.10.0-8-amd64: Hauppauge WinTV-HVR1110 DVB-T/Hybrid bug 125 ms polling on ir-kbd-i2c.ko bad DEFAULT_POLLING_INTERVAL
Hi! On Sat, Sep 11, 2021 at 02:18:30AM +, Joaquín Alberto Calderón Pozo wrote: > Hi Salvatore. > > As I mentioned early, I am newbie in reporting bugs and your help is > much appreciated. > > It is the first time I report a bug, and as you noticed I don't know > where to start, this is the reason I read the debian documentation > and using the reportbug program. > > As after what you've told me it doesn't seem to be a downstream > issue, I will investigate and further report in upstream and sorry > for the inconveniences. First of all, don't worry it was not to "push back" you in any way. Thinking of what you reported I was just stating that this should be turned directly to upstream. You did already a good analysis tracking down where you see the problem, and even if the patch you apply might not be the "real" solution it gives the maintainers maybe th right hint. You did already a great start on this trying to track down hwere you see the issue. The get_maintainers.pl script in the linux (upstream) sources gives the possibility to find the "correct" persons to contact. So this would be my suggestion to contact Mauro Carvalho Chehab and the respective linux-media lists. Thanks for reporting! Regards, Salvatore
Bug#994050: linux-image-5.10.0-8-amd64: Hauppauge WinTV-HVR1110 DVB-T/Hybrid bug 125 ms polling on ir-kbd-i2c.ko bad DEFAULT_POLLING_INTERVAL
Hi Salvatore.
As I mentioned early, I am newbie in reporting bugs and your help is much
appreciated.
It is the first time I report a bug, and as you noticed I don't know where to
start, this is the reason I read the debian documentation and using the
reportbug program.
As after what you've told me it doesn't seem to be a downstream issue, I will
investigate and further report in upstream and sorry for the inconveniences.
Best regards.
From: Salvatore Bonaccorso on behalf of
Salvatore Bonaccorso
Sent: Friday, September 10, 2021 21:06
To: Joaquín Alberto Calderón ;
994...@bugs.debian.org <994...@bugs.debian.org>
Subject: Re: Bug#994050: linux-image-5.10.0-8-amd64: Hauppauge WinTV-HVR1110
DVB-T/Hybrid bug 125 ms polling on ir-kbd-i2c.ko bad DEFAULT_POLLING_INTERVAL
Control: tags -1 + moreinfo upstream
Hi
On Fri, Sep 10, 2021 at 07:18:07PM +0200, Joaquín Alberto Calderón wrote:
> Package: src:linux
> Version: 5.10.46-4
> Severity: important
> Tags: patch
> X-Debbugs-Cc: kini_calde...@hotmail.com
>
> Although I have a very old pci (not express) Hauppauge WinTV-HVR1110
> DVB-T/Hybrid TV card with a remote control, I am still using it because has
> fully support and functionallity and it's hardware capable of play DVB-T HD
> streams.
>
> It has a very strange behaviour:
>
> -One is it has a slow response when I push a key, has a delay, and sometimes
> even no key response, nothing happens, as if never push a key.
> -Other is when you hold a key, it start to begin the repeat key (characters
> like numerical) appears in the test app (kwrite) then, has a pause, stops to
> write characters, and begin the sequence again, writes some sequence, then
> stops... and so on. Even I noticed the repeat speed is a bit slow, compared to
> a keyboard key hold on.
>
> So... I began to investigates the causes and after two weeks of research,
> searchs on the web, I found the module affected and a solution.
>
> The module affected is ir-kbd-i2c.ko, this remote (rc5 protocol) uses this
> module as uinput (devinput) device, in resume as like an attatched keyboard.
> Resulting investigation in get noticed that this remote with rc5 protocol has
> 8hz of time frame when receiving the air gap code (rc5 procotol timing).
>
> Investigating the sources files in the kernel sources for try and fall, re-
> compiling the modules, get me to get noticed that the polling ir remote
> interval is 100ms which is 5hz, forcing this value to 125ms, re-compiling the
> module causes the remote to work normally as expecte, the response is like a
> real keyboard and the repeat sequence not only as speedy as a normal keyboard,
> but also hasn't got a pause in repetition. In resume, the problem is solved.
>
> Here is the patch:
>
> --- ir-kbd-i2c.original.c 2021-09-08 23:45:23.723210301 +0200
> +++ ir-kbd-i2c.hauppauge.patched.c 2021-09-10 03:55:28.003529072 +0200
> @@ -742,7 +742,7 @@
> return -ENOMEM;
>
> ir->c = client;
> - ir->polling_interval = DEFAULT_POLLING_INTERVAL;
> + ir->polling_interval = 125;
> i2c_set_clientdata(client, ir);
>
> switch(addr) {
>
> I am a experienced user, but not an experienced developer, also in
> editing/submitting bugs, I don't know if this is the right way to solve this,
> If the rest of brand remotes are affected for my solution, but for me, solved
> my problem in this particular case.
>
> I don't know where the value DEFAULT_POLLING_INTERVAL is get stablished or a
> way when detect a Hauppauge WinTV-HVR1110 DVB-T/Hybrid TV card to stablish
> 125ms instead of 100ms. As I said, I'm not an expert but experienced user.
>
> I don't know if this is the right package to post this bug. Thanks.
Thanks for the report!
This is IMHO not something which should handled with an entry point in
downstream in Debian, but rather going to report it upstream directly.
Can you do that?
Details on reporting:
https://www.kernel.org/doc/html/latest/admin-guide/bug-hunting.html
Best guess for reporting the issue you are seeing:
$ ./scripts/get_maintainer.pl ./drivers/media/i2c/ir-kbd-i2c.c
Mauro Carvalho Chehab (maintainer:MEDIA INPUT
INFRASTRUCTURE (V4L/DVB),commit_signer:1/1=100%)
Sean Young (commit_signer:1/1=100%)
Christophe JAILLET
(commit_signer:1/1=100%,authored:1/1=100%,added_lines:2/2=100%,removed_lines:2/2=100%)
linux-me...@vger.kernel.org (open list:MEDIA INPUT INFRASTRUCTURE (V4L/DVB))
linux-ker...@vger.kernel.org (open list)
Feel free to keep this bugreport downstream into the loop.
Regards,
Salvatore
Bug#994050: linux-image-5.10.0-8-amd64: Hauppauge WinTV-HVR1110 DVB-T/Hybrid bug 125 ms polling on ir-kbd-i2c.ko bad DEFAULT_POLLING_INTERVAL
Control: tags -1 + moreinfo upstream
Hi
On Fri, Sep 10, 2021 at 07:18:07PM +0200, Joaquín Alberto Calderón wrote:
> Package: src:linux
> Version: 5.10.46-4
> Severity: important
> Tags: patch
> X-Debbugs-Cc: kini_calde...@hotmail.com
>
> Although I have a very old pci (not express) Hauppauge WinTV-HVR1110
> DVB-T/Hybrid TV card with a remote control, I am still using it because has
> fully support and functionallity and it's hardware capable of play DVB-T HD
> streams.
>
> It has a very strange behaviour:
>
> -One is it has a slow response when I push a key, has a delay, and sometimes
> even no key response, nothing happens, as if never push a key.
> -Other is when you hold a key, it start to begin the repeat key (characters
> like numerical) appears in the test app (kwrite) then, has a pause, stops to
> write characters, and begin the sequence again, writes some sequence, then
> stops... and so on. Even I noticed the repeat speed is a bit slow, compared to
> a keyboard key hold on.
>
> So... I began to investigates the causes and after two weeks of research,
> searchs on the web, I found the module affected and a solution.
>
> The module affected is ir-kbd-i2c.ko, this remote (rc5 protocol) uses this
> module as uinput (devinput) device, in resume as like an attatched keyboard.
> Resulting investigation in get noticed that this remote with rc5 protocol has
> 8hz of time frame when receiving the air gap code (rc5 procotol timing).
>
> Investigating the sources files in the kernel sources for try and fall, re-
> compiling the modules, get me to get noticed that the polling ir remote
> interval is 100ms which is 5hz, forcing this value to 125ms, re-compiling the
> module causes the remote to work normally as expecte, the response is like a
> real keyboard and the repeat sequence not only as speedy as a normal keyboard,
> but also hasn't got a pause in repetition. In resume, the problem is solved.
>
> Here is the patch:
>
> --- ir-kbd-i2c.original.c 2021-09-08 23:45:23.723210301 +0200
> +++ ir-kbd-i2c.hauppauge.patched.c 2021-09-10 03:55:28.003529072 +0200
> @@ -742,7 +742,7 @@
> return -ENOMEM;
>
> ir->c = client;
> - ir->polling_interval = DEFAULT_POLLING_INTERVAL;
> + ir->polling_interval = 125;
> i2c_set_clientdata(client, ir);
>
> switch(addr) {
>
> I am a experienced user, but not an experienced developer, also in
> editing/submitting bugs, I don't know if this is the right way to solve this,
> If the rest of brand remotes are affected for my solution, but for me, solved
> my problem in this particular case.
>
> I don't know where the value DEFAULT_POLLING_INTERVAL is get stablished or a
> way when detect a Hauppauge WinTV-HVR1110 DVB-T/Hybrid TV card to stablish
> 125ms instead of 100ms. As I said, I'm not an expert but experienced user.
>
> I don't know if this is the right package to post this bug. Thanks.
Thanks for the report!
This is IMHO not something which should handled with an entry point in
downstream in Debian, but rather going to report it upstream directly.
Can you do that?
Details on reporting:
https://www.kernel.org/doc/html/latest/admin-guide/bug-hunting.html
Best guess for reporting the issue you are seeing:
$ ./scripts/get_maintainer.pl ./drivers/media/i2c/ir-kbd-i2c.c
Mauro Carvalho Chehab (maintainer:MEDIA INPUT
INFRASTRUCTURE (V4L/DVB),commit_signer:1/1=100%)
Sean Young (commit_signer:1/1=100%)
Christophe JAILLET
(commit_signer:1/1=100%,authored:1/1=100%,added_lines:2/2=100%,removed_lines:2/2=100%)
linux-me...@vger.kernel.org (open list:MEDIA INPUT INFRASTRUCTURE (V4L/DVB))
linux-ker...@vger.kernel.org (open list)
Feel free to keep this bugreport downstream into the loop.
Regards,
Salvatore
Bug#994050: linux-image-5.10.0-8-amd64: Hauppauge WinTV-HVR1110 DVB-T/Hybrid bug 125 ms polling on ir-kbd-i2c.ko bad DEFAULT_POLLING_INTERVAL
Package: src:linux
Version: 5.10.46-4
Severity: important
Tags: patch
X-Debbugs-Cc: kini_calde...@hotmail.com
Although I have a very old pci (not express) Hauppauge WinTV-HVR1110
DVB-T/Hybrid TV card with a remote control, I am still using it because has
fully support and functionallity and it's hardware capable of play DVB-T HD
streams.
It has a very strange behaviour:
-One is it has a slow response when I push a key, has a delay, and sometimes
even no key response, nothing happens, as if never push a key.
-Other is when you hold a key, it start to begin the repeat key (characters
like numerical) appears in the test app (kwrite) then, has a pause, stops to
write characters, and begin the sequence again, writes some sequence, then
stops... and so on. Even I noticed the repeat speed is a bit slow, compared to
a keyboard key hold on.
So... I began to investigates the causes and after two weeks of research,
searchs on the web, I found the module affected and a solution.
The module affected is ir-kbd-i2c.ko, this remote (rc5 protocol) uses this
module as uinput (devinput) device, in resume as like an attatched keyboard.
Resulting investigation in get noticed that this remote with rc5 protocol has
8hz of time frame when receiving the air gap code (rc5 procotol timing).
Investigating the sources files in the kernel sources for try and fall, re-
compiling the modules, get me to get noticed that the polling ir remote
interval is 100ms which is 5hz, forcing this value to 125ms, re-compiling the
module causes the remote to work normally as expecte, the response is like a
real keyboard and the repeat sequence not only as speedy as a normal keyboard,
but also hasn't got a pause in repetition. In resume, the problem is solved.
Here is the patch:
--- ir-kbd-i2c.original.c 2021-09-08 23:45:23.723210301 +0200
+++ ir-kbd-i2c.hauppauge.patched.c 2021-09-10 03:55:28.003529072 +0200
@@ -742,7 +742,7 @@
return -ENOMEM;
ir->c = client;
- ir->polling_interval = DEFAULT_POLLING_INTERVAL;
+ ir->polling_interval = 125;
i2c_set_clientdata(client, ir);
switch(addr) {
I am a experienced user, but not an experienced developer, also in
editing/submitting bugs, I don't know if this is the right way to solve this,
If the rest of brand remotes are affected for my solution, but for me, solved
my problem in this particular case.
I don't know where the value DEFAULT_POLLING_INTERVAL is get stablished or a
way when detect a Hauppauge WinTV-HVR1110 DVB-T/Hybrid TV card to stablish
125ms instead of 100ms. As I said, I'm not an expert but experienced user.
I don't know if this is the right package to post this bug. Thanks.
-- Package-specific info:
** Version:
Linux version 5.10.0-8-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP
Debian 5.10.46-4 (2021-08-03)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64
root=UUID=0aa74469-7d27-4605-b6a8-9331ba5f3c26 ro quiet
** Tainted: OE (12288)
* externally-built ("out-of-tree") module was loaded
* unsigned module was loaded
** Kernel log:
[ 15.205051] saa7134: i2c eeprom e0: 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
[ 15.205052] saa7134: i2c eeprom f0: 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00
[ 15.205091] tveeprom: Hauppauge model 67019, rev B4B4, serial# 4030267784
[ 15.205093] tveeprom: MAC address is 00:0d:fe:39:01:88
[ 15.205094] tveeprom: tuner model is Philips 8275A (idx 114, type 4)
[ 15.205096] tveeprom: TV standards PAL(B/G) NTSC(M) PAL(I) SECAM(L/L')
PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
[ 15.205097] tveeprom: audio processor is SAA7131 (idx 41)
[ 15.205098] tveeprom: decoder processor is SAA7131 (idx 35)
[ 15.205099] tveeprom: has radio, has IR receiver, has IR transmitter
[ 15.205100] saa7134: saa7133[0]: hauppauge eeprom: model=67019
[ 15.237132] intel_powerclamp: No package C-state available
[ 15.305460] intel_powerclamp: No package C-state available
[ 15.408789] tuner: 8-004b: Tuner -1 found with type(s) Radio TV.
[ 15.524772] tda829x 8-004b: setting tuner address to 61
[ 15.659862] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC1200:
line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
[ 15.659867] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0
(0x0/0x0/0x0/0x0/0x0)
[ 15.659870] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1
(0x1b/0x0/0x0/0x0/0x0)
[ 15.659871] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[ 15.659873] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x11/0x1e
[ 15.659875] snd_hda_codec_realtek hdaudioC0D0:inputs:
[ 15.659877] snd_hda_codec_realtek hdaudioC0D0: Front Mic=0x19
[ 15.659880] snd_hda_codec_realtek hdaudioC0D0: Rear Mic=0x18
[ 15.659882] snd_hda_codec_realtek hdaudioC0D0: Line=0x1a
[ 15.700783] tda829x 8-004b: type set to tda8290+75a
[ 15.728552] input: HDA Digital PCBeep as
