From: Mark Brown <broonie@kernel.org>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.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 13:56:31 +0100 [thread overview]
Message-ID: <20130422125631.GK30351@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5175310F.6080002@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
On Mon, Apr 22, 2013 at 09:46:07AM -0300, Mauro Carvalho Chehab wrote:
> Em 22-04-2013 07:03, Mark Brown escreveu:
> >Yes, you understood me perfectly - to a good approximation the matching
> >up should be done by whatever the chip is soldered down to.
> That doesn't make any sense to me. I2C devices can be used anywere,
> as they can be soldered either internally on an USB webcam without
> any regulators or any other platform code on it or could be soldered
> to some platform-specific bus.
If it's running on Linux on a visible I2C bus it ought to be shown as an
I2C bus on Linux and the thing doing that plumbing ought to be worrying
about hooking up anything the driver needs.
> Also, what best describes "soldered" here is the binding between
> an I2C driver and the I2C adapter. The I2C adapter is a platform
> driver on embedded devices, where, on an usual USB camera, it
> is just a USB->I2C bridge.
Sure, but there's no meaningful difference between these things as far
as plumbing things together goes.
> Also, requiring that simple USB cameras to have regulators will
> prevent its usual usage, as non-platform distros don't set config
> REGULATOR, and it shouldn't.
No problem there, the regulator API stubs itself out if it's not
enabled.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-04-22 12:56 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
2013-04-22 12:46 ` Mauro Carvalho Chehab
2013-04-22 12:56 ` Mark Brown [this message]
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=20130422125631.GK30351@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 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.