From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] bcma: use device from DT (brcm, bus-gpio) for SoC GPIO chip
Date: Sat, 27 Sep 2014 00:03:18 +0200 [thread overview]
Message-ID: <2539898.4te2VKk57a@wuerfel> (raw)
In-Reply-To: <1411741733-13888-1-git-send-email-zajec5@gmail.com>
On Friday 26 September 2014 16:28:53 Rafa? Mi?ecki wrote:
> +The top-level axi bus may contain following children:
> +
> +- gpio: GPIO chip on the SoC
> +
> + Required properties:
> + - compatible: "brcm,bus-gpio"
> + - gpio-controller : makes the node a GPIO controller
> + - #gpio-cells : size of the GPIO specifier, must be 2
> +
>
I wonder if it would be better to avoid the subnode here and just
make the parent itself the gpio controller.
Is the gpio controller part of the bus itself in reality, or is it
a device that gets probed on the bus?
Arnd
next prev parent reply other threads:[~2014-09-26 22:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 14:28 [PATCH] bcma: use device from DT (brcm,bus-gpio) for SoC GPIO chip Rafał Miłecki
2014-09-26 22:03 ` Arnd Bergmann [this message]
2014-09-27 8:05 ` [PATCH] bcma: use device from DT (brcm, bus-gpio) " Rafał Miłecki
2014-09-27 8:33 ` [PATCH] bcma: use device from DT (brcm,bus-gpio) " Hauke Mehrtens
2014-09-27 10:37 ` [PATCH] bcma: use device from DT (brcm, bus-gpio) " Rafał Miłecki
2014-09-27 20:47 ` [PATCH] bcma: use device from DT (brcm,bus-gpio) " Hauke Mehrtens
2014-09-28 8:24 ` [PATCH V2] bcma: use device from DT (brcm, bus-gpio) " Rafał Miłecki
2014-09-30 9:37 ` Arnd Bergmann
2014-09-30 9:56 ` Rafał Miłecki
2014-09-30 10:28 ` Arnd Bergmann
2014-09-30 10:22 ` [PATCH V3] bcma: use device from DT (brcm, bus-chipcommon) " Rafał Miłecki
2014-09-30 10:36 ` Arnd Bergmann
2014-09-30 10:41 ` Rafał Miłecki
2014-09-30 10:55 ` [PATCH V4] bcma: use chipcommon node from DT " Rafał Miłecki
2014-09-30 11:08 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2539898.4te2VKk57a@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox