linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Patrik Gfeller <patrik.gfeller@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: atomisp kernel driver(s)
Date: Mon, 20 Apr 2020 01:31:09 +0200	[thread overview]
Message-ID: <20200420013109.65babb54@coco.lan> (raw)
In-Reply-To: <1d529105-3b7d-38d0-b7a2-d385b2221ff7@gmail.com>

Em Sat, 18 Apr 2020 17:37:22 +0200
Patrik Gfeller <patrik.gfeller@gmail.com> escreveu:

> On 18.04.20 17:26, Mauro Carvalho Chehab wrote:
> > Em Sat, 18 Apr 2020 17:25:49 +0200
> > Mauro Carvalho Chehab <mchehab+huawei@kernel.org> escreveu:
> >  
> >> Em Sat, 18 Apr 2020 16:39:25 +0200
> >> Patrik Gfeller <patrik.gfeller@gmail.com> escreveu:
> >>  
> >>> Hello Mauro et al,
> >>>
> >>> I've recently switched to Linux, and I'm very impressed. Almost
> >>> everything thing works out of the box. Only the webcam on my device does
> >>> not. I did some digging and if I'm right an atomisp driver would be
> >>> required. Is this correct? Below the output of lspci:
> >>>
> >>> 00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor
> >>> x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 36) 00:02.0
> >>> VGA compatible controller: Intel Corporation Atom/Celeron/Pentium
> >>> Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 36)
> >>> 00:03.0 Multimedia controller: Intel Corporation Atom/Celeron/Pentium
> >>> Processor x5-E8000/J3xxx/N3xxx Series Imaging Unit (rev 36) 00:0a.0
> >>> Non-VGA unclassified device: Intel Corporation Device 22d8 (rev 36)
> >>> 00:0b.0 Signal processing controller: Intel Corporation
> >>> Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power
> >>> Management Controller (rev 36) 00:14.0 USB controller: Intel Corporation
> >>> Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI
> >>> Controller (rev 36) 00:1a.0 Encryption controller: Intel Corporation
> >>> Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted
> >>> Execution Engine (rev 36) 00:1c.0 PCI bridge: Intel Corporation
> >>> Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express
> >>> Port #1 (rev 36) 00:1f.0 ISA bridge: Intel Corporation
> >>> Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU (rev 36)
> >>> 01:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless
> >>> Network Adapter (rev 31)

What hardware do you have?

I did a look at the atomisp driver. There are some APIs that changed upstream,
but making the driver to build again is not hard:

	https://git.linuxtv.org/mchehab/experimental.git/log/?h=atomisp

If this would work or just hang, I don't know :-)

This driver is still a big mess, and it requires some defines on its source
code, in order to use it with some different Atom models.

> >>>
> >>> According to the history it looks like the driver was removed from the
> >>> kernel in 2018 and replaced with a dummy driver (to make sure power save
> >>> works).
> >>>
> >>> Is there a chance that the atomisp driver will return to the kernel?
> >>> There are quite a few older tablets and 2in1 devices that would benefit.
> >>> Unfortunately I do not understand the removed code (my coding skills are
> >>> very basic) and can thus not help to change what ever is necessary to
> >>> make it fit for the kernel :-( (does not sound like a beginner project).
> >>> However - I would be glad to help out to help testing an ISP driver.  
> >> There are simply too many things there to be fixed, and nobody without
> >> time for it. Also, the last reports we had is that the driver was not
> >> working.
> >>
> >> Unfortunately, I don't have myself any atomisp hardware, otherwise I
> >> could try fixing it on my spare time.  
> > In time: not really sure if it would be a worth project, as newer Intel
> > hardware are coming with a different IP block (IPU3).  
> 
> I don't know how widespread the IPU that I have is, I assume that some 
> other tablets & 2in1 devices that are a few years old use it as well. 

The IPU is used on some Dell 2in1 devices(I guess they use an i5core 
with a chipset made for mobile market). Not sure if they're using IPU3
also on Atom.

> For me it would be definitely nice to have this driver. However, I can 
> ask around in some of the forums  if there is a wider interest. Might be 
> a niche tough, but the support for the Atom device I use have been 
> greatly improved in the recent years. So there is at least some work 
> going on for that platform (I do not know, but I think it is called 
> cherry trail?). As there are many older reports of problems with audio, 
> touchscreen, stability (freezes) ... and none of them are present anymore.
> 
> As mentioned, if the development is hindered by missing hardware I would 
> be glad to help. Anyhow - many thanks for your replies, much appreciated!
> 
> >
> > Thanks,
> > Mauro  



Thanks,
Mauro

  reply	other threads:[~2020-04-19 23:31 UTC|newest]

Thread overview: 69+ 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 [this message]
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
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-04-18 15:29   ` 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=20200420013109.65babb54@coco.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=patrik.gfeller@gmail.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;
as well as URLs for NNTP newsgroup(s).