[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3a07d0d9fbe7178bbe9efa99fcb331df213a461f.camel@linux.intel.com>
Date: Tue, 26 Jun 2018 16:23:22 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Bartosz Golaszewski <brgl@...ev.pl>
Cc: alanx.chiang@...el.com, linux-i2c <linux-i2c@...r.kernel.org>,
andy.yeh@...el.com, Sakari Ailus <sakari.ailus@...ux.intel.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
On Tue, 2018-06-26 at 14:36 +0200, Bartosz Golaszewski wrote:
> 2018-06-26 14:14 GMT+02:00 Andy Shevchenko
> <andriy.shevchenko@...ux.intel.com>:
> > On Tue, 2018-06-26 at 09:41 +0200, Bartosz Golaszewski wrote:
> > > 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?
> >
> > The current at24 driver has no address width support,
> > thus, reusing same
> > (allocated) IDs (non-DT case) is hard.
^^^^^
> Every supported compatible has the width already specified in its
> corresponding chip data.
Please, read again carefully what I wrote before.
--
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Intel Finland Oy
Powered by blists - more mailing lists