All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@linux.intel.com>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: greg@kroah.com, mchehab@kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH] staging/atomisp: Add support for the Intel IPU v2
Date: Thu, 09 Mar 2017 11:17:33 +0000	[thread overview]
Message-ID: <1489058253.5218.16.camel@linux.intel.com> (raw)
In-Reply-To: <20170308133726.05a12c0d@vento.lan>

> Before moving firmware-dependent drivers out of staging, please send
the
> firmware files to linux-firmware ML.

The firmware files come with the system. They may have system dependant
components and it's also not clear that they can be put in linux-
firmware for licensing reasons. They are however available on the
device itself, and in the downloadable re-install/upgrade kit supplied
by the actual product vendor for the relevant device.

I'm working on the firmware question but it's a slow moving item 8(

> >  920 files changed, 204645 insertions(+)
> 
> Wow! that's huge!

It was quite a bit larger. I'm slowly trying to diet it, and it looks
like a lot of the code is portability indirections, or in many cases
simply unused library routines. That said the hardware does an awful
lot of things.

> > +5. The AtomISP driver includes some special IOCTLS
> > (ATOMISP_IOC_XXXX_XXXX)
> > +   that may need some cleaning up.
> 
> Those likely require upstream discussions, in order to identify if
> are 
> there any already existing ioctl set that does the same thing and/or
> if it makes sense to add new ioctls to do what's needed there.

Definitely.

> When you think that each of those I2C drivers are ready to be 
> promoted out of staging, please send them as if they're a new driver
> to
> linux-media@vger.kernel.org, as this will make the review process
> easier.

Will do - thanks

Alan

      reply	other threads:[~2017-03-09 11:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <148735051279.12479.11445229229552101143.stgit@acox1-desk1.ger.corp.intel.com>
2017-03-08 16:37 ` [PATCH] staging/atomisp: Add support for the Intel IPU v2 Mauro Carvalho Chehab
2017-03-09 11:17   ` Alan Cox [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=1489058253.5218.16.camel@linux.intel.com \
    --to=alan@linux.intel.com \
    --cc=greg@kroah.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=mchehab@s-opensource.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 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.