From: Magnus Damm <magnus.damm@gmail.com>
To: linux-sh@vger.kernel.org
Subject: Re: [RFC V2 0/4] prototype: switch I2C IP cores at runtime
Date: Tue, 17 Mar 2015 09:18:36 +0000 [thread overview]
Message-ID: <CANqRtoRLwbQ3b3nKB7doXT8vm60kp_6aW7k586e-L7n6F0NOmw@mail.gmail.com> (raw)
In-Reply-To: <1426576524-22315-1-git-send-email-wsa@the-dreams.de>
Hi Wolfram,
On Tue, Mar 17, 2015 at 4:15 PM, Wolfram Sang <wsa@the-dreams.de> wrote:
> Some SoC (like Renesas RCar Gen2) have different I2C IP cores with different
> feature sets. This is an experimental patch series to let those different IP
> cores access the same I2C bus at runtime. Finally, we have some code to talk
> about :) Unlike previous sketched versions, this one does not require a
> remove/probe-cycle of I2C bus drivers which would mean complete
> reinitialization of all connected I2C clients. However, the first two patches
> need serious discussion. So, have a look if you are interested...
>
> Please have a look at the individual patches for changes since last version.
> This is mainly code improvements and rebase to v4.0-rc4 for easier testing and
> to keep discussion alive :) These patches are only sent to the sh-list for now.
> I'd like to have consensus here before involving people from the outside.
Thanks. I think this looks rather clean myself!
This approach would also in theory allow using a GPIO bitbang driver
as one alternative I2C master, right?
If so then I'm happy because we can then keep a single DTB and yet
generic distro-kernels should be able to include GPIO bitbang support
in their kernels but may exclude other variants of I2C master
controller drivers.
Cheers,
/ magnus
prev parent reply other threads:[~2015-03-17 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 7:15 [RFC V2 0/4] prototype: switch I2C IP cores at runtime Wolfram Sang
2015-03-17 9:18 ` Magnus Damm [this message]
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=CANqRtoRLwbQ3b3nKB7doXT8vm60kp_6aW7k586e-L7n6F0NOmw@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=linux-sh@vger.kernel.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).