From: Alan Cox <alan@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>,
Devid Antonio Filoni <d.filoni@ubuntu.com>
Cc: andriy.shevchenko@linux.intel.com,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jérémy Lefaure" <jeremy.lefaure@lse.epita.fr>,
"Hans Verkuil" <hverkuil@xs4all.nl>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
devel@driverdev.osuosl.org
Subject: Re: [PATCH v4] staging: atomisp: add a driver for ov5648 camera sensor
Date: Tue, 10 Oct 2017 10:08:40 +0100 [thread overview]
Message-ID: <1507626520.26339.9.camel@linux.intel.com> (raw)
In-Reply-To: <20171006125716.txmwvuhhxdw2fyji@paasikivi.fi.intel.com>
> Would it make sense to first get the other drivers to upstream and
> then see what's the status of atomisp?
Agreed
> the board specific information from firmware is conveyed to the
> sensor drivers will change to what the rest of the sensor drivers are
> using. I think a most straightforward way would be to amend the ACPI
> tables to include the necessary information.
I don't see that happening. The firmware they have today is the
firmware they will always have, and for any new devices we manage to
get going is probably going to end up entirely hardcoded.
> For this reason I'm tempted to postpone applying this patch at least
> until the other drivers are available.
Yes - unless someone has a different controller and that sensor on a
board so can test it that way ?
Alan
next prev parent reply other threads:[~2017-10-10 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 23:23 [PATCH v4] staging: atomisp: add a driver for ov5648 camera sensor Devid Antonio Filoni
2017-10-06 12:57 ` Sakari Ailus
2017-10-10 9:08 ` Alan Cox [this message]
2017-10-10 11:49 ` Sakari Ailus
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=1507626520.26339.9.camel@linux.intel.com \
--to=alan@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=d.filoni@ubuntu.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil@xs4all.nl \
--cc=jeremy.lefaure@lse.epita.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.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