From: "jay.xu@rock-chips.com" <jay.xu@rock-chips.com>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: linus.walleij <linus.walleij@linaro.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
linux-gpio <linux-gpio@vger.kernel.org>
Subject: Re: Re: [PATCH 1/2] gpio: rockchip: make gpio work without cru module
Date: Fri, 4 Mar 2022 11:00:32 +0800 [thread overview]
Message-ID: <202203041100320387276@rock-chips.com> (raw)
In-Reply-To: 8576445.5iEe77X0Xf@diego
Hi Heiko:
--------------
jay.xu@rock-chips.com
>Hi Jianqun,
>
>Am Donnerstag, 3. März 2022, 07:22:10 CET schrieb Jianqun Xu:
>> In some case the system may has no builtin cru module, the gpio driver
>> will fail to get periph clock and debounce clock.
>
>can you elaborate a bit on what these cases are?
>
>> On rockchip SoCs, the pclk and dbg clk are default to be enabled and
>> ungated, the gpio possible to work without cru module.
>>
>> This patch makes gpio work fine without cru module.
>>
>> Signed-off-by: Jianqun Xu <jay.xu@rock-chips.com>
>> ---
>> drivers/gpio/gpio-rockchip.c | 14 +++++++++-----
>> 1 file changed, 9 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/gpio/gpio-rockchip.c b/drivers/gpio/gpio-rockchip.c
>> index a4c4e4584f5b..1da0324445cc 100644
>> --- a/drivers/gpio/gpio-rockchip.c
>> +++ b/drivers/gpio/gpio-rockchip.c
>> @@ -195,6 +195,9 @@ static int rockchip_gpio_set_debounce(struct gpio_chip *gc,
>> unsigned int cur_div_reg;
>> u64 div;
>>
>> + if (!bank->db_clk)
>> + return -ENOENT;
>> +
>> if (bank->gpio_type == GPIO_TYPE_V2 && !IS_ERR(bank->db_clk)) {
>> div_debounce_support = true;
>> freq = clk_get_rate(bank->db_clk);
>> @@ -654,8 +657,10 @@ static int rockchip_get_bank_data(struct rockchip_pin_bank *bank)
>> return -EINVAL;
>>
>> bank->clk = of_clk_get(bank->of_node, 0);
>> - if (IS_ERR(bank->clk))
>> - return PTR_ERR(bank->clk);
>> + if (IS_ERR(bank->clk)) {
>> + bank->clk = NULL;
>> + dev_warn(bank->dev, "works without clk pm\n");
>
>I'd definitly expect a more sensitive handling here (and below).
A often case is when we prepare driver for a new SoC, and need to test it on FPGA or ZEBU,
they have no cru module works, that will case gpio driver fail, I need to do wip fix
Another case is when a product needs to cut kernel as mini as possible, then the cru maybe cut and move to
other place, like uboot, the gpio will fail since get clock fail.
We have keep pclk and dbg clk (if have) to always on currently, is it possible to not handle clock for gpio ?
>
>I.e. the change right now, simply disables all error handling.
>But I do expect a handling difference between:
>- clock described in DT, but not available - should fail
>- clock not described in DT - can be allowed to go to NULL
>
>
>Heiko
>
>
>> + }
>>
>> clk_prepare_enable(bank->clk);
>> id = readl(bank->reg_base + gpio_regs_v2.version_id);
>> @@ -666,9 +671,8 @@ static int rockchip_get_bank_data(struct rockchip_pin_bank *bank)
>> bank->gpio_type = GPIO_TYPE_V2;
>> bank->db_clk = of_clk_get(bank->of_node, 1);
>> if (IS_ERR(bank->db_clk)) {
>> - dev_err(bank->dev, "cannot find debounce clk\n");
>> - clk_disable_unprepare(bank->clk);
>> - return -EINVAL;
>> + bank->db_clk = NULL;
>> + dev_warn(bank->dev, "works without debounce clk pm\n");
>> }
>> } else {
>> bank->gpio_regs = &gpio_regs_v1;
>>
>
>
>
>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2022-03-04 3:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 6:22 [PATCH 0/2] gpio-rochchip Jianqun Xu
2022-03-03 6:22 ` [PATCH 1/2] gpio: rockchip: make gpio work without cru module Jianqun Xu
2022-03-03 11:28 ` Heiko Stübner
2022-03-04 3:00 ` jay.xu [this message]
2022-03-03 6:22 ` [PATCH 2/2] gpio: rockchip: get pinctrl node from 'gpio-ranges' property Jianqun Xu
2022-03-03 11:40 ` Heiko Stübner
2022-03-04 3:02 ` jay.xu
2022-03-07 8:08 ` jay.xu
2022-03-15 1:15 ` 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=202203041100320387276@rock-chips.com \
--to=jay.xu@rock-chips.com \
--cc=heiko@sntech.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
/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).