From: Stephen Warren <swarren@wwwdotorg.org>
To: Christian Daudt <csd@broadcom.com>
Cc: Device Tree List <devicetree@vger.kernel.org>,
Linaro Patches <patches@linaro.org>,
Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@arm.com>,
Linus Walleij <linus.walleij@linaro.org>,
Markus Mayer <markus.mayer@linaro.org>,
Tim Kryger <tim.kryger@linaro.org>,
Markus Mayer <mmayer@broadcom.com>,
Matt Porter <matt.porter@linaro.org>,
ARM Kernel List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v9 1/3] gpio: bcm281xx: Add GPIO driver
Date: Tue, 10 Sep 2013 16:17:54 -0600 [thread overview]
Message-ID: <522F9A92.1040205@wwwdotorg.org> (raw)
In-Reply-To: <522F8BB0.6010301@broadcom.com>
On 09/10/2013 03:14 PM, Christian Daudt wrote:
> Hi Stephen,
> On 13-09-10 01:02 PM, Stephen Warren wrote:
>> On 09/10/2013 12:07 PM, Markus Mayer wrote:
>>> From: Markus Mayer <mmayer@broadcom.com>
>>>
>>> Add the GPIO driver for the Broadcom bcm281xx family of mobile SoCs.
>>> These GPIO controllers may contain up to 8 banks where each bank
>>> includes 32 pins that can be driven high or low and act as an edge
>>> sensitive interrupt.
>> The binding,
>> Reviewed-by: Stephen Warren <swarren@nvidia.com>
>>
>> although ...
>>
>>> diff --git a/Documentation/devicetree/bindings/gpio/gpio-bcm-kona.txt
>>> b/Documentation/devicetree/bindings/gpio/gpio-bcm-kona.txt
>>> +This GPIO driver is used in the following Broadcom SoCs:
>>> + BCM11130, BCM11140, BCM11351, BCM28145, BCM28155
>> Given that, I would expect the documentation of the compatible property
>> to enumerate the compatible values for all of those different chips,
>> although the driver could choose to only bind to e.g. brcm,bcm11351-gpio
>> or brcm,kona-gpio, since they're all compatible with it.
>>
> How would this help ? All of these chips are part of the same family and
> thus quite similar (the primary difference being on the memory
> controller and packaging), and we can't know a priori on which
> variations bugs will happen, if any.
That's exactly why the DT should include a compatible value that
precisely describes the chip; so that information is there if it's
needed in the future.
next prev parent reply other threads:[~2013-09-10 22:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 18:07 [PATCH v9 0/3] gpio: bcm281xx: GPIO driver Markus Mayer
2013-09-10 18:07 ` [PATCH v9 1/3] gpio: bcm281xx: Add " Markus Mayer
2013-09-10 20:02 ` Stephen Warren
2013-09-10 21:14 ` Christian Daudt
2013-09-10 22:17 ` Stephen Warren [this message]
[not found] ` <1378836423-12467-2-git-send-email-markus.mayer-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-09-20 18:28 ` Linus Walleij
2013-09-10 18:07 ` [PATCH v9 2/3] ARM: bcm281xx: Enable " Markus Mayer
2013-09-10 22:32 ` Christian Daudt
[not found] ` <1378836423-12467-3-git-send-email-markus.mayer-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-09-20 18:32 ` Linus Walleij
2013-09-10 18:07 ` [PATCH v9 3/3] ARM: bcm281xx: Add device node for the GPIO controller Markus Mayer
2013-09-10 22:32 ` Christian Daudt
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=522F9A92.1040205@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=Sudeep.KarkadaNagesha@arm.com \
--cc=csd@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=markus.mayer@linaro.org \
--cc=matt.porter@linaro.org \
--cc=mmayer@broadcom.com \
--cc=patches@linaro.org \
--cc=tim.kryger@linaro.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;
as well as URLs for NNTP newsgroup(s).