From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sakari Ailus <sakari.ailus@iki.fi>, Kristian Beilke <beilke@posteo.de>
Cc: linux-media@vger.kernel.org, alan@linux.intel.com
Subject: Re: [BUG] atomisp_ov2680 not initializing correctly
Date: Tue, 19 Dec 2017 22:37:01 +0200 [thread overview]
Message-ID: <1513715821.7000.228.camel@linux.intel.com> (raw)
In-Reply-To: <20171219120020.w7byb7bv3hhzn2jb@valkosipuli.retiisi.org.uk>
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.
WRT to the messages below it seems we have no platform data for that
device. It needs to be added.
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
> > [ 21.469907] ov2680: module is from the staging directory, the
> > quality
> > is unknown, you have been warned.
> > [ 21.492774] ov2680 i2c-OVTI2680:00: gmin: initializing atomisp
> > module
> > subdev data.PMIC ID 1
> > [ 21.492891] acpi OVTI2680:00: Failed to find gmin variable
> > OVTI2680:00_CamClk
> > [ 21.492974] acpi OVTI2680:00: Failed to find gmin variable
> > OVTI2680:00_ClkSrc
> > [ 21.493090] acpi OVTI2680:00: Failed to find gmin variable
> > OVTI2680:00_CsiPort
> > [ 21.493209] acpi OVTI2680:00: Failed to find gmin variable
> > OVTI2680:00_CsiLanes
> > [ 21.493511] ov2680 i2c-OVTI2680:00: i2c-OVTI2680:00 supply V1P8SX
> > not
> > found, using dummy regulator
> > [ 21.493550] ov2680 i2c-OVTI2680:00: i2c-OVTI2680:00 supply V2P8SX
> > not
> > found, using dummy regulator
> > [ 21.493569] ov2680 i2c-OVTI2680:00: i2c-OVTI2680:00 supply V1P2A
> > not
> > found, using dummy regulator
> > [ 21.493585] ov2680 i2c-OVTI2680:00: i2c-OVTI2680:00 supply
> > VPROG4B
> > not found, using dummy regulator
> > [ 21.568134] ov2680 i2c-OVTI2680:00: camera pdata: port: 0 lanes:
> > 1
> > order: 00000002
> > [ 21.568257] ov2680 i2c-OVTI2680:00: read from offset 0x300a error
> > -121
> > [ 21.568265] ov2680 i2c-OVTI2680:00: sensor_id_high = 0xffff
> > [ 21.568269] ov2680 i2c-OVTI2680:00: ov2680_detect err s_config.
> > [ 21.568291] ov2680 i2c-OVTI2680:00: sensor power-gating failed
> >
> > Afterwards I do not get a camera device.
> >
> > Am I missing some firmware or dependency?
See above.
> > Can I somehow help to improve
> > the driver?
Yes, definitely, but first of all we need to find at least one device
and corresponding firmware where it actually works.
For me it doesn't generate any interrupt (after huge hacking to make
that firmware loaded and settings / platform data applied).
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-12-19 20:37 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 [this message]
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
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=1513715821.7000.228.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alan@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).