[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqJeod3Rm4K_7c3AcH8A4aMKKmT97CcbGpRbG4b0yWzrXA@mail.gmail.com>
Date: Mon, 1 Jun 2020 11:08:37 -0600
From: Rob Herring <robh+dt@...nel.org>
To: Wolfram Sang <wsa@...-dreams.de>
Cc: Serge Semin <Sergey.Semin@...kalelectronics.ru>,
Devicetree Compiler <devicetree-compiler@...r.kernel.org>,
Serge Semin <fancer.lancer@...il.com>,
Alexey Malahov <Alexey.Malahov@...kalelectronics.ru>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
Jarkko Nikula <jarkko.nikula@...ux.intel.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Frank Rowand <frowand.list@...il.com>,
devicetree@...r.kernel.org, Linux I2C <linux-i2c@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] check: Add 10bit/slave i2c reg flags support
On Sat, May 30, 2020 at 3:32 AM Wolfram Sang <wsa@...-dreams.de> wrote:
>
>
> > + addr = reg & 0x3FFFFFFFU;
> > + snprintf(unit_addr, sizeof(unit_addr), "%x", addr);
>
> Hmm, this hardcoded value will not work if we ever need to add another
> bit. I hope this will never happen, though.
I had this concern and requested the first time this was submitted
(and abandoned) to just mask out the top byte. However, Joel's version
of this fix[1] does some actual checks on 10-bit addressing, so I've
dropped that request.
> > + if ((reg & (1U << 31)) && addr > 0x3ff)
>
> Same here with bit 31. I haven't checked DTC but can't we import the
> header with the defines into the project? Or is this then a circular
> dependency?
Easier to just duplicate the define here which Joel's patches do.
Rob
[1] https://www.spinics.net/lists/devicetree-compiler/msg03196.html
Powered by blists - more mailing lists