From: Patrik Gfeller <patrik.gfeller@gmail.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: linux-media@vger.kernel.org
Subject: Re: atomisp kernel driver(s)
Date: Fri, 24 Apr 2020 15:58:06 +0200 [thread overview]
Message-ID: <c18ae1e7-cade-7231-7d07-c5d83be1093a@gmail.com> (raw)
In-Reply-To: <682558b0-a2cf-9fe2-6e54-20462ecccb5d@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 11268 bytes --]
On 24.04.20 12:07, Patrik Gfeller wrote:
>
> On 24.04.20 11:10, Patrik Gfeller wrote:
>>
>> 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.
> I've added the missing firmware files and now I do not have warnings
> when I create the ramdisk. Unfortunately it makes no difference - the
> device does not work yet (dmesg looks the same).
>>>
>>> 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
As this seems to be related to acpi here the section of the acpidump
(full dump attached):
DSDT @ 0x0000000000000000
...
19950: 00 14 0C 5F 50 53 33 00 70 00 43 4B 43 33 14 0C ..._PS3.p.CKC3..
19960: 5F 50 53 30 00 70 01 43 4B 43 33 10 4F 4E 2F 03 _PS0.p.CKC3.ON/.
19970: 5F 53 42 5F 50 43 49 30 49 32 43 33 14 24 4D 45 _SB_PCI0I2C3.$ME
19980: 4D 42 01 5B 80 4D 52 47 4E 00 68 01 5B 81 0B 4D MB.[.MRGN.h.[..M
19990: 52 47 4E 01 44 41 54 41 08 70 44 41 54 41 60 A4 RGN.DATA.pDATA`.
199A0: 60 5B 84 33 43 4C 4B 34 00 00 00 14 0B 5F 53 54 `[.3CLK4....._ST
199B0: 41 00 A4 43 4B 43 34 14 10 5F 4F 4E 5F 00 70 01 A..CKC4.._ON_.p.
199C0: 43 4B 43 34 5B 22 0A 05 14 0D 5F 4F 46 46 00 70 CKC4["...._OFF.p
199D0: 0A 02 43 4B 43 34 5B 82 43 48 43 41 4D 31 08 5F ..CKC4[.CHCAM1._
199E0: 41 44 52 00 08 5F 48 49 44 0D 4F 56 54 49 32 36 ADR.._HID.OVTI26
199F0: 38 30 00 08 5F 43 49 44 0D 4F 56 54 49 32 36 38 80.._CID.OVTI268
19A00: 30 00 08 5F 53 55 42 0D 31 33 41 30 31 30 34 33 0.._SUB.13A01043
19A10: 00 08 5F 44 44 4E 0D 4F 56 32 36 38 30 00 08 5F .._DDN.OV2680.._
19A20: 55 49 44 01 08 5F 44 45 50 12 11 02 49 32 43 37 UID.._DEP...I2C7
19A30: 5E 5E 2E 49 32 43 37 50 4D 49 32 08 5F 50 52 30 ^^.I2C7PMI2._PR0
19A40: 12 0E 03 50 32 38 54 50 31 38 44 43 4C 4B 34 08 ...P28TP18DCLK4.
19A50: 50 4C 44 42 12 1A 01 11 17 0A 14 82 00 00 00 00 PLDB............
19A60: 00 00 00 61 0C 00 00 03 00 00 00 FF FF FF FF 14 ...a............
19A70: 0B 5F 50 4C 44 08 A4 50 4C 44 42 14 09 5F 53 54 ._PLD..PLDB.._ST
19A80: 41 00 A4 0A 0F 14 4C 05 5F 43 52 53 00 08 53 42 A.....L._CRS..SB
19A90: 55 46 11 4A 04 0A 46 8C 20 00 01 01 01 00 02 00 UF.J..F. .......
19AA0: 00 00 00 00 00 17 00 00 19 00 23 00 00 00 37 00 ..........#...7.
19AB0: 5C 5F 53 42 2E 47 50 4F 31 00 8E 1E 00 01 00 01 \_SB.GPO1.......
19AC0: 02 00 00 01 06 00 80 1A 06 00 36 00 5C 5F 53 42 ..........6.\_SB
19AD0: 2E 50 43 49 30 2E 49 32 43 33 00 79 00 A4 53 42 .PCI0.I2C3.y..SB
19AE0: 55 46 08 43 31 43 44 11 04 0B 20 02 14 4E 36 5F UF.C1CD... ..N6_
19AF0: 44 53 4D 04 A0 4C 09 93 68 11 13 0A 10 4F 6C 2F DSM..L..h....Ol/
19B00: DC 5B 04 1D 4F 97 B9 88 2A 68 60 A4 BE 70 12 4F .[..O...*h`..p.O
19B10: 07 12 0D 43 61 6D 49 64 00 0D 6F 76 32 36 38 30 ...CamId..ov2680
19B20: 00 0D 43 61 6D 54 79 70 65 00 0D 31 00 0D 43 73 ..CamType..1..Cs
19B30: 69 50 6F 72 74 00 0D 30 00 0D 43 73 69 4C 61 6E iPort..0..CsiLan
19B40: 65 73 00 0D 31 00 0D 43 73 69 46 6D 74 00 0D 31 es..1..CsiFmt..1
19B50: 35 00 0D 43 73 69 42 61 79 65 72 00 0D 30 00 0D 5..CsiBayer..0..
19B60: 43 61 6D 43 6C 6B 00 0D 31 00 0D 52 65 67 75 6C CamClk..1..Regul
19B70: 61 74 6F 72 31 70 38 76 00 0D 30 00 0D 52 65 67 ator1p8v..0..Reg
19B80: 75 6C 61 74 6F 72 32 70 38 76 00 0D 30 00 60 A4 ulator2p8v..0.`.
19B90: 60 A0 22 93 68 11 13 0A 10 6A A7 7B 37 90 F3 FF `.".h....j.{7...
19BA0: 4A AB 38 9B 1B F3 3A 30 15 A4 0D 4F 56 54 49 32 J.8...:0...OVTI2
19BB0: 36 38 30 00 A0 20 93 68 11 13 0A 10 AA AA 62 3C 680.. .h......b<
19BC0: E0 D8 1A 40 84 C3 FC 05 65 6F A2 8C A4 0D 4F 56 ...@....eo....OV
19BD0: 32 36 38 30 00 A0 22 93 68 11 13 0A 10 8F CE 2A 2680..".h......*
19BE0: 82 14 28 74 41 A5 6B 5F 02 9F E0 79 EE A4 0D 43 ..(tA.k_...y...C
19BF0: 49 46 46 32 31 39 32 00 A0 49 05 93 68 11 13 0A IFF2192..I..h...
19C00: 10 2A 51 59 29 8C 02 46 46 B7 3D 4D 1B 56 72 FA .*QY)..FF.=M.Vr.
19C10: D8 A0 34 93 42 44 49 44 0A 04 A0 15 93 46 42 49 ..4.BDID.....FBI
19C20: 44 0A 02 A4 0D 49 4E 54 45 4C 5F 46 46 52 44 00 D....INTEL_FFRD.
19C30: A0 15 93 46 42 49 44 0A 03 A4 0D 49 4E 54 45 4C ...FBID....INTEL
19C40: 5F 46 46 52 44 00 A4 0D 49 4E 54 45 4C 5F 52 56 _FFRD...INTEL_RV
19C50: 50 00 A0 1B 93 68 11 13 0A 10 42 B2 8A 91 7C C3 P....h....B...|.
19C60: 0A 45 9D 0F F4 7A B9 7C 3D EA A4 0B 01 01 A0 1B .E...z.|=.......
19C70: 93 68 11 13 0A 10 D8 7B 3B EA 9B E0 39 42 AD 6E .h.....{;...9B.n
19C80: ED 52 5F 3F 26 AB A4 0B 11 10 A0 19 93 68 11 13 .R_?&........h..
>>> [ 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.
There was probably also a problem as I did not unload intel_atomisp2_pm.
That is what lsmod reports now:
$ lsmod | grep atom
atomisp 790528 0
videobuf_vmalloc 16384 1 atomisp
videobuf_core 28672 2 atomisp,videobuf_vmalloc
punit_atom_debug 16384 0
snd_soc_sst_atom_hifi2_platform 110592 2 snd_intel_sst_core
snd_soc_core 253952 3
snd_soc_sst_atom_hifi2_platform,snd_soc_rt5645,snd_soc_sst_cht_bsw_rt5645
snd_pcm 114688 7
snd_compress,snd_hdmi_lpe_audio,snd_soc_sst_atom_hifi2_platform,snd_soc_core,snd_soc_rt5645,snd_soc_sst_cht_bsw_rt5645,snd_pcm_dmaengine
atomisp_ov2680 28672 0
videodev 237568 2 atomisp,atomisp_ov2680
snd 94208 15
snd_seq,snd_seq_device,snd_timer,snd_compress,snd_hdmi_lpe_audio,snd_soc_sst_atom_hifi2_platform,snd_soc_core,snd_pcm,snd_rawmidi
mc 53248 3 atomisp,videodev,atomisp_ov2680
But it looks as there are no devices for atomisp, or ov2680:
pgfeller@ASUS:~$ ls -l /sys/dev/block | grep atom
pgfeller@ASUS:~$ ls -l /sys/dev/block | grep 2680
pgfeller@ASUS:~$ ls -l /sys/dev/char | grep atom
pgfeller@ASUS:~$ ls -l /sys/dev/char | grep 2680
pgfeller@ASUS:~$
>>
>> 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
>>>
with kind regards,
Patrik
[-- Attachment #2: acpidump.txt.tar.gz --]
[-- Type: application/gzip, Size: 152589 bytes --]
next prev parent reply other threads:[~2020-04-24 13:58 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-18 14:39 atomisp kernel driver(s) Patrik Gfeller
2020-04-18 15:25 ` Mauro Carvalho Chehab
2020-04-18 15:26 ` Mauro Carvalho Chehab
2020-04-18 15:37 ` Patrik Gfeller
2020-04-19 23:31 ` Mauro Carvalho Chehab
2020-04-20 17:48 ` Patrik Gfeller
2020-04-20 18:27 ` Patrik Gfeller
2020-04-20 20:47 ` Mauro Carvalho Chehab
2020-04-22 17:56 ` Patrik Gfeller
2020-04-22 19:13 ` Mauro Carvalho Chehab
2020-04-24 8:52 ` Patrik Gfeller
2020-04-24 9:10 ` Patrik Gfeller
2020-04-24 10:07 ` Patrik Gfeller
2020-04-24 13:58 ` Patrik Gfeller [this message]
2020-04-25 11:22 ` Mauro Carvalho Chehab
2020-04-26 11:38 ` Patrik Gfeller
2020-04-26 16:50 ` Mauro Carvalho Chehab
2020-04-27 18:31 ` Patrik Gfeller
2020-04-27 21:50 ` Mauro Carvalho Chehab
2020-04-28 17:59 ` Patrik Gfeller
2020-04-28 23:13 ` Mauro Carvalho Chehab
2020-04-29 17:56 ` Patrik Gfeller
2020-04-29 18:17 ` Mauro Carvalho Chehab
2020-04-30 7:56 ` Patrik Gfeller
2020-04-30 10:55 ` Mauro Carvalho Chehab
2020-04-30 15:09 ` Patrik Gfeller
2020-04-30 22:25 ` Mauro Carvalho Chehab
2020-05-01 8:54 ` Patrik Gfeller
2020-05-01 9:38 ` Mauro Carvalho Chehab
2020-05-01 17:31 ` Patrik Gfeller
2020-05-01 19:30 ` Mauro Carvalho Chehab
2020-05-02 8:15 ` Patrik Gfeller
2020-05-02 9:20 ` Patrik Gfeller
2020-05-02 10:00 ` Mauro Carvalho Chehab
2020-05-02 9:34 ` Mauro Carvalho Chehab
2020-05-02 14:29 ` Patrik Gfeller
2020-05-02 16:28 ` Mauro Carvalho Chehab
2020-05-02 18:23 ` Patrik Gfeller
2020-05-02 14:50 ` Patrik Gfeller
2020-05-01 20:56 ` [PATCH] media: atomisp: use add_qos_request instead of update Mauro Carvalho Chehab
2020-04-18 15:29 ` atomisp kernel driver(s) Patrik Gfeller
2020-04-25 2:39 ` Laurent Pinchart
2020-04-25 10:36 ` Patrik Gfeller
2020-04-25 12:19 ` Mauro Carvalho Chehab
2020-04-26 19:07 ` Laurent Pinchart
2020-04-26 20:51 ` Mauro Carvalho Chehab
2020-04-26 19:33 ` Laurent Pinchart
2020-04-28 18:13 ` Patrik Gfeller
2020-04-26 7:44 ` Patrik Gfeller
2020-04-26 19:17 ` Laurent Pinchart
2020-04-29 17:59 ` Patrik Gfeller
2020-04-29 18:19 ` Laurent Pinchart
2020-04-30 15:28 ` Patrik Gfeller
2020-05-02 16:08 ` Andy Shevchenko
2020-05-02 17:04 ` Mauro Carvalho Chehab
2020-05-02 17:33 ` Andy Shevchenko
2020-05-03 10:18 ` Mauro Carvalho Chehab
2020-05-12 10:20 ` Mauro Carvalho Chehab
2020-05-12 11:12 ` Andy Shevchenko
2020-05-12 11:21 ` Andy Shevchenko
2020-05-12 14:56 ` Mauro Carvalho Chehab
2020-05-12 16:01 ` Andy Shevchenko
2020-05-13 18:36 ` Patrik Gfeller
2020-05-20 8:04 ` Mauro Carvalho Chehab
2020-05-13 9:56 ` Mauro Carvalho Chehab
2020-05-03 8:46 ` Patrik Gfeller
2020-05-03 10:23 ` Mauro Carvalho Chehab
2020-05-03 12:31 ` Patrik Gfeller
2020-05-03 13:36 ` Patrik Gfeller
2020-05-03 14:43 ` Mauro Carvalho Chehab
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=c18ae1e7-cade-7231-7d07-c5d83be1093a@gmail.com \
--to=patrik.gfeller@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.