On Fri, Jan 28, 2022 at 4:51 PM Linus Walleij <linus.walleij@xxxxxxxxxx> wrote: > On Wed, Jan 26, 2022 at 3:59 PM Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote: > > On Mon, Apr 12, 2021 at 2:24 PM Linus Walleij <linus.walleij@xxxxxxxxxx> wrote: > > > > interrupts: > > > + description: interrupt line(s) connected to the DRDY line(s) and/or the > > > + Intertial interrupt lines INT1 and INT2 if these exist. This means up to > > > + three interrupts, and the DRDY must be the first one if it exists on > > > > So this says three (the LSM9DS0 datasheet agrees)... > > > > > + the package. The trigger edge of the interrupts is sometimes software > > > + configurable in the hardware so the operating system should parse this > > > + flag and set up the trigger edge as indicated in the device tree. > > > minItems: 1 > > > + maxItems: 2 > > > > ... while this says two? > > Looks like a bug, could you send a patch? (I'm a bit preoccupied right now.) Oh wait a minute, LSM9DS0 is one of those with more than one component inside it isn't it? While it is a bit awkward, we do bindings per-subcomponent on these, so for example lsm330dlc registers as "st,lsm330dlc-accel" and "st,lsm330dlc-gyro" and it makes a bit of sense because they each have different I2C addresses as well. I see it as two components just sharing a physical package rather than one component in a package. So the IRQs are per-subcomponent, not for the entire package. Does this influence the situation you have with LSM9DS0? Yours, Linus Walleij
