RE: [PATCH 1/3] dt-bindings: add "size" property.

["Mohandass, Divagar" <divagar.mohandass@intel.com>]

>-----Original Message-----
>From: Rob Herring [mailto:robh@kernel.org]
>Sent: Friday, August 04, 2017 1:58 AM
>To: Mohandass, Divagar <divagar.mohandass@intel.com>
>Cc: mark.rutland@arm.com; wsa@the-dreams.de;
>devicetree@vger.kernel.org; linux-i2c@vger.kernel.org; linux-
>kernel@vger.kernel.org; Mani, Rajmohan <rajmohan.mani@intel.com>
>Subject: Re: [PATCH 1/3] dt-bindings: add "size" property.
>
>On Thu, Jul 27, 2017 at 10:13:07PM +0530, divagar.mohandass@intel.com
>wrote:
>> From: Divagar Mohandass <divagar.mohandass@intel.com>
>
>Please improve the subject. Add size to what?

I will update the title to say 'add eeprom "size" property' in the next version.

>
>>
>> This adds "size" as optional property for i2c eeproms.
>>
>> "size" should be mentioned in byte and it should refer to the eeprom
>> size. This will be read by the driver and used to calculating the
>> number of bytes in read/write calls.
>>
>> Signed-off-by: Divagar Mohandass <divagar.mohandass@intel.com>
>> ---
>>  Documentation/devicetree/bindings/eeprom/eeprom.txt | 2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/eeprom/eeprom.txt
>> b/Documentation/devicetree/bindings/eeprom/eeprom.txt
>> index 5696eb5..1436569 100644
>> --- a/Documentation/devicetree/bindings/eeprom/eeprom.txt
>> +++ b/Documentation/devicetree/bindings/eeprom/eeprom.txt
>> @@ -32,6 +32,8 @@ Optional properties:
>>
>>    - read-only: this parameterless property disables writes to the
>> eeprom
>>
>> +  - size: total eeprom size in bytes
>> +
>
>This should be implied by the compatible string of the eeprom. Why do you
>need this?

This eeprom "size" property is optional for at24 driver, 
In the at24 driver size information is passed as part of the i2c_device_id' 
driver_data during initial probe. If you want to use an existing ID for an 
eeprom for a different size, there is no way to override it currently. 
By introducing an optional size device property, we can reuse IDs for chips of
different sizes.

This is also consistent with the implementation in the at25 driver.

>
>Rob