[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210609155037.glkvwomea66dlrww@earth.universe>
Date: Wed, 9 Jun 2021 17:50:37 +0200
From: Sebastian Reichel <sebastian.reichel@...labora.com>
To: Mark Brown <broonie@...nel.org>
Cc: Rob Herring <robh+dt@...nel.org>, Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <kernel@...gutronix.de>,
Fabio Estevam <festevam@...il.com>, Ian Ray <ian.ray@...com>,
linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
devicetree@...r.kernel.org, kernel@...labora.com
Subject: Re: [PATCHv3 3/5] dt-bindings: misc: ge-achc: Convert to DT schema
format
Hi,
On Wed, Jun 09, 2021 at 12:47:47PM +0100, Mark Brown wrote:
> On Fri, May 28, 2021 at 01:33:45PM +0200, Sebastian Reichel wrote:
>
> > -Required SPI properties:
> > -
> > -- reg : Should be address of the device chip select within
> > - the controller.
>
> There is an existing binding...
>
> > + reg:
> > + minItems: 2
> > + maxItems: 2
> > + items:
> > + - description: Control interface
> > + - description: Firmware programming interface
>
> ...but this new one is incompatible with it.
The current binding is broken, since it uses the same compatible
value for two different SPI "devices" (main SPI interface and
EzPort). It only "works" because compatible string is only used
to export the device to userspace via spidev and otherwise ignored.
But the main spidev is not used by current FW and FW update cannot
be done from userspace because it requires reset pin handling during
spi transactions. So basically upstream support for this binding is
completley broken anyways (downstream has additional patches to work
around the limitations).
In PATCHv2 it was pointed out, that there should be one device for
both chip selects, since the reset/clocks/... are shared.
-- Sebastian
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists