From: Sean Wang <sean.wang@mediatek.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
driverdev-devel@linuxdriverproject.org,
Sergio Paracuellos <sergio.paracuellos@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
linux-mediatek@lists.infradead.org, NeilBrown <neil@brown.name>
Subject: Re: [PATCH 1/2] gpio: mediatek: add driver for MT7621
Date: Mon, 11 Jun 2018 11:29:29 +0800 [thread overview]
Message-ID: <1528687769.21593.19.camel@mtkswgap22> (raw)
In-Reply-To: <CACRpkdaw9O6TbZie5AOTmQJ9-3=yHETFFX7YVkPBEL72EZzZ=g@mail.gmail.com>
Hi,
On Fri, 2018-06-08 at 13:59 +0200, Linus Walleij wrote:
> Hi Sergio!
>
> Thanks for your patch!
>
> Given that we have combined pin control and GPIO drivers for
> almost all Mediatek chips in drivers/pinctrl/mediatek/*
> I would ideally like to have some input from the Mediatek
> maintainers (especially Sean Wang) on this, especially:
>
> - Is MT7621 a non-pincontrol GPIO controller, or can it
> eventually use pin control as a back-end? Will a separate
> pin control driver appear later for this SoC?
>
MT7621 also have the circuit for pad setup tweaking Tx driving and mux
setup switching to either gpio mode or specific hardware mode, but the
circuit for all of them is being accessed in a different register range
from gpio controller being implemented here.
the part of pad or mux control for MT7621 I thought that is really
simple, so it seems worth joining pinmux and pinconf together into a
single driver to become a full function about pin setup.
> - Would it make sense to have a combined driver just like
> for the other Mediatek SoCs in drivers/pinctrl/mediatek?
> If this GPIO controller does not do pin control I understand
> why it is submitted as a GPIO driver only.
>
> drivers/pinctrl/mediatek/pinctrl-mt7622.c is suspiciously
> similarly named. Is this a relative or just as different as
> night and day?
>
The MT7621 is just as completely different as night and day from MT7622.
MT7622 pinctrl originate from MediaTek IPs but MT7621 pinctrl originate
from Ralink IPs and even MT7621 should be the last one machine using the
Ralink pinctrl IPs. And for these machine MT762x appearing later MT7622,
they all will be developed based on pinctrl-mt7622 architecture .
> Also you can see that this driver has a built-in GPIO driver,
> using an external interrupt.
>
> On Sat, Jun 2, 2018 at 9:30 AM, Sergio Paracuellos
[ ... ]
> I guess you want to use
> builtin_platform_driver()?
>
> Yours,
> Linus Walleij
next prev parent reply other threads:[~2018-06-11 3:29 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 [this message]
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
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=1528687769.21593.19.camel@mtkswgap22 \
--to=sean.wang@mediatek.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=linux-mediatek@lists.infradead.org \
--cc=neil@brown.name \
--cc=robh+dt@kernel.org \
--cc=sergio.paracuellos@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).