From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [PATCH v4 05/10] eeprom: Add bindings for simple eeprom framework Date: Tue, 7 Apr 2015 18:46:24 +0100 Message-ID: <20150407174624.GO6023@sirena.org.uk> 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> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="kU+YCB/tRrGD+zr2" Return-path: Content-Disposition: inline In-Reply-To: <55241575.7040809@linaro.org> Sender: linux-kernel-owner@vger.kernel.org To: Srinivas Kandagatla Cc: Matt Porter , Rob Herring , "linux-arm-kernel@lists.infradead.org" , "devicetree@vger.kernel.org" , Arnd Bergmann , Greg Kroah-Hartman , Sascha Hauer , Stephen Boyd , "linux-kernel@vger.kernel.org" , Rob Herring , Kumar Gala , Maxime Ripard , "linux-api@vger.kernel.org" , linux-arm-msm List-Id: linux-arm-msm@vger.kernel.org --kU+YCB/tRrGD+zr2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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. --kU+YCB/tRrGD+zr2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVJBfvAAoJECTWi3JdVIfQJYsH/Ah8snDt+b0J7XauOp9qrx7N iiOJ87rZzRMlPGP/fVh7NEU2WqogDQ9kiNB9tporY/+ZTxjFp3BtRxHavuMC7/+9 f0DrJxTp9KxBCH3wYQgHf8Tjapfjf0kzQsZIGQs6iP4x5zdXTkrVTE5ukXGFHXWm xLbIFbz30+2TCXlzhckmPId7MHQsJYC+A2F1cfjyizDtu5HlXQC3Tmi/2/DnqZ+Z kwqzieafjYNCbjIgtuZSAXCejI3C+cG3o95Dhf2y27HObxamwP7KbeFf5vzUZsj/ T2WRGnhyzahCQ5zTudbx+JajK98WBy+9fh6JigCZ5JPv3jrMLX4xRs1GuQGjmIM= =Rwf7 -----END PGP SIGNATURE----- --kU+YCB/tRrGD+zr2--