From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
Linus Walleij <linus.walleij@linaro.org>,
driverdev-devel@linuxdriverproject.org,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
NeilBrown <neil@brown.name>
Subject: Re: [PATCH 2/2] dt-bindings: document gpio-mt7621 bindings
Date: Thu, 14 Jun 2018 06:45:39 +0200 [thread overview]
Message-ID: <20180614044539.GA8681@foobar> (raw)
In-Reply-To: <CAL_Jsq+0bnEmE2n-O3a7ecSXOsjTfZD3AqJDQunO6xzUF_W-=A@mail.gmail.com>
On Wed, Jun 13, 2018 at 01:28:35PM -0600, Rob Herring wrote:
> On Wed, Jun 13, 2018 at 10:23 AM, Sergio Paracuellos
> <sergio.paracuellos@gmail.com> wrote:
> > Hi Rob,
> >
> > Thanks for your time in reviewing this.
> >
> > On Tue, Jun 12, 2018 at 10:56 PM, Rob Herring <robh@kernel.org> wrote:
> >> On Sat, Jun 02, 2018 at 09:30:10AM +0200, Sergio Paracuellos wrote:
> >>> Add a devicetree binding documentation for the mt7621 driver.
> >>
>
> >>> + second cell specifies GPIO flags, as defined in <dt-bindings/gpio/gpio.h>.
> >>> + Only the GPIO_ACTIVE_HIGH and GPIO_ACTIVE_LOW flags are supported.
> >>> +- gpio-controller : Marks the device node as a GPIO controller.
> >>> +- reg : The id of the bank that the node describes.
> >>
> >> I'd prefer to not have banks defined in DT. Do you have a variable
> >> number or resources that are per bank? If not, then you don't need them.
> >
> > Mmmm, That's what I understood from documentation:
> >
> > "Some system-on-chips (SoCs) use the concept of GPIO banks. ...
> > Usually each such bank is
> > exposed in the device tree as an individual gpio-controller node. ..."
>
> This should be conditioned on being able to divide up the registers by
> bank which seems like you can't. Or there's the case like the DW GPIO
> block and the number of banks is configurable.
I see. Thanks for clarifing this.
>
> > If this is not a good approach, could you please me point me out to a
> > device tree example where
> > the correct approach is being used?
>
> I'm not sure offhand. There are lots of examples of single nodes I'm
> sure. Which ones have banks I haven't a clue. IIRC, there were some
> cases where the bank # was part of the GPIO cells, but I seem to
> recall Linus prefers not having 3 cells.
Ok, so... does the following single node sounds acceptable?
gpio: gpio@600 {
#gpio-cells = <2>;
#interrupt-cells = <2>;
compatible = "mediatek,mt7621-gpio";
gpio-controller;
interrupt-controller;
reg = <0x600 0x60>;
interrupt-parent = <&gic>;
interrupts = <GIC_SHARED 12 IRQ_TYPE_LEVEL_HIGH>;
mediatek,gpio-bank-widths = <32 32 32>;
}
Changing definition for "reg" and adding a new one for
"mediatek,gpio-bank-widths" as follows:
reg:
Define the base and range of the address space containing
the mediatek GPIO controller registers
mediatek,gpio-bank-widths:
Number of GPIO lines for each bank. Number of elements must
correspond to number of banks suggested by the 'reg' property.
Thanks in advance.
>
> Rob
Best regards,
Sergio Paracuellos
next prev parent reply other threads:[~2018-06-14 4:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-02 7:30 [PATCH 0/2] gpio: mediatek: driver for gpio chip in MT7621 SoC Sergio Paracuellos
2018-06-02 7:30 ` [PATCH 1/2] gpio: mediatek: add driver for MT7621 Sergio Paracuellos
2018-06-08 11:59 ` Linus Walleij
2018-06-08 12:17 ` Linus Walleij
2018-06-09 6:17 ` Sergio Paracuellos
2018-06-09 5:54 ` Sergio Paracuellos
2018-06-11 3:29 ` Sean Wang
2018-06-02 7:30 ` [PATCH 2/2] dt-bindings: document gpio-mt7621 bindings Sergio Paracuellos
2018-06-12 20:56 ` Rob Herring
2018-06-13 9:40 ` Dan Carpenter
2018-06-13 16:23 ` Sergio Paracuellos
2018-06-13 19:28 ` Rob Herring
2018-06-14 4:45 ` Sergio Paracuellos [this message]
2018-06-14 14:17 ` Linus Walleij
2018-06-14 16:20 ` Sergio Paracuellos
2018-06-14 14:14 ` Linus Walleij
2018-06-14 14:33 ` Rob Herring
2018-06-14 14:48 ` Linus Walleij
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=20180614044539.GA8681@foobar \
--to=sergio.paracuellos@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=neil@brown.name \
--cc=robh@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.