From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Sylwester Nawrocki
<sylvester.nawrocki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Cc: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
Subject: Re: I2C dummy adapter driver ?
Date: Thu, 20 Feb 2014 09:49:48 -0700 [thread overview]
Message-ID: <5306322C.8030703@wwwdotorg.org> (raw)
In-Reply-To: <5305382E.9050902-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 02/19/2014 04:03 PM, Sylwester Nawrocki wrote:
> Hi All,
>
> I was wondering whether it would be reasonable to create a generic
> Linux dummy I2C bus controller driver. The rationale behind it is
> there might be hardware configurations where I2C communication is
> handled by firmware but still it is useful to have I2C slave devices
^^^^^^^^
That doesn't sound like a dummy driver. Rather, it sounds like a driver
for the firmware(?) interface that's used to do the I2C transactions.
> instantiated by a Linux I2C bus adapter driver.
> It would be useful to have the common devicetree I2C binding scheme
> working regardless of where the I2C communication is handled - in
> firmware or by the host CPU.
>
> Currently we have a somewhat dummy I2C adapter driver at drivers/media/
> platform/exynos4-is/fimc-is-i2c.c. But it is going to be needed by
> multiple SoCs and I thought about separating it or creating a generic
> dummy I2C adapter driver.
next prev parent reply other threads:[~2014-02-20 16:49 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 [this message]
[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
[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=5306322C.8030703@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sylvester.nawrocki-Re5JQEeQqe8AvxtiuMwx3w@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).