Hi Nicolas,
We added mipi nodes to the device tree that we use with our custom board and are able to capture from two mipi cameras. I forwarded our working device tree to Penguin Solutions to see if they can cut and paste portions to get their SOM
to work on their dev board. I think what we would like is maybe a review of the camss node additions to tell us if what is working is actually correct. Does that sound like something Linaro would do?
Thanks,
Kim
From: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Sent: Monday, December 19, 2022 10:59 PM
To: Kim Steiner <kim.steiner@sightlineapplications.com>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>; Jordan Holt <jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org
Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
hey Kim,
Back in those days, there was a Camera Mezzanine (an add-on board) from D3 engineering, which we used for the initial development of the camera driver for SD820, this is what the DTS references in the 4.14 release branch. However this camera
mezzanine was never launched, nor 'easily' available for anyone, so we removed the support from the DB820c DTS (and did not push it upstream). With the exception of a small group of developers, nobody had a DB820c + D3 mezzanine. The initial idea was to create
2 DTS files, or the DB820c only and the DB820c+D3, but since the D3 did not materialize, the camera nodes have been removed.
But that does not imply that Camera is not working on Snapdragon 820 (the SoC), it does, and is enabled upstream. It's just the default DTS configuration for the DB820c (the board, not the SoC) where it's not defined by default, since the
DB820c (the board) does not come with camera.
The appropriate thing to do is to create a DTS file for any custom hardware which accurately describes the board. Since your device has cameras, your DTS needs to define these nodes. I can see that PenguinSolutions have opened a support
ticket with Linaro since they are trying to enable ov5640 camera on qcomlt-5.15 kernel, and need the DTS changes for that. If you are okay with it, this is something we can do once we receive your hardware (with schematics). Dmitry can provide a full DTS,
derived from the DB820c DTS with complete description of the hardware, including cameras.
cheers
nicolas
On Tue, Dec 20, 2022 at 12:01 AM Kim Steiner <kim.steiner@sightlineapplications.com> wrote:
Hi Nicolas,
Why were there camera nodes in the 4.14 kernel? Isn’t this also used by DB820c?
Thanks,
Kim
From: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Sent: Monday, December 19, 2022 1:35 AM
To: Kim Steiner <kim.steiner@sightlineapplications.com>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>; Jordan Holt <jordan.holt@sightlineapplications.com>; Paul Neuhardt <paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org
Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
On Thu, Dec 15, 2022 at 3:20 PM Kim Steiner <kim.steiner@sightlineapplications.com> wrote:
Hi. We were talking about camera testing on the DB820c yesterday and Linaro said that no camera has been tested. I asked Penguin Solutions how things are going with their patches. They said there are no camera nodes in the device tree. I noticed this too and had to add my own camera nodes. Is this something that you would have to add in order to test a camera on the DB820c?
Yes, you are correct. We never sent upstream the camera support in the 820c DTS, the main reason is that QCOM never really shipped an official mezzanine for the 820c that has camera, even today it's difficult to get the hardware. The 820c DTS upstream describes the 820c as you can 'buy' it. But there is camera (camss) support in the msm8996.dtsi platform, so that any 8996 based board can use camera, once they configure the camera nodes in the corresponding DTS.
Once we start working on your custom hardware, we can help review the DTS.
Thanks,
Kim
-----Original Message-----
From: Kim Steiner
Sent: Wednesday, December 14, 2022 2:17 PM
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>; Jordan Holt <jordan.holt@sightlineapplications.com>
Cc: Paul Neuhardt <paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org
Subject: RE: [Sightlineapplications] Re: Project Status and Burn Report
Thanks Dmitry. I will test this later this week.
Attached is the DB820C boot up and .config. I disabled CONFIG_BT, CONFIG_SND, and CONFIG_CFG80211, but I still see a CONFIG_WIRELESS enabled. I've attached a snapshot of the DB820c as well.
Also, we were running a 1280x720 @60 fps when we saw the capture/display glitch when capture and encoding.
I will get back to you about the bootloader when I figure that out.
Thanks,
Kim
-----Original Message-----
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Sent: Wednesday, December 14, 2022 10:14 AM
To: Kim Steiner <kim.steiner@sightlineapplications.com>; Jordan Holt <jordan.holt@sightlineapplications.com>
Cc: Paul Neuhardt <paul.neuhardt@linaro.org>; sightlineapplications@lists.linaro.org
Subject: Re: [Sightlineapplications] Re: Project Status and Burn Report
Hi Kim,
On 08/12/2022 16:03, Kim Steiner wrote:
> Hi Dmitry,
>
> I did some more testing on the DB820C. I see a couple of more boot up failures.
As promised, quick and dirty patch to unlock CPU frequencies.
Using this patch I got the following frequencies after bootup:
root@linaro-alip:~# cpufreq-info | grep current
current policy: frequency should be within 307 MHz and 1.59 GHz.
current CPU frequency is 1.59 GHz (asserted by call to hardware).
current policy: frequency should be within 307 MHz and 1.59 GHz.
current CPU frequency is 1.59 GHz (asserted by call to hardware).
current policy: frequency should be within 307 MHz and 2.15 GHz.
current CPU frequency is 2.00 GHz (asserted by call to hardware).
current policy: frequency should be within 307 MHz and 2.15 GHz.
current CPU frequency is 2.00 GHz (asserted by call to hardware).
--
With best wishes
Dmitry
_______________________________________________
Sightlineapplications mailing list -- sightlineapplications@lists.linaro.org
To unsubscribe send an email to sightlineapplications-leave@lists.linaro.org