From: Chris Healy <Chris.Healy@zii.aero>
To: CoryTusar <cory.tusar@pid1solutions.com>,
        "robh+dt@kernel.org" <robh+dt@kernel.org>,
        "pawel.moll@arm.com" <pawel.moll@arm.com>,
        "mark.rutland@arm.com" <mark.rutland@arm.com>,
        "ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
        "galak@codeaurora.org" <galak@codeaurora.org>,
        "agust@denx.de" <agust@denx.de>,
        "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
CC: "jic23@kernel.org" <jic23@kernel.org>, "vz@mleia.com" <vz@mleia.com>,
        "broonie@kernel.org" <broonie@kernel.org>, "afd@ti.com" <afd@ti.com>,
        "andrew@lunn.ch" <andrew@lunn.ch>,
        Keith Vennel <Keith.Vennel@zii.aero>,
        "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/5] Devicetree support for misc/eeprom/eeprom_93xx46.
Thread-Topic: [PATCH v3 0/5] Devicetree support for misc/eeprom/eeprom_93xx46.
Thread-Index: AQHRJ0J7chk53kPSsk6slaensQUXc560z5pP
Date: Mon, 30 Nov 2015 17:04:21 +0000
Message-ID: <1448903060754.7335@zii.aero>
References: <1448429452-26972-1-git-send-email-cory.tusar@pid1solutions.com>
In-Reply-To: <1448429452-26972-1-git-send-email-cory.tusar@pid1solutions.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2629
Lines: 52

On 11/25/2015 12:30 AM, Cory Tusar wrote:
> This series of patches adds an initial set of devicetree bindings to the
> eeprom_93xx46 driver which mirror the configuration options previously
> available as a platform device.  These bindings are then extended to
> include support for specific Atmel devices in this family and also to
> support GPIO-based selection of the device (e.g. for use with an SPI bus
> mux).
>
> Additionally, an address aliasing issue with 16-bit read and write
> accesses in the eeprom_93xx46 driver discovered during testing is fixed.
>
> Changes since v2:
>   - Changed node name to 'eeprom' in DT bindings example.
>   - Simplified several bits of return logic.
>   - Removed #ifdef CONFIG_OF.
>   - Allow compiler to handle promotion to bool return values.
>   - Reworked GPIO handling to use gpiod_* functions throughout (and
>     fixed an oversight where GPIO flags were being ignored).
>
> Changes since v1:
>   - Consolidated all Documentation/devictree additions into a single patch.
>   - Clarified compatible string shall be only one of the supported values.
>   - Renamed the 'select-gpio' binding to 'select-gpios'.
>
> Cory Tusar (5):
>   misc: eeprom_93xx46: Fix 16-bit read and write accesses.
>   Documentation: devicetree: Add DT bindings to eeprom_93xx46 driver.
>   misc: eeprom_93xx46: Implement eeprom_93xx46 DT bindings.
>   misc: eeprom_93xx46: Add quirks to support Atmel AT93C46D device.
>   misc: eeprom_93xx46: Add support for a GPIO 'select' line.
>
>  .../devicetree/bindings/misc/eeprom-93xx46.txt     |  25 +++
>  drivers/misc/eeprom/eeprom_93xx46.c                | 212 +++++++++++++++++----
>  include/linux/eeprom_93xx46.h                      |   9 +
>  3 files changed, 210 insertions(+), 36 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/misc/eeprom-93xx46.txt

Entire series was...

Tested-by: Chris Healy <chris.healy@zii.aero>

...on a Freescale i.MX51 platform with a Microchip 93LC46A EEPROM.

________________________________


This email and any files transmitted with it are confidential & proprietary to Systems and Software Enterprises, LLC. This information is intended solely for the use of the individual or entity to which it is addressed. Access or transmittal of the information contained in this e-mail, in full or in part, to any other organization or persons is not authorized.
--
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/