On Wed, Oct 11, 2017 at 10:35 AM, Linus Walleij <linus.walleij@xxxxxxxxxx> wrote: > On Wed, Sep 27, 2017 at 4:40 AM, Masahiro Yamada > <yamada.masahiro@xxxxxxxxxxxxx> wrote: > >> This GPIO controller is used on UniPhier SoC family. >> >> The vendor specific property "socionext,interrupt-ranges" is for >> specifying interrupt mapping to the parent interrupt controller >> because the mapping is not contiguous. It works like "ranges", >> but transforms "interrupts" instead of "reg". >> >> Signed-off-by: Masahiro Yamada <yamada.masahiro@xxxxxxxxxxxxx> >> Acked-by: Rob Herring <robh@xxxxxxxxxx> > > Patch applied. > >> +- socionext,interrupt-ranges: Specifies an interrupt number mapping between >> + this GPIO controller and its interrupt parent, in the form of arbitrary >> + number of <child-interrupt-base parent-interrupt-base length> triplets. > (...) >> + socionext,interrupt-ranges = <0 48 16>, <16 154 5>, <21 217 3>; > > Still uncertain about that thing. > > But as it is, you need running code, and we have rough consensus. > > So merging. > > If it turns out to be a bad binding we may need to patch in an alternative > later. Sorry I had to take it back out, because the <dt-bindings/*> stuff in the other patch should also be in this patch rather than in the driver. Please move that over here, and if you insist on those macros, also use them in the example so we understand how this is supposed to be used, i.e. also add a consumer node to the bindings example if it is gonna use magic macros. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
