From: Hauke Mehrtens <hauke@hauke-m.de>
To: "Rafał Miłecki" <zajec5@gmail.com>, "Arnd Bergmann" <arnd@arndb.de>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"John W. Linville" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] bcma: use device from DT (brcm,bus-gpio) for SoC GPIO chip
Date: Sat, 27 Sep 2014 10:33:37 +0200 [thread overview]
Message-ID: <54267661.5000401@hauke-m.de> (raw)
In-Reply-To: <CACna6rwwfJOdnxhmnW7MUuUC1YBPx8bmDbiaSy1+G39hF4p7OA@mail.gmail.com>
On 09/27/2014 10:05 AM, Rafał Miłecki wrote:
> On 27 September 2014 00:03, Arnd Bergmann <arnd@arndb.de> wrote:
>> 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?
>
> I'm not sure how to treat this chip.
> We control GPIOs using ChipCommon regs (and ChipCommon is one of
> cores/devices on the bus), so you could also consider GPIO chip a
> sub-device of ChipCommon.
> I believe every Broadcom bus has a GPIO chip. In the ancient (MIPS)
> times, even if we didn't have ChipCommon, there was an EXTIF core that
> used to provide access to the GPIO chip.
>
> What do you think? Should I make it separated device, even it if
> depends on the SoC and its ChipCommon core (device)?
>
I would make GPIO a subdevive of chipcommon. The chipcommon core has an
own IRQ which is also used for GPIO.
Hauke
next prev parent reply other threads:[~2014-09-27 8:33 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
2014-09-27 8:05 ` Rafał Miłecki
2014-09-27 8:33 ` Hauke Mehrtens [this message]
2014-09-27 10:37 ` Rafał Miłecki
2014-09-27 20:47 ` Hauke Mehrtens
2014-09-28 8:24 ` [PATCH V2] " Rafał Miłecki
2014-09-30 9:37 ` [PATCH V2] bcma: use device from DT (brcm, bus-gpio) " 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 ` [PATCH V3] bcma: use device from DT (brcm, bus-chipcommon) " 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=54267661.5000401@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=zajec5@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).