From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Atri Bhattacharya <badshah400@aim.com>,
linux-iio <linux-iio@vger.kernel.org>
Subject: Re: [RFC 0/4] Intel Integrated Sensor Hub Support (ISH)
Date: Sun, 05 Jun 2016 23:47:17 -0700 [thread overview]
Message-ID: <1465195637.16143.1.camel@linux.intel.com> (raw)
In-Reply-To: <1464923314.3200.3.camel@aim.com>
Hi,
On Fri, 2016-06-03 at 05:08 +0200, Atri Bhattacharya wrote:
> On Thu, 2016-06-02 at 13:00 -0700, Srinivas Pandruvada wrote:
> >
> > I see. Can you add the following change and try?
> > diff --git a/drivers/hid/intel-ish-hid/ipc/pci-ish.c
> > b/drivers/hid/intel-ish-hid/ipc/pci-ish.c
> > index e4d00d2..f241e1f 100644
> > --- a/drivers/hid/intel-ish-hid/ipc/pci-ish.c
> > +++ b/drivers/hid/intel-ish-hid/ipc/pci-ish.c
> > @@ -199,6 +199,7 @@ static int ish_resume(struct device *device)
> > struct ishtp_device *dev = pci_get_drvdata(pdev);
> >
> > disable_irq_wake(pdev->irq);
> > + ish_hw_start(dev);
> > ishtp_send_resume(dev);
> > dev->suspend_flag = 0;
> >
> >
> >
>
I have sent a full series of patches to address the issues you raised.
Can you give try, before I repost my RFC series?
Thanks,
Srinivas
> --
> Atri Bhattacharya
> Fri 3 Jun 05:01:36 CEST 2016
>
> Sent from openSUSE Tumbleweed (20160531) (x86_64) on my laptop.
next prev parent reply other threads:[~2016-06-06 6:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 4:27 [RFC 0/4] Intel Integrated Sensor Hub Support (ISH) Srinivas Pandruvada
2016-05-31 4:27 ` [RFC 1/4] Documentation: hid: Intel ISH HID document Srinivas Pandruvada
2016-05-31 4:27 ` [RFC 2/4] hid: intel_ish-hid: ISH Transport layer Srinivas Pandruvada
2016-05-31 4:27 ` [RFC 3/4] hid: intel-ish-hid: ipc layer Srinivas Pandruvada
2016-05-31 4:27 ` [RFC 4/4] hid: intel-ish-hid: ISH HID client driver Srinivas Pandruvada
2016-06-01 13:36 ` [RFC 0/4] Intel Integrated Sensor Hub Support (ISH) Atri Bhattacharya
2016-06-02 3:27 ` Srinivas Pandruvada
2016-06-02 7:48 ` Atri Bhattacharya
2016-06-02 16:49 ` Srinivas Pandruvada
2016-06-02 19:42 ` Atri Bhattacharya
2016-06-02 20:00 ` Srinivas Pandruvada
2016-06-02 21:44 ` Pandruvada, Srinivas
2016-06-02 22:29 ` Atri Bhattacharya
2016-06-02 22:48 ` Srinivas Pandruvada
2016-06-02 22:57 ` Atri Bhattacharya
2016-06-02 23:13 ` Atri Bhattacharya
2016-06-03 2:50 ` Atri Bhattacharya
2016-06-03 4:01 ` Srinivas Pandruvada
2016-06-03 3:08 ` Atri Bhattacharya
2016-06-03 4:02 ` Srinivas Pandruvada
2016-06-06 6:47 ` Srinivas Pandruvada [this message]
2016-06-09 21:45 ` Grant Likely
2016-06-09 21:54 ` Srinivas Pandruvada
2016-06-10 9:44 ` Grant Likely
2016-06-10 13:55 ` Srinivas Pandruvada
2016-06-10 14:26 ` Bastien Nocera
2016-06-10 14:45 ` Srinivas Pandruvada
2016-06-10 15:04 ` Bastien Nocera
2016-06-10 15:23 ` Srinivas Pandruvada
2016-06-10 15:27 ` Bastien Nocera
2016-06-14 13:44 ` Grant Likely
2016-06-14 15:12 ` Bastien Nocera
2016-06-14 16:08 ` Grant Likely
2016-06-14 17:01 ` Bastien Nocera
2016-06-14 21:33 ` Grant Likely
2016-06-10 14:02 ` Grant Likely
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=1465195637.16143.1.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=badshah400@aim.com \
--cc=linux-iio@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;
as well as URLs for NNTP newsgroup(s).