[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191203163850.GN1998@sirena.org.uk>
Date: Tue, 3 Dec 2019 16:38:50 +0000
From: Mark Brown <broonie@...nel.org>
To: Jonathan Cameron <jic23@...nel.org>
Cc: "Ardelean, Alexandru" <alexandru.Ardelean@...log.com>,
"rodrigorsdc@...il.com" <rodrigorsdc@...il.com>,
"Popa, Stefan Serban" <StefanSerban.Popa@...log.com>,
"kernel-usp@...glegroups.com" <kernel-usp@...glegroups.com>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"lars@...afoo.de" <lars@...afoo.de>,
"pmeerw@...erw.net" <pmeerw@...erw.net>,
"Hennerich, Michael" <Michael.Hennerich@...log.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"knaack.h@....de" <knaack.h@....de>
Subject: Re: [PATCH v4] dt-bindings: iio: accel: add binding documentation
for ADIS16240
On Sun, Dec 01, 2019 at 11:40:32AM +0000, Jonathan Cameron wrote:
> +CC Mark as we probably need a more general view point on
> the question of whether SPI mode should be enforced by binding
> or in the driver.
Not sure I see the question here, I think I was missing a bit of
the conversation? It's perfectly fine for a driver to specify a
mode, if the hardware always uses some unusual mode then there's
no sense in forcing every single DT to set the same mode. On the
other hand if there's some configuration for the driver that was
handling some board specific configuration that there's already
some generic SPI support for setting then it seems odd to have a
custom driver specific configuration mechanism.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists