From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: rrs@researchut.com, linux-iio <linux-iio@vger.kernel.org>
Subject: Re: sensor-hub: Move the memset to sensor_hub_get_feature()
Date: Fri, 30 Dec 2016 08:50:10 -0800 [thread overview]
Message-ID: <1483116610.27585.51.camel@linux.intel.com> (raw)
In-Reply-To: <1483094837.11693.3.camel@researchut.com>
On Fri, 2016-12-30 at 16:17 +0530, Ritesh Raj Sarraf wrote:
> Hello Srini,
>
> On Thu, 2016-12-29 at 23:01 +0530, Ritesh Raj Sarraf wrote:
> >
> > On Thu, 2016-12-29 at 09:22 -0800, Srinivas Pandruvada wrote:
> > >
> > > >
> > > > If you need more information, please tell me.
> > > I tried on couple of systems with the patch. It seems to fix the
> > > issue.
> > > It is possible some low level power related changes have impacted
> > > this.
> > > Can you do bisect? I suggest just try 4.9-rc1. I think it will
> > > not work
> > > there probably.
> > Okay. Let me do a bisect on it. I'll ping back on this thread soon.
> Since yesterday's attempts, I haven't been able to reproduce the bug
> again, so
> far. Apart from re-building the kernel, I have also blacklisted the
> particular
> USB device from power savings (based on your hint). I don't know if
> disabling
> the power savings for that USB device is the cause for not seeing the
> issue, but
> so far, the device seems to report data.
>
> Do you think power savings mode can impact these devices ? I know of
> USB plugged
> keyboard/mice to generally break, when enabling power savings mode.
> But I had
> hoped that in-built USB devices were immune to it.
>
This is possible. If your remove from blacklist does it still work? May
be rebuild of kernel fixed this:-)
Thanks,
Srinivas
> Thanks,
> Ritesh
>
next prev parent reply other threads:[~2016-12-30 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-28 11:38 sensor-hub: Move the memset to sensor_hub_get_feature() Ritesh Raj Sarraf
2016-12-28 13:23 ` Ritesh Raj Sarraf
2016-12-28 16:48 ` Srinivas Pandruvada
2016-12-28 17:24 ` Ritesh Raj Sarraf
2016-12-28 17:37 ` Ritesh Raj Sarraf
2016-12-28 17:53 ` Ritesh Raj Sarraf
2016-12-29 17:22 ` Srinivas Pandruvada
2016-12-29 17:31 ` Ritesh Raj Sarraf
2016-12-30 10:47 ` Ritesh Raj Sarraf
2016-12-30 16:50 ` Srinivas Pandruvada [this message]
2016-12-31 12:55 ` Ritesh Raj Sarraf
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=1483116610.27585.51.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=linux-iio@vger.kernel.org \
--cc=rrs@researchut.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 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.