[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aSdBt937C6Cjj_8s@black.igk.intel.com>
Date: Wed, 26 Nov 2025 19:06:47 +0100
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: Lei Xue <lei.xue@...iatek.com>
Cc: Sean Wang <sean.wang@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org,
linux-gpio@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
yong.mao@...iatek.com, qingliang.li@...iatek.com,
Fred-WY.Chen@...iatek.com, ot_cathy.xu@...iatek.com,
ot_shunxi.zhang@...iatek.com, ot_yaoy.wang@...iatek.com,
ot_ye.wang@...iatek.com
Subject: Re: [PATCH 1/3] pinctrl: mediatek: Add gpio-range record in pinctrl
driver
On Tue, Nov 25, 2025 at 10:36:34AM +0800, Lei Xue wrote:
> Kernel GPIO subsystem mapping hardware pin number to a different
> range of gpio number. Add gpio-range structure to hold
> the mapped gpio range in pinctrl driver. That enables the kernel
> to search a range of mapped gpio range against a pinctrl device.
...
> static int mtk_build_gpiochip(struct mtk_pinctrl *hw)
> {
> struct gpio_chip *chip = &hw->chip;
> if (ret < 0)
> return ret;
>
> + mtk_pinctrl_gpio_range_init(hw, chip);
> +
> return 0;
We have a callback for that in struct gpio_chip. Any reason not to use it?
> }
...
> + pinctrl_add_gpio_range(hw->pctrl, &hw->range);
Not sure if this is needed.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists