[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<DU0PR04MB9417FEFA3DB02082D02A963F88332@DU0PR04MB9417.eurprd04.prod.outlook.com>
Date: Wed, 20 Mar 2024 11:07:40 +0000
From: Peng Fan <peng.fan@....com>
To: Andy Shevchenko <andy.shevchenko@...il.com>, "Peng Fan (OSS)"
<peng.fan@....nxp.com>
CC: "linus.walleij@...aro.org" <linus.walleij@...aro.org>, "brgl@...ev.pl"
<brgl@...ev.pl>, "andy@...nel.org" <andy@...nel.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH V2] gpiolib: use dev_err() when gpiod_configure_flags
failed
> Subject: Re: [PATCH V2] gpiolib: use dev_err() when gpiod_configure_flags
> failed
>
> On Wed, Mar 20, 2024 at 9:25 AM Peng Fan (OSS) <peng.fan@....nxp.com>
> wrote:
> >
> > From: Peng Fan <peng.fan@....com>
> >
> > When gpio-ranges property was missed to be added in the gpio node,
> > using dev_err() to show an error message will helping to locate issues
> > easier.
>
> I'm not convinced, so not my call to approve / reject, but see a remark below.
You mean dev_err not help or else?
>
> ...
>
> > ret = gpiod_configure_flags(desc, con_id, lookupflags, flags);
> > if (ret < 0) {
> > - dev_dbg(consumer, "setup of GPIO %s failed\n", con_id);
> > + dev_err(consumer, "setup of GPIO %s failed: %d\n",
> > + con_id, ret);
> > gpiod_put(desc);
> > return ERR_PTR(ret);
>
> While at it, can you move it to be after the gpiod_put()?
Does it matter?
Thanks,
Peng.
>
> > }
>
> --
> With Best Regards,
> Andy Shevchenko
Powered by blists - more mailing lists