linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Johannes Stezenbach <js@linuxtv.org>
Cc: Shuah Khan <shuahkh@osg.samsung.com>,
	Shuah Khan <shuah.kh@samsung.com>,
	linux-media@vger.kernel.org
Subject: Re: em28xx breaks after hibernate
Date: Fri, 26 Sep 2014 12:48:51 -0300	[thread overview]
Message-ID: <20140926124851.56a24d6b@recife.lan> (raw)
In-Reply-To: <20140926154227.GA22194@linuxtv.org>

Em Fri, 26 Sep 2014 17:42:27 +0200
Johannes Stezenbach <js@linuxtv.org> escreveu:

> On Fri, Sep 26, 2014 at 09:22:53AM -0600, Shuah Khan wrote:
> > > 
> > > [   20.212162] usb 1-1: reset high-speed USB device number 2 using ehci-pci
> > > [   20.503868] em2884 #0: Resuming extensions
> > > [   20.505275] em2884 #0: Resuming video extensionem2884 #0: Resuming DVB extension
> > > [   20.533513] drxk: status = 0x439130d9
> > > [   20.534282] drxk: detected a drx-3913k, spin A2, xtal 20.250 MHz
> > > [   23.008852] em2884 #0: writing to i2c device at 0x52 failed (error=-5)
> > > [   23.011408] drxk: i2c write error at addr 0x29
> > > [   23.013187] drxk: write_block: i2c write error at addr 0x8303b4
> > > [   23.015440] drxk: Error -5 while loading firmware
> > > [   23.017291] drxk: Error -5 on init_drxk
> > > [   23.018835] em2884 #0: fe0 resume 0
> > > 
> > > Any idea on this?
> > > 
> > 
> > Looks like this is what's happening:
> > during suspend:
> > 
> > drxk_sleep() gets called and marks state->m_drxk_state == DRXK_UNINITIALIZED
> > 
> > init_drxk() does download_microcode() and this step fails
> > because the conditions in which init_drxk() gets called
> > from drxk_attach() are different.
> > 
> > i2c isn't ready.
> > 
> > Is it possible for you to test this without power loss
> > on usb assuming this test run usb bus looses power?
> > 
> > If you could do the following tests and see if there is
> > a difference:
> > 
> > echo mem > /sys/power/state
> > vs
> > echo disk > /sys/power/state
> > 
> > If it is possible, with and without reset_resume hook.
> 
> My testing time is up for today, I'll look into it
> maybe tomorrow.

Ok.

> BTW, what about 3.17?  The patches in media_tree.git are for
> 3.18, right?  If so, and you have patches for 3.17 or
> 3.16-stable to test, let me know.

Yes, those patches are for 3.18. Don't remember if they were
tagged with c/c stable. If not, we'll need to rebase them to
-stable after being merged for 3.18-rc1.

Regards,
Mauro

      reply	other threads:[~2014-09-26 15:48 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25 12:53 em28xx breaks after hibernate Johannes Stezenbach
2014-09-25 13:45 ` Shuah Khan
2014-09-25 14:10   ` Mauro Carvalho Chehab
2014-09-25 15:07     ` Shuah Khan
2014-09-25 16:01   ` Johannes Stezenbach
2014-09-25 17:36     ` Johannes Stezenbach
2014-09-25 18:01       ` Shuah Khan
2014-09-25 17:40     ` Shuah Khan
2014-09-25 18:17       ` Johannes Stezenbach
2014-09-25 18:45         ` Shuah Khan
2014-09-25 19:03           ` Shuah Khan
2014-09-26  7:41             ` Johannes Stezenbach
2014-09-26  8:00           ` Johannes Stezenbach
2014-09-26  8:08             ` Johannes Stezenbach
2014-09-26 10:14               ` Mauro Carvalho Chehab
2014-09-26 11:07                 ` Johannes Stezenbach
2014-09-26 11:42                   ` Mauro Carvalho Chehab
2014-09-26 12:02                     ` Johannes Stezenbach
2014-09-26 12:11                       ` Mauro Carvalho Chehab
2014-09-26 12:03                     ` Mauro Carvalho Chehab
2014-09-26 12:27                       ` Johannes Stezenbach
2014-09-26 13:12                         ` Mauro Carvalho Chehab
2014-09-26 13:25                           ` Johannes Stezenbach
2014-09-26 14:25                             ` Shuah Khan
2014-09-26 14:25                             ` Johannes Stezenbach
2014-09-26 14:30                               ` Shuah Khan
2014-09-26 15:06                                 ` Johannes Stezenbach
2014-09-26 15:22                                   ` Johannes Stezenbach
2014-09-26 15:43                                     ` Mauro Carvalho Chehab
2014-09-28 10:55                                       ` Johannes Stezenbach
2014-09-28 11:12                                         ` Mauro Carvalho Chehab
2014-09-28 11:54                                           ` Johannes Stezenbach
2014-09-28 12:35                                             ` Mauro Carvalho Chehab
2014-09-28 12:57                                             ` Mauro Carvalho Chehab
2014-09-29  2:38                                             ` Mauro Carvalho Chehab
2014-09-26 15:22                                   ` Shuah Khan
2014-09-26 15:35                                     ` Mauro Carvalho Chehab
2014-09-26 15:40                                     ` Mauro Carvalho Chehab
2014-09-26 15:42                                     ` Johannes Stezenbach
2014-09-26 15:48                                       ` Mauro Carvalho Chehab [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=20140926124851.56a24d6b@recife.lan \
    --to=mchehab@osg.samsung.com \
    --cc=js@linuxtv.org \
    --cc=linux-media@vger.kernel.org \
    --cc=shuah.kh@samsung.com \
    --cc=shuahkh@osg.samsung.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).