From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Kristian Beilke <beilke@posteo.de>,
Sakari Ailus <sakari.ailus@iki.fi>,
linux-media@vger.kernel.org, alan@linux.intel.com
Subject: Re: [BUG] atomisp_ov2680 not initializing correctly
Date: Sat, 30 Dec 2017 21:10:25 +0000 [thread overview]
Message-ID: <20171230211025.7aeaafcd@alans-desktop> (raw)
In-Reply-To: <1514476996.7000.437.camel@linux.intel.com>
> AFAIR Alan has CHT hardware he is developing / testing on.
I have a loaned board from the company Vincent (who did the intial
patches) works for. At the moment it's loading firmware, finding cameras
doing power management but not transferring images.
Unfortunately because of the design of the driver and firmware at the
moment we are reduced to analyzing all the structs by hand between
multiple different driver releases, and playing games to try and find out
why various things are not matching up (assuming the firmware we have
will actually work with the Windows tablet in question in the first
place).
It's nasty because there are complex structs shared between the firmware
and the OS, and in at least one spot the supposedly 'pristine' CHT driver
that was used for the merge we now know could never have worked because
it mismatched its own firmware !
On BYT I can't currently do much as my latest Intel Android tablet has
died and it's getting hard to find more because I guess the rest of those
made have also died.
> > [ 21.120554] rt5645 i2c-10EC5645:00: i2c-10EC5645:00 supply avdd not
> > found, using dummy regulator
> > [ 21.120587] rt5645 i2c-10EC5645:00: i2c-10EC5645:00 supply cpvdd
> > not
> > found, using dummy regulator
It couldn't figure out how to power managed some of the components.
> > [ 21.145141] intel_sst_acpi 808622A8:00: LPE base: 0x91400000
> > size:0x200000
> > [ 21.145146] intel_sst_acpi 808622A8:00: IRAM base: 0x914c0000
> > [ 21.145241] intel_sst_acpi 808622A8:00: DRAM base: 0x91500000
> > [ 21.145250] intel_sst_acpi 808622A8:00: SHIM base: 0x91540000
> > [ 21.145262] intel_sst_acpi 808622A8:00: Mailbox base: 0x91544000
> > [ 21.145269] intel_sst_acpi 808622A8:00: DDR base: 0x20000000
> > [ 21.145403] intel_sst_acpi 808622A8:00: Got drv data max stream 25
> > [ 21.892310] atomisp-isp2 0000:00:03.0: Refused to change power
> > state,
> > currently in D3
> > [ 21.904537] OVTI2680:00:
> > ov2680_s_parm:run_mode :2000
> > [ 21.919743] atomisp-isp2 0000:00:03.0: Refused to change power
> > state,
> > currently in D3
> > [ 21.930399] OVTI2680:00:
> > ov2680_s_parm:run_mode :2000
> > [ 21.956479] atomisp-isp2 0000:00:03.0: Refused to change power
> > state,
> > currently in D3
The D3 warnings you can ignore I think. PCI D3 is busted but the native
power management should be looking after it.
Alan
next prev parent reply other threads:[~2017-12-30 21:10 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 [this message]
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=20171230211025.7aeaafcd@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).