From: Mark Brown <broonie@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
linux-media@vger.kernel.org,
Mike Turquette <mturquette@linaro.org>
Subject: Re: [GIT PULL FOR v3.10] Camera sensors patches
Date: Mon, 22 Apr 2013 11:03:20 +0100 [thread overview]
Message-ID: <20130422100320.GC30351@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1905734.rpqfOCmvCu@avalon>
[-- Attachment #1: Type: text/plain, Size: 504 bytes --]
On Mon, Apr 22, 2013 at 01:14:07AM +0200, Laurent Pinchart wrote:
> I think that Mark's point was that the regulators should be provided by
> platform code (in the generic sense, it could be DT on ARM, board code, or a
> USB bridge driver for a webcam that uses the mt9p031 sensor) and used by the
> sensor driver. That's exactly what my mt9p031 patch does.
Yes, you understood me perfectly - to a good approximation the matching
up should be done by whatever the chip is soldered down to.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-04-22 10:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 9:13 [GIT PULL FOR v3.10] Camera sensors patches Laurent Pinchart
2013-04-14 19:59 ` Mauro Carvalho Chehab
2013-04-15 10:19 ` Laurent Pinchart
2013-04-15 12:42 ` Mauro Carvalho Chehab
2013-04-16 15:30 ` Laurent Pinchart
2013-04-16 17:36 ` Mauro Carvalho Chehab
2013-04-16 18:04 ` Sylwester Nawrocki
2013-04-17 13:55 ` Mark Brown
2013-04-17 14:36 ` Mauro Carvalho Chehab
2013-04-21 23:14 ` Laurent Pinchart
2013-04-22 10:03 ` Mark Brown [this message]
2013-04-22 12:46 ` Mauro Carvalho Chehab
2013-04-22 12:56 ` Mark Brown
2013-04-22 12:46 ` 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=20130422100320.GC30351@opensource.wolfsonmicro.com \
--to=broonie@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=mturquette@linaro.org \
--cc=s.nawrocki@samsung.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).