From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
Cc: Sakari Ailus <sakari.ailus@iki.fi>,
Kristian Beilke <beilke@posteo.de>,
linux-media@vger.kernel.org, alan@linux.intel.com
Subject: Re: [BUG] atomisp_ov2680 not initializing correctly
Date: Thu, 04 Jan 2018 19:58:49 +0200 [thread overview]
Message-ID: <1515088729.7000.714.camel@linux.intel.com> (raw)
In-Reply-To: <20171230205712.6e744bb0@alans-desktop>
On Sat, 2017-12-30 at 20:57 +0000, Alan Cox wrote:
> On Tue, 19 Dec 2017 22:37:01 +0200
> Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> > On Tue, 2017-12-19 at 14:00 +0200, Sakari Ailus wrote:
> > > > I am trying to get the cameras in a Lenovo IdeaPad Miix 320
> > > > (Atom
> > > > x5-Z8350 BayTrail) to work. The front camera is an ov2680. With
> > > > kernel
> > > > 4.14.4 and 4.15rc3 I see the following dmesg output:
> >
> > It seems I forgot to send the rest of the patches I did while ago
> > against AtomISP code.
> >
> > It includes switch to normal DMI matching instead of the crap we
> > have
> > there right now.
>
> The current code expects to be booted on an Android (or ex Android)
> tablet. In which case the various values are buried in the EFI as
> you'd
> expect.
Yes, the logic is left untouched, the code has been cleaned up and allow
to use more natural DMI matching table.
> > WRT to the messages below it seems we have no platform data for that
> > device. It needs to be added.
>
> Or we need to learn how to parse the ACPI data - except that at least
> on
> some devices the ACPI data is at least half fictional so it's not
> clear
> what the Windows driver really does.
...if we have any specs inside how that ACPI table was being populated.
> > Version string: irci_stable_candrpv_0415_20150423_1753
> > SHA1: 548d26a9b5daedbeb59a46ea1da69757d92cd4d6 shisp_2400b0_v21.bin
>
> I'll send you a copy: (unfortunately for non Intel people I've not
> managed to get enough people to care about this to get permission to
> put
> the firmware in the public repository ... yet.....)
I've tried firmware with a version that matches the driver, still same
result. I got only "statistics" IRQs (0x20 by value)
$ head -z -n1 shisp_2400b0_v21.bin
irci_stable_candrpv_0415_20150521_0458
$ sha1sum shisp_2400b0_v21.bin
358d7cd31b2e35b6f812c5bdfc0bc28cc23ce674 shisp_2400b0_v21.bin
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2018-01-04 17:59 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
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 [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=1515088729.7000.714.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alan@linux.intel.com \
--cc=beilke@posteo.de \
--cc=gnomes@lxorguk.ukuu.org.uk \
--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).