Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934508AbbKSRaz (ORCPT ); Thu, 19 Nov 2015 12:30:55 -0500 Received: from mail-qg0-f51.google.com ([209.85.192.51]:36553 "EHLO mail-qg0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751736AbbKSRaw (ORCPT ); Thu, 19 Nov 2015 12:30:52 -0500 Subject: Re: [PATCH v2 2/5] Documentation: devicetree: Add DT bindings to eeprom_93xx46 driver. To: Rob Herring References: <1447903781-3910-1-git-send-email-cory.tusar@pid1solutions.com> <1447903781-3910-3-git-send-email-cory.tusar@pid1solutions.com> <20151119145922.GA24560@rob-hp-laptop> Cc: pawel.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, galak@codeaurora.org, agust@denx.de, gregkh@linuxfoundation.org, jic23@kernel.org, vz@mleia.com, broonie@kernel.org, afd@ti.com, andrew@lunn.ch, Chris.Healy@zii.aero, Keith.Vennel@zii.aero, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org From: Cory Tusar X-Enigmail-Draft-Status: N1110 Message-ID: <564E074A.9020600@pid1solutions.com> Date: Thu, 19 Nov 2015 12:30:50 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <20151119145922.GA24560@rob-hp-laptop> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2789 Lines: 88 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/19/2015 09:59 AM, Rob Herring wrote: > On Wed, Nov 18, 2015 at 10:29:38PM -0500, Cory Tusar wrote: >> This commit documents bindings to be added to the eeprom_93xx46 driver >> which will allow: >> >> - Device word size and read-only attributes to be specified. >> - A device-specific compatible string for use with Atmel AT93C46D >> EEPROMs. >> - Specifying a GPIO line to function as a 'select' or 'enable' signal >> prior to accessing the EEPROM. >> >> Signed-off-by: Cory Tusar > > One nit, but: > > Acked-by: Rob Herring > >> --- >> .../devicetree/bindings/misc/eeprom-93xx46.txt | 25 ++++++++++++++++++++++ >> 1 file changed, 25 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/misc/eeprom-93xx46.txt b/Documentation/devicetree/bindings/misc/eeprom-93xx46.txt >> new file mode 100644 >> index 0000000..8e116a1 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/misc/eeprom-93xx46.txt >> @@ -0,0 +1,25 @@ >> +EEPROMs (SPI) compatible with Microchip Technology 93xx46 family. >> + >> +Required properties: >> +- compatible : shall be one of: >> + "atmel,at93c46d" >> + "eeprom-93xx46" >> +- data-size : number of data bits per word (either 8 or 16) >> + >> +Optional properties: >> +- read-only : parameter-less property which disables writes to the EEPROM >> +- select-gpios : if present, specifies the GPIO that will be asserted prior to >> + each access to the EEPROM (e.g. for SPI bus multiplexing) >> + >> +Property rules described in Documentation/devicetree/bindings/spi/spi-bus.txt >> +apply. In particular, "reg" and "spi-max-frequency" properties must be given. >> + >> +Example: >> + 93c46c@0 { > > This should be eeprom@0. Easy enough. Will fix for v3. Thanks. >> + compatible = "eeprom-93xx46"; >> + reg = <0>; >> + spi-max-frequency = <1000000>; >> + spi-cs-high; >> + data-size = <8>; >> + select-gpios = <&gpio4 4 GPIO_ACTIVE_HIGH>; >> + }; >> -- >> 2.4.10 >> - -- Cory Tusar Principal PID 1 Solutions, Inc. "There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies." --Sir Charles Anthony Richard Hoare -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlZOB0oACgkQHT1tsfGwHJ9EigCfUGD754C+nIpu5/bvnprFt1gF DDYAn1KkIYfk6Tp5X1eqfn2OirGHVLTe =PLGL -----END PGP SIGNATURE----- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/