From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
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: Sat, 30 Dec 2017 20:57:12 +0000 [thread overview]
Message-ID: <20171230205712.6e744bb0@alans-desktop> (raw)
In-Reply-To: <1513715821.7000.228.camel@linux.intel.com>
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:
> > Cc Alan and Andy.
> >
> > On Sat, Dec 16, 2017 at 04:50:04PM +0100, Kristian Beilke wrote:
> > > Dear all,
> > >
> > > 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.
The Windows devices seem to use a mix of ACPI, hardcoding and plain magic
in order to decide what hardware they have.
> 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.
For CHT and maybe some BYT the Windows devices also use ACPI for the power
management to drive the PMIC opregion and thus the PMIC power lines.
> In any case, I have no firmware to test BayTrail hardware I have (MRD7).
>
> The driver claims it needs:
>
> Firmware file: shisp_2400b0_v21.bin
> Version string: irci_stable_candrpv_0415_20150521_0458
>
> What I have is:
>
> 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.....)
Alan
next prev parent reply other threads:[~2017-12-30 20: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 [this message]
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=20171230205712.6e744bb0@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=alan@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=beilke@posteo.de \
--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).