Re: [RESEND PATCH 0/9] eeprom: at24: at24cs series serial number read

2015-10-21 Thread Bartosz Golaszewski
2015-10-21 16:23 GMT+02:00 Peter Korsgaard : >> "Bartosz" == Bartosz Golaszewski writes: > > >> As the serial number is available on a separate i2c address, wouldn't > >> it be simpler to handle these as special (read only) device variants and

Re: [RESEND PATCH 0/9] eeprom: at24: at24cs series serial number read

2015-10-21 Thread Peter Korsgaard
> "Bartosz" == Bartosz Golaszewski writes: Hi, >> > I wanted to respond that this way we would not be protected from >> > concurrent accesses, but then I saw I didn't actually include any >> > locks in the serial read function - my bad. It needs to be fixed as

Re: [RESEND PATCH 0/9] eeprom: at24: at24cs series serial number read

2015-10-21 Thread Peter Korsgaard
> "Bartosz" == Bartosz Golaszewski writes: >> As the serial number is available on a separate i2c address, wouldn't >> it be simpler to handle these as special (read only) device variants and >> instantiate E.G. a 24c64 (for the normal data) and a 24cs64 (for

Re: [RESEND PATCH 0/9] eeprom: at24: at24cs series serial number read

2015-10-21 Thread Bartosz Golaszewski
2015-10-21 13:03 GMT+02:00 Peter Korsgaard : >> "Bartosz" == Bartosz Golaszewski writes: > > > Chips from the at24cs EEPROM series have an additional read-only memory > area > > containing a factory pre-programmed serial number. In order to

Re: [RESEND PATCH 0/9] eeprom: at24: at24cs series serial number read

2015-10-21 Thread Peter Korsgaard
> "Bartosz" == Bartosz Golaszewski writes: > Chips from the at24cs EEPROM series have an additional read-only memory area > containing a factory pre-programmed serial number. In order to access it, a > dummy write must be executed before reading the serial