From: Michael Walle <michael@walle.cc>
To: "Andy Shevchenko" <andy@kernel.org>,
"TY_Chang[張子逸]" <tychang@realtek.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] Add GPIO support for Realtek DHC(Digital Home Center) RTD SoCs.
Date: Thu, 14 Dec 2023 15:35:18 +0100 [thread overview]
Message-ID: <0f0b3b65a838aea6797ae78c47d6af49@walle.cc> (raw)
In-Reply-To: <ZXsKAyIlY3y3tgUi@smile.fi.intel.com>
Hi,
>> >> >> This driver enables configuration of GPIO direction, GPIO values,
>> >> >> GPIO debounce settings and handles GPIO interrupts.
>> >> >
>> >> >Why gpio-regmap can't be used?
>> >>
>> >> I will try to use gpio-remap in the next version.
>> >
>> >If it appears that it makes code uglier / complicated, please add the note
>> >somewhere to answer the above question.
>>
>> I've traced the gpio-regmap.c file. It appears that for the driver to
>> register
>> gpio_irq_chip, it must create the irq_domain and add it into
>> gpio_regmap_config.
>> Additionally, the driver needs to register the irq handler by itself.
>> However, this process can be managed by the gpiolib if the driver
>> fills in the struct
>> gpio_irq_chip inside struct gpio_chip before invoking
>> gpiochip_add_data.
>
> Hmm... I thought this is solvable issue.
> Michael, is there a limitation in GPIO regmap that this driver can't be
> converted?
gpio-regmap is designed that regmap-irq (drivers/base/regmap/irq.c) can
be
used. So, if regmap-irq fit this driver, then it can be used together
with
gpio-regmap.
From a quick glance at the patch, it looks like the gpio portion might
fit
gpio-regmap.
>> Moreover, apart from managing the registers for gpio direction and
>> value, there
>> are several other registers that require access(interrupt enable,
>> debounce...).
>> The GPIO IRQ status registers are located at different base addresses
>> and are
>> not contiguous. It may need to create an additional regmap and assign
>> the access
>> table to this regmap.
>
> AFAIK this is not a problem as you can provide your own xlate function
> that
> will take care about register mapping.
Just for the gpio part. IIRC regmap has it own translation (regmap
fields).
>> With the above consideration, I tend to keep using the existing
>> method.
>
> I would like to hear from Michael if it's indeed a big obstacle.
So, regarding the irq portion, again, it must fit the regmap-irq. For
the
additional requirement to set the debounce, you can add a .set_config to
gpio_regmap_config and supply your own set_config callback. See also
[1].
-michael
[1]
https://lore.kernel.org/linux-gpio/d4a6a640c373b6d939e147691efa596c@walle.cc/
next prev parent reply other threads:[~2023-12-14 14:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 10:07 [PATCH v3 0/2] Add gpio driver support for Realtek DHC SoCs TY Chang
2023-12-07 10:07 ` [PATCH v3 1/2] dt-bindings: gpio: realtek: Add realtek,rtd-gpio TY Chang
2023-12-07 13:54 ` Krzysztof Kozlowski
2023-12-08 9:03 ` TY_Chang[張子逸]
2023-12-08 12:19 ` Krzysztof Kozlowski
2023-12-07 10:07 ` [PATCH v3 2/2] Add GPIO support for Realtek DHC(Digital Home Center) RTD SoCs TY Chang
2023-12-07 13:45 ` Andy Shevchenko
2023-12-12 9:55 ` TY_Chang[張子逸]
2023-12-13 13:40 ` Andy Shevchenko
2023-12-14 7:57 ` TY_Chang[張子逸]
2023-12-14 13:58 ` Andy Shevchenko
2023-12-14 14:35 ` Michael Walle [this message]
2023-12-14 14:49 ` Andy Shevchenko
2023-12-15 6:50 ` TY_Chang[張子逸]
2023-12-18 8:50 ` Michael Walle
[not found] ` <202312181420.3BIEK9gtC1692907@rtits1.realtek.com.tw>
2023-12-20 7:13 ` TY_Chang[張子逸]
2023-12-15 3:29 ` TY_Chang[張子逸]
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=0f0b3b65a838aea6797ae78c47d6af49@walle.cc \
--to=michael@walle.cc \
--cc=andy@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tychang@realtek.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
all inboxes | Powered by JetHome®