Messages in this thread | | | Date | Tue, 30 Oct 2012 11:46:17 -0700 | From | David Daney <> | Subject | Re: [PATCH] i2c-EEPROM: Export memory accessor |
| |
On 10/31/2012 08:56 AM, Pantelis Antoniou wrote: > Various platforms need access to the EEPROM in other > places besides their platform registration callbacks. > Export the memory accessor to the i2c_client
i2c_clients are *not* intrinsically memory, so adding this to the generic i2c_client structure doesn't really make sense. What would the semantics of this interface be with respect to temperature sensors and GPIO expanders?
NACK.
> and implement > it for the at24 driver. > > And before you ask, no, the platform callback can't be used > for anything that depends on DT.
Why can't you just allocate (and populate) a struct at24_platform_data for the device if it isn't supplied by whatever created the device?
| |