Re: [PATCH RFC v2 3/5] pinctrl: mediatek: common: Expose more configurations to GPIO set_config
Nícolas F. R. A. Prado <[email protected]>
| Newsgroups | dev.linux.lists.kernelci,org.infradead.lists.linux-arm-kernel,org.infradead.lists.linux-mediatek,org.kernel.vger.linux-gpio,org.kernel.vger.linux-kernel,org.kernel.vger.linux-kselftest |
|---|---|
| Message-ID | <4ed22f25-ad10-461c-be68-8472590db44d@notapiano> |
On Fri, Nov 01, 2024 at 03:54:58PM +0800, Chen-Yu Tsai wrote: > On Sat, Oct 26, 2024 at 5:16 AM Nícolas F. R. A. Prado > <[email protected]> wrote: > > > > Currently the set_config callback in the gpio_chip registered by the > > pinctrl-mtk-common driver only supports configuring a single parameter > > on specific pins (the input debounce of the EINT controller, on pins > > that support it), even though many other configurations are already > > implemented and available through the pinctrl API for configuration of > > pins by the Devicetree and other drivers. > > > > Expose all configurations currently implemented through the GPIO API so > > they can also be set from userspace, which is particularly useful to > > allow testing them from userspace. Signed-off-by: Nícolas F. R. A. Prado <[email protected]> > > Missing signed-off-by? Huh, I don't know how the pre-send checks didn't catch it, will take a look, thanks for pointing it out! I've added the SoB above so it can still be merged if no further versions are required. Thanks, Nícolas