From mboxrd@z Thu Jan 1 00:00:00 1970 From: broonie@kernel.org (Mark Brown) Date: Tue, 7 Apr 2015 18:46:24 +0100 Subject: [PATCH v4 05/10] eeprom: Add bindings for simple eeprom framework In-Reply-To: <55241575.7040809@linaro.org> References: <1427752492-17039-1-git-send-email-srinivas.kandagatla@linaro.org> <1427752679-17261-1-git-send-email-srinivas.kandagatla@linaro.org> <20150406133208.GH30984@beef> <20150406150442.GA26319@beef> <55241575.7040809@linaro.org> Message-ID: <20150407174624.GO6023@sirena.org.uk> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tue, Apr 07, 2015 at 06:35:49PM +0100, Srinivas Kandagatla wrote: > On 06/04/15 16:04, Matt Porter wrote: > >On Mon, Apr 06, 2015 at 09:11:05AM -0500, Rob Herring wrote: > >>>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 > Correct me If am wrong. > 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. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: Digital signature URL: