Re: [BUG] atomisp_ov2680 not initializing correctly

> Maybe we need start over, i.e. find a (presumable old) kernel with > driver _and_ corresponding firmware _and_ hardware it supports to > start > with... You can do that with Intel aero and then in theory port the relevant headers into the updated driver. I've actually been closely comparing

Re: [BUG] atomisp_ov2680 not initializing correctly

On Sat, 2017-12-30 at 20:57 +, Alan Cox wrote: > On Tue, 19 Dec 2017 22:37:01 +0200 > Andy Shevchenko 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 > > > >

Re: [BUG] atomisp_ov2680 not initializing correctly

On Sat, 2017-12-30 at 21:10 +, Alan Cox wrote: > > 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

Re: [BUG] atomisp_ov2680 not initializing correctly

On Tue, 2018-01-02 at 18:31 +, Alan Cox wrote: > > Patch 0003-atomisp_gmin_platform-tweak-to-drive-axp288.patch gives a > > little confusion. > > The PMIC driver should work via ACPI OpRegion macro (and should be > > enabled in kernel configuration). That's how it supposed to work. > > The

Re: [BUG] atomisp_ov2680 not initializing correctly

> Patch 0003-atomisp_gmin_platform-tweak-to-drive-axp288.patch gives a > little confusion. > The PMIC driver should work via ACPI OpRegion macro (and should be > enabled in kernel configuration). That's how it supposed to work. > The patch seems redundant. I am fairly sure it is meant to work

Re: [BUG] atomisp_ov2680 not initializing correctly

On Sun, Dec 31, 2017 at 5:19 PM, Kristian Beilke wrote: > On 12/28/2017 05:03 PM, 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: On Thu, 2017-12-21 at 13:54 +0100, Kristian Beilke wrote:

Re: [BUG] atomisp_ov2680 not initializing correctly

On 12/28/2017 05:03 PM, 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: >>> On Thu, 2017-12-21 at 13:54 +0100, Kristian Beilke wrote: On Tue, Dec 19, 2017 at 10:37:01PM +0200, Andy Shevchenko wrote: > On

Re: [BUG] atomisp_ov2680 not initializing correctly

> 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

Re: [BUG] atomisp_ov2680 not initializing correctly

On Tue, 19 Dec 2017 22:37:01 +0200 Andy Shevchenko 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

Re: [BUG] atomisp_ov2680 not initializing correctly

+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

Re: [BUG] atomisp_ov2680 not initializing correctly

On Sat, 2017-12-23 at 01:31 +0100, Kristian Beilke wrote: > On 12/21/2017 03:23 PM, Andy Shevchenko wrote: > > On Thu, 2017-12-21 at 13:54 +0100, Kristian Beilke wrote: > > > On Tue, Dec 19, 2017 at 10:37:01PM +0200, Andy Shevchenko wrote: > > > > On Tue, 2017-12-19 at 14:00 +0200, Sakari Ailus

Re: [BUG] atomisp_ov2680 not initializing correctly

On 12/21/2017 03:23 PM, Andy Shevchenko wrote: > On Thu, 2017-12-21 at 13:54 +0100, Kristian Beilke wrote: >> On Tue, Dec 19, 2017 at 10:37:01PM +0200, Andy Shevchenko wrote: >>> On Tue, 2017-12-19 at 14:00 +0200, Sakari Ailus wrote: Cc Alan and Andy. On Sat, Dec 16, 2017 at

Re: [BUG] atomisp_ov2680 not initializing correctly

On Thu, 2017-12-21 at 13:54 +0100, Kristian Beilke wrote: > On Tue, Dec 19, 2017 at 10:37:01PM +0200, Andy Shevchenko 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

Re: [BUG] atomisp_ov2680 not initializing correctly

On Tue, Dec 19, 2017 at 10:37:01PM +0200, Andy Shevchenko 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

Re: [BUG] atomisp_ov2680 not initializing correctly

On 12/19/2017 09:37 PM, Andy Shevchenko 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

Re: [BUG] atomisp_ov2680 not initializing correctly

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.

Re: [BUG] atomisp_ov2680 not initializing correctly

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: >

[BUG] atomisp_ov2680 not initializing correctly

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: [ 21.469907] ov2680: module is from the staging directory, the quality is unknown, you have