All of lore.kernel.org
 help / color / mirror / Atom feed
From: Octavian Purdila <octavian.purdila@intel.com>
To: Johan Hovold <johan@kernel.org>
Cc: Lee Jones <lee.jones@linaro.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mfd: dln2: add suspend/resume functionality
Date: Mon, 8 Dec 2014 18:14:19 +0200	[thread overview]
Message-ID: <CAE1zotJPkTsvwqYEsfHHrdgdBW+03M20nqGzUL8bQXBfn70tBg@mail.gmail.com> (raw)
In-Reply-To: <20141208105732.GA14346@localhost>

On Mon, Dec 8, 2014 at 12:57 PM, Johan Hovold <johan@kernel.org> wrote:
> On Fri, Dec 05, 2014 at 03:05:45PM +0200, Octavian Purdila wrote:
>> On Fri, Dec 5, 2014 at 2:06 PM, Johan Hovold <johan@kernel.org> wrote:
>> > On Fri, Dec 05, 2014 at 01:51:17PM +0200, Octavian Purdila wrote:
>> >> On Fri, Dec 5, 2014 at 12:17 PM, Johan Hovold <johan@kernel.org> wrote:
>
>> >> > And surely you need to resubmit the read urbs in resume, or you will
>> >> > never receive any more data.
>> >> >
>> >> > How did you test this patch?
>> >> >
>> >>
>> >> The resume cb is not called in my setup (kvm), only reset_resume.
>> >
>> > Please make sure to test your patches on proper hardware.
>>
>> It was tested with the proper hardware, I was just testing it in the
>> setup we use, which is kvm with USB pass through.
>
> I was referring to your kvm setup.
>

I see the same behavior (reset_resume called) when testing on bare
bone hardware. BTW, KVM allows me to test more thoroughly, as I can
use custom SSDT tables required by i2c devices to find their IRQs.

      reply	other threads:[~2014-12-08 16:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27 11:57 [PATCH] mfd: dln2: add suspend/resume functionality Octavian Purdila
2014-12-05 10:17 ` Johan Hovold
2014-12-05 11:51   ` Octavian Purdila
2014-12-05 12:06     ` Johan Hovold
2014-12-05 13:05       ` Octavian Purdila
2014-12-08 10:57         ` Johan Hovold
2014-12-08 16:14           ` Octavian Purdila [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=CAE1zotJPkTsvwqYEsfHHrdgdBW+03M20nqGzUL8bQXBfn70tBg@mail.gmail.com \
    --to=octavian.purdila@intel.com \
    --cc=johan@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.