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 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
