linux-kernel - Re: [PATCH v2 0/2] Add a property in at24.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ff4c668d0807657940a4cddc6f7eb63d19be327c.camel@linux.intel.com>
Date:   Tue, 26 Jun 2018 15:14:26 +0300
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Bartosz Golaszewski <brgl@...ev.pl>, alanx.chiang@...el.com
Cc:     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 09:41 +0200, Bartosz Golaszewski wrote:
> 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?

The current at24 driver has no address width support, thus, reusing same
(allocated) IDs (non-DT case) is hard.

-- 
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Intel Finland Oy