Re: [PATCH] iio: st-sensors: Update ST Sensor bindings

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jul 12, 2021 at 02:56:39PM +0100, Jonathan Cameron wrote:
> On Mon, 12 Jul 2021 15:04:44 +0200
> Maxime Ripard <maxime@xxxxxxxxxx> wrote:
> 
> > Hi,
> > 
> > On Mon, Apr 12, 2021 at 02:23:31PM +0200, Linus Walleij wrote:
> > > This adjusts the ST Sensor bindings with the more fine-grained
> > > syntax checks that were proposed late in the last kernel cycle
> > > and colliding with parallel work.
> > > 
> > > Cc: devicetree@xxxxxxxxxxxxxxx
> > > Reviewed-by: Rob Herring <robh@xxxxxxxxxx>
> > > Signed-off-by: Linus Walleij <linus.walleij@xxxxxxxxxx>  
> > 
> > I'm not really sure of how I supposed to fix this, but this creates an
> > issue on the Pinephone
> > (arch/arm64/boot/dts/allwinner/sun50i-a64-pinephone-1.2.dts) that has a
> > LIS3MDL with only the DRDY pin routed and thus only has a single
> > interrupt in the DT.
> > 
> > One of the if condition in that patch enforces that there's two
> > interrupts for the LIS3MDL, but it's not really clear to me why after
> > looking at the datasheet?
> 
> It shouldn't be enforcing that 2 are specified rather that 2 'might' be
> specified.

But then you don't need that condition at all, it's already what is
being enforced by the main schema here:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/iio/st,st-sensors.yaml#n90

> maxItems is set, but not minItems. 

Yeah, and if one is missing the other is added with the value of the
other.

What the schema enforces currently is that (for the common part) the
interrupt list can be between 1 and 2 and then for a specific set of
compatibles (including the LIS3MDL) it has to be exactly 2.

Even the common part looks weird though, it says that it can handle up
to three interrupts but has maxItems: 2?

> Driver wise, at the moment it looks like we only handle one interrupt.
> So to handle selection when two are possible and either 1 or 2 might
> be wired up we need to add interrupt names (with default order so we
> don't break anything before adding them to the binding).
> 
> Would that work for this device?

I don't know the LIS3MDL to comment whether it makes sense or not, but
it looks like it's a single sensor so I'm not really sure why we'd need
more than one interrupt

Maxime

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]


  Powered by Linux