mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bingbu Cao <bingbu.cao@linux.intel.com>
To: Kai Heng Feng <kai.heng.feng@canonical.com>,
	Kieran Bingham <kieran.bingham@ideasonboard.com>
Cc: sakari.ailus@linux.intel.com, bingbu.cao@intel.com,
	yong.zhi@intel.com, linux-media@vger.kernel.org,
	devel@driverdev.osuosl.org,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	LibCamera Devel <libcamera-devel@lists.libcamera.org>
Subject: Re: ipu3-imgu 0000:00:05.0: required queues are disabled
Date: Tue, 29 Jan 2019 19:32:12 +0800	[thread overview]
Message-ID: <9311dd48-2169-5615-4368-1053a0d47e07@linux.intel.com> (raw)
In-Reply-To: <76CB59A0-D8F2-4C01-A600-60138ED5E785@canonical.com>



On 01/28/2019 11:45 PM, Kai Heng Feng wrote:
> Hi Kieran,
>
>> On Jan 28, 2019, at 4:48 PM, Kieran Bingham <kieran.bingham@ideasonboard.com> wrote:
>>
>> Hi Kai-Heng,
>>
>> On 27/01/2019 05:56, Kai-Heng Feng wrote:
>>> Hi,
>>>
>>> We have a bug report [1] that the ipu3 doesn’t work.
>>> Does ipu3 need special userspace to work?
>> Yes, it will need further userspace support to configure the pipeline,
>> and to provide 3A algorithms for white balance, focus, and exposure
>> times to the sensor.
>>
>> We are developing a stack called libcamera [0] to support this, but it's
>> still in active development and not yet ready for use. Fortunately
>> however, IPU3 is one of our primary initial targets.
> Thanks for the info.
Hi, Kai-Heng,

Like Bingham said, for IPU3 some heavy control from the userspace is needed.
libcamera is a very good start.
If you just want to verify the driver firstly, you can use script to take a try.
>> [0] https://www.libcamera.org/
>>
>>> [1] https://bugs.launchpad.net/bugs/1812114
>> I have reported similar information to the launchpad bug entry.
>>
>> It might help if we can get hold of a Dell 7275 sometime although I
>> think Mauro at least has one ?
>>
>> If this is a priority for Canonical, please contact us directly.
> Not really, just raise issues from Launchpad to appropriate mailing list.
>
> Kai-Heng
>
>>> Kai-Heng
>> --
>> Regards
>>
>> Kieran
>


      reply	other threads:[~2019-01-29 11:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-27  5:56 Kai-Heng Feng
2019-01-28  8:48 ` Kieran Bingham
2019-01-28 15:45   ` Kai Heng Feng
2019-01-29 11:32     ` Bingbu Cao [this message]

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=9311dd48-2169-5615-4368-1053a0d47e07@linux.intel.com \
    --to=bingbu.cao@linux.intel.com \
    --cc=bingbu.cao@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=kai.heng.feng@canonical.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=libcamera-devel@lists.libcamera.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=yong.zhi@intel.com \
    /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

all inboxes | Powered by JetHome®