On 07/04/15 18:46, Mark Brown wrote:

On Tue, Apr 07, 2015 at 06:35:49PM +0100, Srinivas Kandagatla wrote:

quoted

On 06/04/15 16:04, Matt Porter wrote:

quoted

On Mon, Apr 06, 2015 at 09:11:05AM -0500, Rob Herring wrote:

quoted

quoted

quoted

quoted

The generic binding could really use a "read-only" property here as this
is a common hardware attribute for many nvmem devices. A serial EEPROM

quoted

Correct me If am wrong.

quoted

Regarding write protection/read-only, regmap already has provisions to
support this feature. regmap would bail out with errors if any attempt to
write to non-writable regions. It all depends on the data providers how they
setup the regmap and the bindings for those are specific individual data
providers I think.

There is the ability to flag read/write permissions in regmap but I
think there's some suggestion that this should be exposed to userspace
so that it's easier for it to handle things rather than just writing
then coping with any errors.

Yes, That's possible if the data provider use the "read-only" generic 
binding like MTD partitions which the eeprom framwork could use to set 
the binary file mode appropriately.

"read-only" property seems to be more generic for all types of data 
providers.

I will give it a try and document this in the bindings too in next version.

--srini