Re: [RFC PATCH 2/3] drivers: misc: eeprom: at24: support reading mac eeprom from different addresses

On 30.06.2017 10:20, Uwe Kleine-König wrote: > Hallo, > > On Thu, Jun 29, 2017 at 02:39:10PM +0300, Claudiu Beznea wrote: >> diff --git a/include/linux/platform_data/at24.h >> b/include/linux/platform_data/at24.h >> index 271a4e2..d55c454 100644 >> --- a/include/linux/platform_data/at24.h >>

Re: [RFC PATCH 2/3] drivers: misc: eeprom: at24: support reading mac eeprom from different addresses

On 29.06.2017 18:32, David Lechner wrote: > On 06/29/2017 06:39 AM, Claudiu Beznea wrote: >> Add support for reading from different offsets of EEPROM. >> The offset is initialized via device tree. If nothing is >> given as input the old value, 0x90, is used. In this way >> the driver could be

Re: [RFC PATCH 2/3] drivers: misc: eeprom: at24: support reading mac eeprom from different addresses

On 30.06.2017 10:20, Uwe Kleine-König wrote: > Hallo, > > On Thu, Jun 29, 2017 at 02:39:10PM +0300, Claudiu Beznea wrote: >> diff --git a/include/linux/platform_data/at24.h >> b/include/linux/platform_data/at24.h >> index 271a4e2..d55c454 100644 >> --- a/include/linux/platform_data/at24.h >>

Re: [RFC PATCH 2/3] drivers: misc: eeprom: at24: support reading mac eeprom from different addresses

On 29.06.2017 18:32, David Lechner wrote: > On 06/29/2017 06:39 AM, Claudiu Beznea wrote: >> Add support for reading from different offsets of EEPROM. >> The offset is initialized via device tree. If nothing is >> given as input the old value, 0x90, is used. In this way >> the driver could be

Re: [RFC PATCH 2/3] drivers: misc: eeprom: at24: support reading mac eeprom from different addresses

On 29.06.2017 16:30, Ludovic Desroches wrote: > On Thu, Jun 29, 2017 at 02:56:03PM +0300, Andy Shevchenko wrote: >> On Thu, Jun 29, 2017 at 2:39 PM, Claudiu Beznea >> wrote: >>> Add support for reading from different offsets of EEPROM. >>> The offset is initialized

Re: [RFC PATCH 2/3] drivers: misc: eeprom: at24: support reading mac eeprom from different addresses

On 29.06.2017 16:30, Ludovic Desroches wrote: > On Thu, Jun 29, 2017 at 02:56:03PM +0300, Andy Shevchenko wrote: >> On Thu, Jun 29, 2017 at 2:39 PM, Claudiu Beznea >> wrote: >>> Add support for reading from different offsets of EEPROM. >>> The offset is initialized via device tree. If nothing

Re: [RFC PATCH 2/3] drivers: misc: eeprom: at24: support reading mac eeprom from different addresses

Hallo, On Thu, Jun 29, 2017 at 02:39:10PM +0300, Claudiu Beznea wrote: > diff --git a/include/linux/platform_data/at24.h > b/include/linux/platform_data/at24.h > index 271a4e2..d55c454 100644 > --- a/include/linux/platform_data/at24.h > +++ b/include/linux/platform_data/at24.h > @@ -50,6 +50,7

Re: [RFC PATCH 2/3] drivers: misc: eeprom: at24: support reading mac eeprom from different addresses

Hallo, On Thu, Jun 29, 2017 at 02:39:10PM +0300, Claudiu Beznea wrote: > diff --git a/include/linux/platform_data/at24.h > b/include/linux/platform_data/at24.h > index 271a4e2..d55c454 100644 > --- a/include/linux/platform_data/at24.h > +++ b/include/linux/platform_data/at24.h > @@ -50,6 +50,7

Re: [RFC PATCH 2/3] drivers: misc: eeprom: at24: support reading mac eeprom from different addresses

On 06/29/2017 06:39 AM, Claudiu Beznea wrote: Add support for reading from different offsets of EEPROM. The offset is initialized via device tree. If nothing is given as input the old value, 0x90, is used. In this way the driver could be used as generic driver for different vendor memories by

Re: [RFC PATCH 2/3] drivers: misc: eeprom: at24: support reading mac eeprom from different addresses

On 06/29/2017 06:39 AM, Claudiu Beznea wrote: Add support for reading from different offsets of EEPROM. The offset is initialized via device tree. If nothing is given as input the old value, 0x90, is used. In this way the driver could be used as generic driver for different vendor memories by

Re: [RFC PATCH 2/3] drivers: misc: eeprom: at24: support reading mac eeprom from different addresses

On Thu, Jun 29, 2017 at 02:56:03PM +0300, Andy Shevchenko wrote: > On Thu, Jun 29, 2017 at 2:39 PM, Claudiu Beznea > wrote: > > Add support for reading from different offsets of EEPROM. > > The offset is initialized via device tree. If nothing is > > given as input

Re: [RFC PATCH 2/3] drivers: misc: eeprom: at24: support reading mac eeprom from different addresses

On Thu, Jun 29, 2017 at 02:56:03PM +0300, Andy Shevchenko wrote: > On Thu, Jun 29, 2017 at 2:39 PM, Claudiu Beznea > wrote: > > Add support for reading from different offsets of EEPROM. > > The offset is initialized via device tree. If nothing is > > given as input the old value, 0x90, is used.

Re: [RFC PATCH 2/3] drivers: misc: eeprom: at24: support reading mac eeprom from different addresses

On Thu, Jun 29, 2017 at 2:39 PM, Claudiu Beznea wrote: > Add support for reading from different offsets of EEPROM. > The offset is initialized via device tree. If nothing is > given as input the old value, 0x90, is used. In this way > the driver could be used as

Re: [RFC PATCH 2/3] drivers: misc: eeprom: at24: support reading mac eeprom from different addresses

On Thu, Jun 29, 2017 at 2:39 PM, Claudiu Beznea wrote: > Add support for reading from different offsets of EEPROM. > The offset is initialized via device tree. If nothing is > given as input the old value, 0x90, is used. In this way > the driver could be used as generic driver for different >

[RFC PATCH 2/3] drivers: misc: eeprom: at24: support reading mac eeprom from different addresses

Add support for reading from different offsets of EEPROM. The offset is initialized via device tree. If nothing is given as input the old value, 0x90, is used. In this way the driver could be used as generic driver for different vendor memories by only changing the reading offset via device tree.

[RFC PATCH 2/3] drivers: misc: eeprom: at24: support reading mac eeprom from different addresses

Add support for reading from different offsets of EEPROM. The offset is initialized via device tree. If nothing is given as input the old value, 0x90, is used. In this way the driver could be used as generic driver for different vendor memories by only changing the reading offset via device tree.