[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMRc=Me-Tm8Q5_hGu2r1uqeYFAvCM9ssr7o=w1KZUyXcAn_uCw@mail.gmail.com>
Date: Tue, 26 Jun 2018 09:41:26 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: alanx.chiang@...el.com
Cc: linux-i2c <linux-i2c@...r.kernel.org>, andy.yeh@...el.com,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
andriy.shevchenko@...el.com, rajmohan.mani@...el.com,
Andy Shevchenko <andy.shevchenko@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/2] Add a property in at24.c
2018-06-26 8:22 GMT+02:00 <alanx.chiang@...el.com>:
> From: "alanx.chiang" <alanx.chiang@...el.com>
>
> In at24.c, it uses 8-bit addressing by default. In this patch,
> add a property address-width that provides a flexible method to
> pass the information to the driver.
>
> alanx.chiang (2):
> dt-bindings: at24: Add address-width property
> eeprom: at24: Add support for address-width property
>
> Documentation/devicetree/bindings/eeprom/at24.txt | 2 ++
> drivers/misc/eeprom/at24.c | 16 ++++++++++++++++
> 2 files changed, 18 insertions(+)
>
> --
> 2.7.4
>
What is your use case exactly? Do you have an EEPROM model that's not
yet supported explicitly in the driver? Why would you need this
option?
Best regards,
Bartosz Golaszewski
Powered by blists - more mailing lists