From: Linus Walleij <linus.walleij@linaro.org>
To: Peng Fan <peng.fan@nxp.com>
Cc: Johan Hovold <johan@kernel.org>,
Steev Klimaszewski <steev@kali.org>,
"Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH 2/3] ASoC: codec: wcd938x: Convert to GPIO descriptors
Date: Mon, 24 Mar 2025 10:57:53 +0100 [thread overview]
Message-ID: <CACRpkdZ_f2EHjTJtkOdAmdAOUsh2Xi0hsToCWuTGkoh1aCZwtA@mail.gmail.com> (raw)
In-Reply-To: <PAXPR04MB8459F7BE5AD43E0685C74A6C88A42@PAXPR04MB8459.eurprd04.prod.outlook.com>
On Mon, Mar 24, 2025 at 9:34 AM Peng Fan <peng.fan@nxp.com> wrote:
> > Subject: Re: [PATCH 2/3] ASoC: codec: wcd938x: Convert to GPIO
> > descriptors
> >
> > On Mon, Mar 24, 2025 at 9:09 AM Peng Fan <peng.fan@nxp.com>
> > wrote:
> >
> > > ok, then the only suspecting point is
> > > wcd938x->reset_gpio = devm_gpiod_get(dev, "reset", GPIOD_ASIS);
> > >
> > > I may need to use GPIOD_OUT_LOW to configure it to output as set
> > raw
> > > set value as 1.
> >
> > I think there may be a bug in gpiod_configure_flags() in gpiolib.c:
> >
> > /* Process flags */
> > if (dflags & GPIOD_FLAGS_BIT_DIR_OUT)
> > ret = gpiod_direction_output_nonotify(desc,
> > !!(dflags & GPIOD_FLAGS_BIT_DIR_VAL));
> > else
> > ret = gpiod_direction_input_nonotify(desc);
> >
> > Shouldn't this be:
> >
> > if (dflags & GPIOD_FLAGS_BIT_DIR_OUT)
> > ret = gpiod_direction_output_nonotify(desc,
> > !!(dflags & GPIOD_FLAGS_BIT_DIR_VAL));
> > else if (dflags & GPIOD_FLAGS_BIT_DIR_SET)
> > ret = gpiod_direction_input_nonotify(desc);
>
> Using GPIO_ASIS should not change direction.
> This change makes sense.
Actually when looking closer at it I was wrong.
From <linux/gpio/consumer.h>:
enum gpiod_flags {
GPIOD_ASIS = 0,
GPIOD_IN = GPIOD_FLAGS_BIT_DIR_SET,
GPIOD_OUT_LOW = GPIOD_FLAGS_BIT_DIR_SET | GPIOD_FLAGS_BIT_DIR_OUT,
GPIOD_OUT_HIGH = GPIOD_FLAGS_BIT_DIR_SET | GPIOD_FLAGS_BIT_DIR_OUT |
GPIOD_FLAGS_BIT_DIR_VAL,
GPIOD_OUT_LOW_OPEN_DRAIN = GPIOD_OUT_LOW | GPIOD_FLAGS_BIT_OPEN_DRAIN,
GPIOD_OUT_HIGH_OPEN_DRAIN = GPIOD_OUT_HIGH | GPIOD_FLAGS_BIT_OPEN_DRAIN,
};
So GPIOD_ASIS does not set GPIOD_FLAGS_BIT_DIR_SET.
Then gpiod_configure_flags() has:
/* No particular flag request, return here... */
if (!(dflags & GPIOD_FLAGS_BIT_DIR_SET)) {
gpiod_dbg(desc, "no flags found for GPIO %s\n", name);
return 0;
}
/* Process flags */
if (dflags & GPIOD_FLAGS_BIT_DIR_OUT)
ret = gpiod_direction_output_nonotify(desc,
!!(dflags & GPIOD_FLAGS_BIT_DIR_VAL));
else
ret = gpiod_direction_input_nonotify(desc);
So the function bails out right above (you could check the debug
print there if in doubt.)
So the behaviour is correct.
So now I have no idea what is going on again :/
But I would suggest trying to set GPIOD_OUT_LOW when requesting
the line and just check if that solves Steev:s problem
(trial-and-error).
Yours,
Linus Walleij
next prev parent reply other threads:[~2025-03-24 9:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 2:26 [PATCH 0/3] ASoC: codec: wcd93xx: Convert to GPIO descriptors Peng Fan (OSS)
2025-03-24 2:26 ` [PATCH 1/3] ASoC: codec: wcd939x: " Peng Fan (OSS)
2025-03-24 7:30 ` Linus Walleij
2025-03-24 2:26 ` [PATCH 2/3] ASoC: codec: wcd938x: " Peng Fan (OSS)
2025-03-24 3:40 ` Steev Klimaszewski
2025-03-24 7:33 ` Peng Fan
2025-03-24 7:46 ` Linus Walleij
2025-03-24 7:53 ` Peng Fan
2025-03-24 7:56 ` Linus Walleij
2025-03-24 8:03 ` Johan Hovold
2025-03-24 8:09 ` Peng Fan
2025-03-24 8:23 ` Linus Walleij
2025-03-24 8:34 ` Peng Fan
2025-03-24 9:57 ` Linus Walleij [this message]
2025-03-24 8:13 ` Johan Hovold
2025-03-24 7:30 ` Linus Walleij
2025-03-24 2:26 ` [PATCH 3/3] ASoC: codec: wcd9335: " Peng Fan (OSS)
2025-03-24 7:47 ` 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=CACRpkdZ_f2EHjTJtkOdAmdAOUsh2Xi0hsToCWuTGkoh1aCZwtA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=johan@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=perex@perex.cz \
--cc=srinivas.kandagatla@linaro.org \
--cc=steev@kali.org \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).