From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Kristian Beilke <beilke@posteo.de>, Hans de Goede <hdegoede@redhat.com>
Cc: Sakari Ailus <sakari.ailus@iki.fi>,
linux-media@vger.kernel.org, alan@linux.intel.com
Subject: Re: [BUG] atomisp_ov2680 not initializing correctly
Date: Fri, 29 Dec 2017 21:38:12 +0200 [thread overview]
Message-ID: <1514576292.7000.558.camel@linux.intel.com> (raw)
In-Reply-To: <1514476996.7000.437.camel@linux.intel.com>
+Cc Hans.
On Thu, 2017-12-28 at 18:03 +0200, Andy Shevchenko wrote:
> On Sat, 2017-12-23 at 01:31 +0100, Kristian Beilke wrote:
> > On 12/21/2017 03:23 PM, Andy Shevchenko wrote:
I spend more time on investigating some additional stuff Sakari gave me, but no result so far.
So, the verbose debug output is here:
https://pastebin.com/RUV8gsUJ
Can anyone tell what's going on?
Note the idle state between 803s - 806s. I pressed Ctrl+C there since no expected IRQ came.
So, was it ever tested on Baytrail???
Who can debug this properly?
For now it's a quite waste of time. I doubt I want to do anything anymore
for this. Consider I'm in postponed state until there will be a *proven* way to test it.
Otherwise, I'm voting 10x times to remove this driver from upstream for good.
P.S. Happy New Year, everyone!
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-12-29 19:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 15:50 [BUG] atomisp_ov2680 not initializing correctly Kristian Beilke
2017-12-19 12:00 ` Sakari Ailus
2017-12-19 20:37 ` Andy Shevchenko
2017-12-20 7:13 ` Kristian Beilke
2017-12-21 12:54 ` Kristian Beilke
2017-12-21 14:23 ` Andy Shevchenko
2017-12-23 0:31 ` Kristian Beilke
2017-12-28 16:03 ` Andy Shevchenko
2017-12-29 19:38 ` Andy Shevchenko [this message]
2017-12-30 21:10 ` Alan Cox
2018-01-04 17:52 ` Andy Shevchenko
2018-01-17 13:52 ` Alan Cox
2017-12-31 15:19 ` Kristian Beilke
2018-01-01 12:42 ` Andy Shevchenko
2018-01-02 18:31 ` Alan Cox
2018-01-04 17:47 ` Andy Shevchenko
2017-12-30 20:57 ` Alan Cox
2018-01-04 17:58 ` Andy Shevchenko
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=1514576292.7000.558.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alan@linux.intel.com \
--cc=beilke@posteo.de \
--cc=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
/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).