From: Magnus Damm <magnus.damm@gmail.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Simon Horman <horms@verge.net.au>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux-I2C <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH v4 00/14] ARM: dts: r8a779x: use demuxer for I2C
Date: Thu, 10 Nov 2016 12:56:38 +0900 [thread overview]
Message-ID: <CANqRtoRwSh602rjbHA2qo=XHyimpyyi_T=0sh2A4NOfzzVB+oQ@mail.gmail.com> (raw)
In-Reply-To: <20161109172813.GA1545@katana>
Hi Wolfram,
On Thu, Nov 10, 2016 at 2:28 AM, Wolfram Sang <wsa@the-dreams.de> wrote:
>
>> ARM: dts: lager: use demuxer for IIC3/I2C3
>
> I think the sanest solution is to drop this patch forever. The WARN from
> the regulator core is sparse in describing the problem yet it is
> correct: The regulator is needed, by the CPU! :) And this will probably
> be the smallest problem when trying to demux the bus which is used to
> handle all DVFS operations. Let's stick to IIC3 here, I'd say. Gen3 even
> has this one IIC instance for exactly the DVFS purpose.
I think postponing merge of patches is one thing but I don't think
dropping them forever is a long term solution. I think we should have
a plan how to describe the hardware as-is in DT and work towards
having software support for it.
My hope has always been that it would be possible to switch I2C master
during run time without deregister/register of all the slave devices.
I do realise much work will be needed to make it happen, but from
hardware point of view it must be possible to switch I2C master
transparently between the messages on the bus.
Thanks,
/ magnus
next prev parent reply other threads:[~2016-11-10 3:56 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 20:20 [PATCH v4 00/14] ARM: dts: r8a779x: use demuxer for I2C Wolfram Sang
2016-11-06 20:20 ` [PATCH v4 01/14] ARM: dts: lager: rename and reindex i2cexio Wolfram Sang
2016-11-07 13:12 ` Geert Uytterhoeven
2016-11-10 10:11 ` Simon Horman
2016-11-06 20:20 ` [PATCH v4 02/14] ARM: dts: lager: use demuxer for IIC1/I2C1 Wolfram Sang
2016-11-06 20:20 ` [PATCH v4 03/14] ARM: dts: lager: use demuxer for IIC2/I2C2 Wolfram Sang
2016-11-06 20:20 ` [PATCH v4 04/14] ARM: dts: lager: use demuxer for IIC3/I2C3 Wolfram Sang
2016-11-06 20:20 ` [PATCH v4 05/14] ARM: dts: koelsch: use demuxer for I2C1 Wolfram Sang
2016-11-06 20:20 ` [PATCH v4 06/14] ARM: dts: koelsch: use demuxer for I2C2 Wolfram Sang
2016-11-06 20:20 ` [PATCH v4 07/14] ARM: dts: koelsch: use demuxer for I2C4 Wolfram Sang
2016-11-15 15:45 ` Geert Uytterhoeven
2016-11-15 17:44 ` Simon Horman
2016-11-16 10:35 ` Geert Uytterhoeven
2016-11-16 13:47 ` Simon Horman
2016-11-16 14:14 ` Geert Uytterhoeven
2016-11-16 14:17 ` Simon Horman
2016-11-16 13:48 ` Geert Uytterhoeven
2016-11-06 20:20 ` [PATCH v4 08/14] ARM: dts: porter: use demuxer for I2C2 Wolfram Sang
2016-11-06 20:20 ` [PATCH v4 09/14] ARM: dts: gose: " Wolfram Sang
2016-11-06 20:20 ` [PATCH v4 10/14] ARM: dts: gose: use demuxer for I2C4 Wolfram Sang
2016-11-06 20:20 ` [PATCH v4 11/14] ARM: dts: alt: use demuxer for I2C1 Wolfram Sang
2016-11-06 20:20 ` [PATCH v4 12/14] ARM: dts: alt: use demuxer for I2C4 Wolfram Sang
2016-11-06 20:20 ` [PATCH v4 13/14] ARM: dts: silk: use demuxer for I2C1 Wolfram Sang
2016-11-06 20:20 ` [PATCH v4 14/14] i2c: mux: demux-pinctrl: make drivers with no pinctrl work again Wolfram Sang
2016-11-07 13:10 ` Geert Uytterhoeven
2016-11-10 20:12 ` Wolfram Sang
2016-11-09 8:44 ` [PATCH v4 00/14] ARM: dts: r8a779x: use demuxer for I2C Simon Horman
2016-11-09 8:55 ` Geert Uytterhoeven
2016-11-09 8:59 ` Wolfram Sang
2016-11-09 14:35 ` Simon Horman
2016-11-09 19:00 ` Geert Uytterhoeven
2016-11-11 8:20 ` Simon Horman
2016-11-10 10:06 ` Simon Horman
2016-11-09 17:28 ` Wolfram Sang
2016-11-10 3:56 ` Magnus Damm [this message]
2016-11-10 7:57 ` Wolfram Sang
2016-11-10 8:12 ` Magnus Damm
2016-11-10 15:30 ` Niklas Söderlund
2016-11-10 15:39 ` Wolfram Sang
2017-01-04 10:25 ` Wolfram Sang
2017-01-09 9:34 ` Niklas Söderlund
2017-01-31 15:42 ` Niklas Söderlund
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='CANqRtoRwSh602rjbHA2qo=XHyimpyyi_T=0sh2A4NOfzzVB+oQ@mail.gmail.com' \
--to=magnus.damm@gmail.com \
--cc=horms@verge.net.au \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@the-dreams.de \
/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).