Re: [PATCH v2 1/2] DT: i2c: Deprecate adi,adxl34x compatible string

2015-05-21 Thread Simon Horman
On Thu, May 21, 2015 at 01:42:25PM +0200, Geert Uytterhoeven wrote: > From: Laurent Pinchart > > 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 ad

[PATCH v2 1/2] DT: i2c: Deprecate adi,adxl34x compatible string

2015-05-21 Thread Geert Uytterhoeven
From: Laurent Pinchart 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 Acked-by: Wolfram

Re: [PATCH v2 1/2] DT: i2c: Deprecate adi,adxl34x compatible string

2015-03-02 Thread Laurent Pinchart
(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 .d

Re: [PATCH v2 1/2] DT: i2c: Deprecate adi,adxl34x compatible string

2015-03-01 Thread Wolfram Sang
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. T

Re: [PATCH v2 1/2] DT: i2c: Deprecate adi,adxl34x compatible string

2015-02-26 Thread Laurent Pinchart
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 i

Re: [PATCH v2 1/2] DT: i2c: Deprecate adi,adxl34x compatible string

2015-01-26 Thread Wolfram Sang
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. >

Re: [PATCH v2 1/2] DT: i2c: Deprecate adi,adxl34x compatible string

2015-01-26 Thread Wolfram Sang
> >> 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 o

Re: [PATCH v2 1/2] DT: i2c: Deprecate adi,adxl34x compatible string

2015-01-15 Thread Laurent Pinchart
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 wrote: > >>> --- a/Documentation/devicetree/bindings/i2c/trivial-devices.txt > >>> +++ b/Documentation/devic

Re: [PATCH v2 1/2] DT: i2c: Deprecate adi,adxl34x compatible string

2015-01-15 Thread Geert Uytterhoeven
On Thu, Jan 15, 2015 at 6:43 PM, 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 wrote: >> >> --- a/Documentation/devicetree/bindings/i2c/trivial-devices.txt >> >> +++ b/Documentation/devicetree/bindings/i2

Re: [PATCH v2 1/2] DT: i2c: Deprecate adi,adxl34x compatible string

2015-01-15 Thread Geert Uytterhoeven
On Thu, Jan 15, 2015 at 3:54 PM, 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. > > Signed-

Re: [PATCH v2 1/2] DT: i2c: Deprecate adi,adxl34x compatible string

2015-01-15 Thread Wolfram Sang
On Thu, Jan 15, 2015 at 06:32:31PM +0100, Geert Uytterhoeven wrote: > On Thu, Jan 15, 2015 at 6:02 PM, Wolfram Sang wrote: > >> --- a/Documentation/devicetree/bindings/i2c/trivial-devices.txt > >> +++ b/Documentation/devicetree/bindings/i2c/trivial-devices.txt > >> @@ -18,8 +18,7 @@ adi,adt7475

Re: [PATCH v2 1/2] DT: i2c: Deprecate adi,adxl34x compatible string

2015-01-15 Thread Geert Uytterhoeven
On Thu, Jan 15, 2015 at 6:02 PM, Wolfram Sang 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 +/-1C TDM E

Re: [PATCH v2 1/2] DT: i2c: Deprecate adi,adxl34x compatible string

2015-01-15 Thread Dmitry Torokhov
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

Re: [PATCH v2 1/2] DT: i2c: Deprecate adi,adxl34x compatible string

2015-01-15 Thread Wolfram Sang
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. >

[PATCH v2 1/2] DT: i2c: Deprecate adi,adxl34x compatible string

2015-01-15 Thread Laurent Pinchart
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 --- Documentation/devicetree/bindings/i2c/