From: Sylwester Nawrocki <s.nawrocki-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Jassi Brar
<jaswinder.singh-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>,
Mauro Carvalho Chehab
<m.chehab-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Subject: Re: I2C dummy adapter driver ?
Date: Tue, 04 Mar 2014 12:38:28 +0100 [thread overview]
Message-ID: <5315BB34.8080803@samsung.com> (raw)
In-Reply-To: <20140228060728.GB29849-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
On 28/02/14 07:07, Mark Brown wrote:
> On Fri, Feb 21, 2014 at 12:45:21PM +0100, Sylwester Nawrocki wrote:
>
>> The I2C bus driver with empty i2c_algorithm.master_xfer() helps WRT to
>> using standard DT binding and v4l2_subdev interface.
>
> Wouldn't a platform device do just as well here if there's no actual
> control?
Then the I2C client devices would have to be instantiated manually,
I think it's more trouble.
I could as well create custom I2C client drivers per ISP, but then the
I2C devices would have to be represented somehow in DT, to pass stuff
like voltage regulators and GPIOs. Anyway, it's not something could be
done in mainline.
Even if there is no actual I2C communication on the host CPU side, the
power up/down sequence is handled there. The intention is to keep this
common per an I2C client, regardless of whether I2C communication is
done by firmware or the host the CPU.
next prev parent reply other threads:[~2014-03-04 11:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 23:03 I2C dummy adapter driver ? Sylwester Nawrocki
[not found] ` <5305382E.9050902-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-02-20 16:49 ` Stephen Warren
[not found] ` <5306322C.8030703-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-02-21 11:26 ` Sylwester Nawrocki
2014-02-21 5:57 ` Jassi Brar
[not found] ` <CAJe_ZhcMMVRTErH3ctbnZyn30_cp9XXjEfUZXdWaVWUHqs4CRw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-21 11:45 ` Sylwester Nawrocki
[not found] ` <53073C51.5010401-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-02-28 6:07 ` Mark Brown
[not found] ` <20140228060728.GB29849-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-03-04 11:38 ` Sylwester Nawrocki [this message]
[not found] ` <5315BB34.8080803-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-03-05 1:15 ` Mark Brown
[not found] ` <20140305011530.GN13126-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-03-07 13:49 ` Sylwester Nawrocki
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=5315BB34.8080803@samsung.com \
--to=s.nawrocki-sze3o3uu22jbdgjk7y7tuq@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=jaswinder.singh-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=m.chehab-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org \
/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).