[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150306063628.GA883@katana>
Date: Fri, 6 Mar 2015 07:36:29 +0100
From: Wolfram Sang <wsa@...-dreams.de>
To: Maxime Ripard <maxime.ripard@...e-electrons.com>
Cc: Chen-Yu Tsai <wens@...e.org>, Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>, linux-i2c@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-sunxi@...glegroups.com,
Hans de Goede <hdegoede@...hat.com>,
Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH v2 1/4] i2c: sunxi: Add Reduced Serial Bus (RSB) support
> From that regard, RSB is a multiple device bus, using addresses, just
> like I2C. The way it communicates is basically the one used by P2WI.
I am not keen to allow everything which "is a bus and has addresses"
into the I2C realm. The addresses are 12 bit, whilst I2C has at maximum
10 bit which is rarely used, so mostly 7 bit are used. It has a runtime
readdressing mechanism which is not present in standard I2C. And if you
look at the protocol with no acks but parities, IMO it doesn't look
closer to I2C than to other two wire protocols. So, being in I2C needs
more arguments.
And while the outcome could be that it really makes sense to add RSB to
I2C with I2C_FUNCS_RSB added, it could also be that there is a more
suitable place for custom busses in the kernel.
Also, the fact that P2WI is in I2C is not an argument IMO. It could have
been a mistake to pick it up.
> So really, it just is more I2C-alike than P2WI has ever been.
Because it has addresses? I disagree.
> Good thing that we are not talking about a full review then, but more
> a philosophical discussion.
Exactly. This is why I wanted to bring this in early.
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists