From: Laurent Pinchart laurent.pinchart+rene...@ideasonboard.com
DT nodes should use the more specific adi,adxl345 and adi,adxl346
compatible values instead. As the ADXL346 is backward-compatible with
the ADXL345, ADXL346 nodes must list both adi,adxl346 and adi,adxl345,
in that order.
(CC'ing Dmitry)
On Monday 02 March 2015 07:40:49 Wolfram Sang wrote:
On Thu, Feb 26, 2015 at 04:27:49PM +0200, Laurent Pinchart wrote:
On Monday 26 January 2015 13:09:47 Wolfram Sang wrote:
If you drop adi,adxl346, checkpatch will start complaining if it
encounters it in a .dts.
Boah,
On Thu, Feb 26, 2015 at 04:27:49PM +0200, Laurent Pinchart wrote:
Hi Wolfram,
On Monday 26 January 2015 13:09:47 Wolfram Sang wrote:
If you drop adi,adxl346, checkpatch will start complaining if it
encounters
it in a .dts.
Boah, this is annoying. That means we need an 346
Hi Wolfram,
On Monday 26 January 2015 13:09:47 Wolfram Sang wrote:
If you drop adi,adxl346, checkpatch will start complaining if it
encounters
it in a .dts.
Boah, this is annoying. That means we need an 346 entry even if it is
not different from 345 (which is fine by me).
If you drop adi,adxl346, checkpatch will start complaining if it encounters
it in a .dts.
Boah, this is annoying. That means we need an 346 entry even if it is
not different from 345 (which is fine by me).
To be clear: you need the entry in the documentation. It can be omitted
from
On Thu, Jan 15, 2015 at 04:54:14PM +0200, Laurent Pinchart wrote:
DT nodes should use the more specific adi,adxl345 and adi,adxl346
compatible values instead. As the ADXL346 is backward-compatible with
the ADXL345, ADXL346 nodes must list both adi,adxl346 and adi,adxl345,
in that order.
On Thu, Jan 15, 2015 at 04:54:14PM +0200, Laurent Pinchart wrote:
DT nodes should use the more specific adi,adxl345 and adi,adxl346
compatible values instead. As the ADXL346 is backward-compatible with
the ADXL345, ADXL346 nodes must list both adi,adxl346 and adi,adxl345,
in that order.
On Thu, Jan 15, 2015 at 6:02 PM, Wolfram Sang w...@the-dreams.de wrote:
--- a/Documentation/devicetree/bindings/i2c/trivial-devices.txt
+++ b/Documentation/devicetree/bindings/i2c/trivial-devices.txt
@@ -18,8 +18,7 @@ adi,adt7475 +/-1C TDM Extended Temp Range I.C
adi,adt7476
On Thu, Jan 15, 2015 at 06:32:31PM +0100, Geert Uytterhoeven wrote:
On Thu, Jan 15, 2015 at 6:02 PM, Wolfram Sang w...@the-dreams.de wrote:
--- a/Documentation/devicetree/bindings/i2c/trivial-devices.txt
+++ b/Documentation/devicetree/bindings/i2c/trivial-devices.txt
@@ -18,8 +18,7 @@
On Thu, Jan 15, 2015 at 6:43 PM, Wolfram Sang w...@the-dreams.de wrote:
On Thu, Jan 15, 2015 at 06:32:31PM +0100, Geert Uytterhoeven wrote:
On Thu, Jan 15, 2015 at 6:02 PM, Wolfram Sang w...@the-dreams.de wrote:
--- a/Documentation/devicetree/bindings/i2c/trivial-devices.txt
+++
On Thu, Jan 15, 2015 at 06:02:09PM +0100, Wolfram Sang wrote:
On Thu, Jan 15, 2015 at 04:54:14PM +0200, Laurent Pinchart wrote:
DT nodes should use the more specific adi,adxl345 and adi,adxl346
compatible values instead. As the ADXL346 is backward-compatible with
the ADXL345, ADXL346 nodes
On Thu, Jan 15, 2015 at 3:54 PM, Laurent Pinchart
laurent.pinchart+rene...@ideasonboard.com wrote:
DT nodes should use the more specific adi,adxl345 and adi,adxl346
compatible values instead. As the ADXL346 is backward-compatible with
the ADXL345, ADXL346 nodes must list both adi,adxl346 and
DT nodes should use the more specific adi,adxl345 and adi,adxl346
compatible values instead. As the ADXL346 is backward-compatible with
the ADXL345, ADXL346 nodes must list both adi,adxl346 and adi,adxl345,
in that order.
Signed-off-by: Laurent Pinchart laurent.pinchart+rene...@ideasonboard.com
Hi Wolfram,
On Thursday 15 January 2015 18:43:33 Wolfram Sang wrote:
On Thu, Jan 15, 2015 at 06:32:31PM +0100, Geert Uytterhoeven wrote:
On Thu, Jan 15, 2015 at 6:02 PM, Wolfram Sang w...@the-dreams.de wrote:
--- a/Documentation/devicetree/bindings/i2c/trivial-devices.txt
+++
14 matches
Mail list logo
