[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdWFzJ-PfFQz-mgbtYdV9d_8=mr+F51=1Jhx0K-HrGrwFg@mail.gmail.com>
Date: Fri, 24 Jan 2014 14:05:46 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Mark Rutland <mark.rutland@....com>
Cc: Mark Brown <broonie@...nel.org>,
"linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
"linux-sh@...r.kernel.org" <linux-sh@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Geert Uytterhoeven <geert+renesas@...ux-m68k.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH v4 13/14] spi: rspi: Add DT support
On Fri, Jan 24, 2014 at 10:33 AM, Mark Rutland <mark.rutland@....com> wrote:
>> +- interrupts : 1 interrupt for RSPI cores using a single multiplexed
>> + interrupt,
>> + 3 interrupts (SPEI, SPRI, SPTI) for RSPI cores using
>> + separate interrupts.
>> +- interrupt-names : Array of strings associated with the interrupt numbers:
>> + "error" for SPEI, "rx" for SPRI, and "tx" for SPTI.
>> + For RSPI cores using a single multiplexed interrupt, the
>> + name "mux" is optional.
>
> Rather than defining the set of interrupts twice, it would be nice to
> have interrupts defined in terms of interrupt-names:
>
> - interrupts: a list of interrupt-specifiers, one for each entry in
> interrupt-names. If interrupt-names is not present, an interrupt
> specifier for a single muxed interrupt.
>
> - interrupt-names: A list of interrupt names. Should contain (if
> present):
> * "error" for SPEI
> * "rx" for SPRI
> * "tx" to SPTI
> * "mux" for a single muxed interrupt
Yes, that sounds much better, thank you.
Will update.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists