linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: JP <jp@jpvw.nl>
To: Sean Young <sean@mess.org>
Cc: James Hutchinson <jahutchinson99@googlemail.com>,
	Antti Palosaari <crope@iki.fi>,
	linux-media@vger.kernel.org,
	Thomas Hollstegge <thomas.hollstegge@gmail.com>
Subject: Re: MyGica T230 dvb-t2 data corruption since commit 5fa8815
Date: Tue, 20 Aug 2019 21:25:18 +0200	[thread overview]
Message-ID: <3ee999e1-69b9-a384-46f5-67a2edc6614b@jpvw.nl> (raw)
In-Reply-To: <20190818102910.djeer6mxyyice253@gofer.mess.org>

Hoi Sean,

On 8/18/19 12:29 PM, Sean Young wrote:
> Hi JP, James,
>
> On Tue, Aug 13, 2019 at 03:46:37PM +0200, JP wrote:
>> Thanks James, my tests on both DVB-T and DVB-C all went OK.
>>
>> So, with the t230 driver in cxusb broken for one hw version of
>> the device and both hw versions now working fine in dvbsky &
>> the driver in cxusb does not crash itself anymore (did you test
>> that, James?) & everybody agrees I think this move to dvbsky
>> should be done.
> So I think the commmit message should say what the two hardware
> revisions are and what the FX2 FIFO issue is exactly.
There are no real different hw versions. My mistake.
There are simply some receiver units that needed the
FIFO fix, and some that did not. Most did not, and some
(maybe most or all) of them suffered like the 2 units
James has.

The issue was that after lock, the TS FIFO sometimes
got overrun and caused a TS error. With commit 5fa8815,
the FIF0 was resync'd after each lock. While this fixed the
driver for some units, it broke the driver for others.

> Would you be able to provide some words for the commit message
> which says what the issue with the existing driver (FX2 FIFO,
> anything else), what hardware revisions were tested (maybe what
> they look like) and what was exactly tested (and for whole long).
move Mygica T230 driver from cxusb to dvbsky

Fixes (kernel NULL pointer dereference) crash of the cxusb
driver when unit is unplugged live from it's USB port.
Adds module option to disable the RC.
Fixes buggy 'resync FIF0 after lock' streaming fix that broke
the driver for most receiver units.

Tested by patch author. DVB-T/T2/C scan and stream A/V
and data 24/7 without any problems on a production machine
for several weeks now.

Tested-by: James Hutchinson <jahutchinson99@googlemail.com>
"I've been running for a couple of weeks now"
"Everything has been working perfectly - the checksum errors when
scanning muxes have gone, and streaming has been working nicely."

> Thanks
>
> Sean
Thank you
Jan Pieter

>
>
>> Sean: some hunks from the 'remove from cxusb' patch won't
>> apply to linux-5.3 , because of the recent addition of the analogue
>> driver code to cxusb. So I now have 2 different 'remove from
>> cxusb'  patches. How do I proceed with that?
>>
>> [one more remark below]
>>
>> On 8/2/19 2:00 PM, James Hutchinson wrote:
>>> Hi Jan,
>>>
>>> I've been running for a couple of weeks now with your two patches applied:
>>>
>>> 1) dvbsky: add MyGica T230
>>> 2) remove t230 from cxusb
>>>
>>> Everything has been working perfectly - the checksum errors when
>>> scanning muxes have gone, and streaming has been working nicely.
>>>
>>> Tested-by: James Hutchinson <jahutchinson99@googlemail.com>
>>>
>>> Regards,
>>> James
>>>
>>> On Fri, 19 Jul 2019 at 19:35, Jan Pieter van Woerkom <jp@jpvw.nl> wrote:
>>>> dvbsky: add MyGica T230.
>>>> Moved from cxusb driver as that driver can't handle FX2 FIFO issue.
>>>>
>>>> Signed-off-by: Jan Pieter van Woerkom <jp@jpvw.nl>
>>>> ---
>>>> diff -ru a/drivers/media/usb/dvb-usb-v2/dvbsky.c b/drivers/media/usb/dvb-usb-v2/dvbsky.c
>>>> --- a/drivers/media/usb/dvb-usb-v2/dvbsky.c     2019-07-08 00:41:56.000000000 +0200
>>>> +++ b/drivers/media/usb/dvb-usb-v2/dvbsky.c     2019-07-19 17:50:54.671341146 +0200
>>>> @@ -561,11 +561,18 @@
>>>>
>>>>           /* attach tuner */
>>>>           si2157_config.fe = adap->fe[0];
>>>> -       si2157_config.if_port = 0;
>>>> -
>>>> -       state->i2c_client_tuner = dvb_module_probe("si2157", "si2141",
>>>> +       if (le16_to_cpu(d->udev->descriptor.idProduct) == USB_PID_MYGICA_T230) {
>>>> +               si2157_config.if_port = 1;
>>>> +               state->i2c_client_tuner = dvb_module_probe("si2157", NULL,
>>>> +                                                  i2c_adapter,
>>>> +                                                  0x60, &si2157_config);
>>>> +       }
>>>> +       else {
>> Coding style: those last 2 lines should be:
>>          } else {
>>>> +               si2157_config.if_port = 0;
>>>> +               state->i2c_client_tuner = dvb_module_probe("si2157", "si2141",
>>>>                                                      i2c_adapter,
>>>>                                                      0x60, &si2157_config);
>>>> +       }
>>>>           if (!state->i2c_client_tuner) {
>>>>                   dvb_module_release(state->i2c_client_demod);
>>>>                   return -ENODEV;
>>>> @@ -787,6 +794,9 @@
>>>>           { DVB_USB_DEVICE(USB_VID_TERRATEC, USB_PID_TERRATEC_CINERGY_S2_R4,
>>>>                   &dvbsky_s960_props, "Terratec Cinergy S2 Rev.4",
>>>>                   RC_MAP_DVBSKY) },
>>>> +       { DVB_USB_DEVICE(USB_VID_CONEXANT, USB_PID_MYGICA_T230,
>>>> +               &mygica_t230c_props, "MyGica Mini DVB-T2 USB Stick T230",
>>>> +               RC_MAP_TOTAL_MEDIA_IN_HAND_02) },
>>>>           { DVB_USB_DEVICE(USB_VID_CONEXANT, USB_PID_MYGICA_T230C,
>>>>                   &mygica_t230c_props, "MyGica Mini DVB-T2 USB Stick T230C",
>>>>                   RC_MAP_TOTAL_MEDIA_IN_HAND_02) },
>> Cheers,
>> Jan Pieter.


      reply	other threads:[~2019-08-20 19:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-17  7:44 MyGica T230 dvb-t2 data corruption since commit 5fa8815 James Hutchinson
2019-07-17 12:21 ` JP
2019-07-17 21:22 ` Thomas Hollstegge
2019-07-19 18:35 ` Jan Pieter van Woerkom
2019-07-21 18:29   ` Sean Young
2019-07-21 22:03     ` JP
     [not found]       ` <CAD+OKUre40kQiucuryJC0uYrvBSqL5M=pAkmi7QxgOoKUWt0bg@mail.gmail.com>
     [not found]         ` <70cb09ed-1ae4-6626-643d-c9e1c9ae47c6@jpvw.nl>
     [not found]           ` <CAD+OKUr-f_a8dcPVp24d4wPhRAE80tf10_kt5s3_WvVmfWu9JQ@mail.gmail.com>
2019-07-22 16:22             ` Jan Pieter van Woerkom
2019-07-23 16:02               ` James Hutchinson
2019-08-02 11:58                 ` James Hutchinson
2019-08-02 12:00   ` James Hutchinson
2019-08-13 13:46     ` JP
2019-08-15 10:14       ` Sean Young
2019-08-15 16:34         ` [PATCH 0/2] media: dvb-usb: move T230 to dvbsky Jan Pieter van Woerkom
2019-08-15 16:37           ` [PATCH 1/2] " Jan Pieter van Woerkom
2019-08-15 16:39           ` [PATCH 2a/2] " Jan Pieter van Woerkom
2019-08-15 16:41           ` [PATCH 2b/2] " Jan Pieter van Woerkom
2019-08-18 10:29       ` MyGica T230 dvb-t2 data corruption since commit 5fa8815 Sean Young
2019-08-20 19:25         ` JP [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3ee999e1-69b9-a384-46f5-67a2edc6614b@jpvw.nl \
    --to=jp@jpvw.nl \
    --cc=crope@iki.fi \
    --cc=jahutchinson99@googlemail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sean@mess.org \
    --cc=thomas.hollstegge@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).