mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Antonio Borneo <antonio.borneo@foss.st.com>
To: Marek Vasut <marex@denx.de>, Mingwei Zheng <zmw12306@gmail.com>
Cc: <linus.walleij@linaro.org>, <mcoquelin.stm32@gmail.com>,
	<alexandre.torgue@foss.st.com>, <make24@iscas.ac.cn>,
	<peng.fan@nxp.com>, <fabien.dessenne@foss.st.com>,
	<linux-gpio@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	Jiasheng Jiang <jiashengjiangcool@gmail.com>
Subject: Re: [PATCH v4] pinctrl: stm32: Add check for clk_enable()
Date: Fri, 13 Dec 2024 14:43:18 +0100	[thread overview]
Message-ID: <05081f6ebe19ce3e0e989aebf415c9ff86a39e3d.camel@foss.st.com> (raw)
In-Reply-To: <a47b567d-96a6-4a87-9f60-33a311c281ae@denx.de>

On Fri, 2024-12-13 at 12:45 +0100, Marek Vasut wrote:
> On 12/13/24 2:09 AM, Mingwei Zheng wrote:
> 
> [...]
> 
> > @@ -1397,7 +1397,7 @@ static int stm32_gpiolib_register_bank(struct stm32_pinctrl *pctl, struct fwnode
> >         return 0;
> >   
> >   err_clk:
> > -       clk_disable_unprepare(bank->clk);
> > +       clk_disable_unprepare(pctl->clks[pctl->nbanks].clk);
> 
> 
> Should this be
> 
> -clk_disable_unprepare(pctl->clks[pctl->nbanks].clk);
> +clk_disable_unprepare(pctl->clks[bank->bank_nr].clk);
>                                    ^^^^^^^^^^^^^
> 

No Marek,
pctl->nbanks is the progressive index of the bank's subnode, that is also the index for pctl->clks[].
Instead bank->bank_nr can be computed from gpio-ranges, and there is no guarantee it would match the index for pctl->clks[].

Actually this is quite confusing; I think it would be much cleaner dropping the clock handling from stm32_gpiolib_register_bank() and moving it to its caller.
In stm32_pctl_probe() we can just call clk_bulk_prepare_enable() and, in case of error, clk_bulk_disable_unprepare()

Antonio

> ?
> 
> >         return err;
> >   }
> >   
> > @@ -1617,10 +1617,18 @@ int stm32_pctl_probe(struct platform_device *pdev)
> >                 return -EINVAL;
> >         }
> >         pctl->banks = devm_kcalloc(dev, banks, sizeof(*pctl->banks),
> > -                       GFP_KERNEL);
> > +                                  GFP_KERNEL);
> >         if (!pctl->banks)
> >                 return -ENOMEM;
> >   
> > +       pctl->clks = devm_kcalloc(dev, banks, sizeof(*pctl->clks),
> > +                                 GFP_KERNEL);
> > +       if (!pctl->clks)
> > +               return -ENOMEM;
> > +
> > +       for (i = 0; i < banks; ++i)
> 
> i++


      reply	other threads:[~2024-12-13 13:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13  1:09 Mingwei Zheng
2024-12-13 11:16 ` [Linux-stm32] " Clement LE GOFFIC
2024-12-13 11:24 ` Antonio Borneo
2024-12-13 11:45 ` Marek Vasut
2024-12-13 13:43   ` Antonio Borneo [this message]

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=05081f6ebe19ce3e0e989aebf415c9ff86a39e3d.camel@foss.st.com \
    --to=antonio.borneo@foss.st.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=fabien.dessenne@foss.st.com \
    --cc=jiashengjiangcool@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=make24@iscas.ac.cn \
    --cc=marex@denx.de \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=peng.fan@nxp.com \
    --cc=zmw12306@gmail.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®