On Tue, May 6, 2014 at 12:02 AM, Olof Johansson <olof@xxxxxxxxx> wrote: > ... or is there some underlying reason for having the two-layer > approach that isn't obvious from this device tree? There is, as explained by Alan. One coherent memory range with several individual ports. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 1/7] ARM: dts: socfpga: add gpio pieces
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH 1/7] ARM: dts: socfpga: add gpio pieces
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Tue, 13 May 2014 10:45:24 +0200
- In-reply-to: <CAOesGMi_0fT4UbfGUp9jkrwYMXgfxC5gmXOBviU9PjAutPdHiw@mail.gmail.com>
- References:
- dwapb: a bug fix a few cleanups, v2
- From: Sebastian Andrzej Siewior
- [PATCH 1/7] ARM: dts: socfpga: add gpio pieces
- From: Sebastian Andrzej Siewior
- Re: [PATCH 1/7] ARM: dts: socfpga: add gpio pieces
- From: Olof Johansson
- dwapb: a bug fix a few cleanups, v2
- Prev by Date: Re: [PATCH] GPIOD, OF: parse flags into gpiod
- Next by Date: Re: [PATCH 1/2] gpio: omap: prepare and unprepare the debounce clock
- Previous by thread: Re: [PATCH 1/7] ARM: dts: socfpga: add gpio pieces
- Next by thread: [PATCH 5/7] gpio: dwapb: use irq_gc_lock() for locking instead bc's lock
- Index(es):
 |