public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Malcolm Priestley <tvboxspy@gmail.com>
To: Antti Palosaari <crope@iki.fi>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH 1/2] [BUG] dvb_usb_v2:  return the download ret in dvb_usb_download_firmware
Date: Thu, 14 Jun 2012 01:44:08 +0100	[thread overview]
Message-ID: <1339634648.3833.37.camel@Route3278> (raw)
In-Reply-To: <4FD9224F.7050809@iki.fi>

On Thu, 2012-06-14 at 02:29 +0300, Antti Palosaari wrote:
> Hi Malcolm,
> I was really surprised someone has had interest to test that stuff at 
> that phase as I did not even advertised it yet :) It is likely happen 
> next Monday or so as there is some issues I would like to check / solve.
> 
> 
> On 06/14/2012 01:24 AM, Malcolm Priestley wrote:
> > Hi antti
> >
> > There some issues with dvb_usb_v2 with the lmedm04 driver.
> >
> > The first being this patch, no return value from dvb_usb_download_firmware
> > causes system wide dead lock with COLD disconnect as system attempts to continue
> > to warm state.
> 
> Hmm, I did not understand what you mean. What I looked lmedm04 driver I 
> think it uses single USB ID (no cold + warm IDs). So it downloads 
> firmware and then reconnects itself from the USB bus?
> For that scenario you should "return RECONNECTS_USB;" from the driver 
> .download_firmware().
> 
If the device disconnects from the USB bus after the firmware download.

In most cases the device is already gone.

There is currently no way to insert RECONNECTS_USB into the return.


> I tested it using one non-public Cypress FX2 device - it was changing 
> USB ID after the FX download, but from the driver perspective it does 
> not matter. It is always new device if it reconnects USB.
> 

Have double checked that the thread is not continuing to write on the
old ID?

The zero condition will lead to dvb_usb_init.

> PS. as I looked that driver I saw many different firmwares. That is now 
> supported and you should use .get_firmware_name() (maybe you already did 
> it).
> 
Yes, I have supported this in the driver.




Regards


Malcolm




  reply	other threads:[~2012-06-14  0:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13 22:24 [PATCH 1/2] [BUG] dvb_usb_v2: return the download ret in dvb_usb_download_firmware Malcolm Priestley
2012-06-13 23:29 ` Antti Palosaari
2012-06-14  0:44   ` Malcolm Priestley [this message]
2012-06-14  1:15     ` Antti Palosaari
2012-06-14 20:31       ` Antti Palosaari
2012-06-14 21:33         ` Malcolm Priestley
2012-06-14 22:12           ` Antti Palosaari
2012-06-14 22:32             ` Malcolm Priestley
2012-06-14 23:14               ` Antti Palosaari
2012-06-14 23:20                 ` Malcolm Priestley

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=1339634648.3833.37.camel@Route3278 \
    --to=tvboxspy@gmail.com \
    --cc=crope@iki.fi \
    --cc=linux-media@vger.kernel.org \
    /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