From: Wolfram Sang <wsa@the-dreams.de>
To: linux-sh@vger.kernel.org
Subject: Re: [RFC V2 4/4] i2c: mux: demux-pinctrl: add driver
Date: Tue, 21 Apr 2015 18:47:01 +0000 [thread overview]
Message-ID: <20150421184701.GA9573@katana> (raw)
In-Reply-To: <1426576524-22315-5-git-send-email-wsa@the-dreams.de>
[-- Attachment #1: Type: text/plain, Size: 589 bytes --]
> > Thanks for your input!
>
> You're welcome. I'm afraid it has mostly been destructive input, I don't have
> any good solution to the problem for now :-(
Well, actually, I have another version based on OF_DYNAMIC mostly ready.
It is not capable of keeping the I2C clients between an IP core switch,
but it is MUCH closer to the driver model. Could be good enough for our
use-case. Tests so far have been promising, but I get an OOPS when the
platform_devices should get destroyed. This looks like an OF_DYNAMIC
problem to me and I haven't got feedback from Pantelis yet.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-04-21 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 7:15 [RFC V2 4/4] i2c: mux: demux-pinctrl: add driver Wolfram Sang
2015-03-18 13:18 ` Laurent Pinchart
2015-03-19 15:53 ` Wolfram Sang
2015-04-21 17:55 ` Laurent Pinchart
2015-04-21 18:47 ` Wolfram Sang [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=20150421184701.GA9573@katana \
--to=wsa@the-dreams.de \
--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).