Re: atomisp kernel driver(s)

[Patrik Gfeller <patrik.gfeller@gmail.com>]

On 24.04.20 10:52, Patrik Gfeller wrote:
>
> On 22.04.20 21:13, Mauro Carvalho Chehab wrote:
>> Em Wed, 22 Apr 2020 19:56:56 +0200
>> Patrik Gfeller <patrik.gfeller@gmail.com> escreveu:
>>
>>> On 20.04.20 22:47, Mauro Carvalho Chehab wrote:
>>>> Em Mon, 20 Apr 2020 20:27:25 +0200
>>>> Patrik Gfeller <patrik.gfeller@gmail.com> escreveu:
>>>>> Me again ... sorry to ask such a basic question, but I can't get your
>>>>> modified source code. I get the following error:
>>>>>      > git clone https://git.linuxtv.org/mchehab/experimental.git/
>>>>> Cloning into 'experimental'...
>>>>> warning: adding alternate object store:
>>>>> https://git.linuxtv.org/git/linux.git/
>>>>> warning: adding alternate object store:
>>>>> https://git.linuxtv.org/git/media_tree.git/
>>>>> warning: adding alternate object store:
>>>>> https://git.linuxtv.org/git/linux.git/
>>>>> error: Unable to find fc8670d1f72b746ff3a5fe441f1fca4c4dba0e6f under
>>>>> https://git.linuxtv.org/mchehab/experimental.git
>>>>> Cannot obtain needed object fc8670d1f72b746ff3a5fe441f1fca4c4dba0e6f
>>>>> while processing commit 6d80bfc14608f4bb5514b79721d30b486f50c987.
>>>>> error: fetch failed.
>>>>>
>>>>> Do I use the wrong command?
>>>> Better to use git:// url:
>>>>
>>>>     git clone git://git.linuxtv.org/mchehab/experimental.git/
>>> I was able to download and compile the code. I installed the kernel and
>>> tried to boot; unfortunately it hangs with the message "Loading initial
>>> ramdisk ..." - after I start the old kernel I check kern.log and syslog
>>> - but I do not see entries from the failed boot attempt. I'll read into
>>> the topic and try around. This will take some time ... so there will be
>>> a dealy, but it's not that I do not care or lacking  interest, I just
>>> first have to sort this out.
>> Well, try to build it first without the atomisp driver. This would allow
>> you to see what's going on.
>
> I was able to solve the problem I had with the ramdisk - I had to 
> strip the kernel modules, probably the ramdisk file was too big.
>
> It is possible to boot with the atomisp driver, but I can not see the 
> camera yet - but maybe that's due to missing firmware, as there were 
> warnings when I installed the kernel that firmware files are missing.
>
> The following I found in dmesg:
>
> [    9.331011] kernel: atomisp_ov2680: module is from the staging 
> directory, the quality is unknown, you have been warned.
> [    9.402456] kernel: ov2680 i2c-OVTI2680:00: gmin: initializing 
> atomisp module subdev data.PMIC ID 1
> [    9.421113] kernel: acpi OVTI2680:00: Failed to find gmin variable 
> OVTI2680:00_CamClk
> [    9.433478] kernel: acpi OVTI2680:00: Failed to find gmin variable 
> OVTI2680:00_ClkSrc
> [    9.443146] kernel: acpi OVTI2680:00: Failed to find gmin variable 
> OVTI2680:00_CsiPort
> [    9.456677] kernel: acpi OVTI2680:00: Failed to find gmin variable 
> OVTI2680:00_CsiLanes
> [    9.479411] kernel: ov2680 i2c-OVTI2680:00: supply V1P8SX not 
> found, using dummy regulator
> [    ...
> [    9.510282] kernel: ov2680 i2c-OVTI2680:00: supply V2P8SX not 
> found, using dummy regulator
> [    ...
> [    9.532284] kernel: ov2680 i2c-OVTI2680:00: supply V1P2A not found, 
> using dummy regulator
> [    9.536200] kernel: ov2680 i2c-OVTI2680:00: supply VPROG4B not 
> found, using dummy regulator
> [   ...'
> [    9.592064] kernel: ov2680 i2c-OVTI2680:00: unable to set PMC rate 1
> [    9.623628] kernel: ov2680 i2c-OVTI2680:00: camera pdata: port: 0 
> lanes: 1 order: 00000002
> [    9.628258] kernel: ov2680 i2c-OVTI2680:00: sensor_revision id = 
> 0x2680, rev= 0
> [    9.636582] kernel: ov2680 i2c-OVTI2680:00: register atomisp i2c 
> module type 1
>
> The first signs of live :-) ... I'll try to find the firmware files to 
> see if it makes a difference.

May be of interest as well:

$ i2cdetect -l
i2c-3    unknown       Synopsys DesignWare I2C adapter     N/A
i2c-10    unknown       i915 gmbus dpc                      N/A
i2c-1    unknown       Synopsys DesignWare I2C adapter     N/A
i2c-8    unknown       i915 gmbus vga                      N/A
i2c-6    unknown       Synopsys DesignWare I2C adapter     N/A
i2c-13    unknown       AUX D/port D                        N/A
i2c-4    unknown       Synopsys DesignWare I2C adapter     N/A
i2c-11    unknown       i915 gmbus dpb                      N/A
i2c-2    unknown       Synopsys DesignWare I2C adapter     N/A
i2c-0    unknown       Synopsys DesignWare I2C adapter     N/A
i2c-9    unknown       i915 gmbus panel                    N/A
i2c-7    unknown       i915 gmbus ssc                      N/A
i2c-5    unknown       Synopsys DesignWare I2C adapter     N/A
i2c-12    unknown       i915 gmbus dpd                      N/A

>
>> Thanks,
>> Mauro
>
> kind regards,
>
> Patrik
>