From: Krzysztof Kozlowski <krzk@kernel.org>
To: Steve Lee <steve.lee.analog@gmail.com>,
lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
tiwai@suse.com, ckeepax@opensource.cirrus.com,
geert@linux-m68k.org, rf@opensource.wolfsonmicro.com,
shumingf@realtek.com, srinivas.kandagatla@linaro.org,
jack.yu@realtek.com, nuno.sa@analog.com,
ryans.lee@maximintegrated.com, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org
Subject: Re: [RESEND V2] ASoC: max98390: Add reset gpio control
Date: Sat, 12 Mar 2022 11:40:55 +0100 [thread overview]
Message-ID: <009acb4c-d59c-c1ad-60b0-cc85fe7ad73d@kernel.org> (raw)
In-Reply-To: <20220312002429.16175-1-steve.lee.analog@gmail.com>
On 12/03/2022 01:24, Steve Lee wrote:
> Add reset gpio control to support RESET PIN connected to gpio.
>
> Signed-off-by: Steve Lee <steve.lee.analog@gmail.com>
> ---
> sound/soc/codecs/max98390.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/sound/soc/codecs/max98390.c b/sound/soc/codecs/max98390.c
> index 40fd6f363f35..9a9299e5cc5a 100644
> --- a/sound/soc/codecs/max98390.c
> +++ b/sound/soc/codecs/max98390.c
> @@ -1022,6 +1022,7 @@ static int max98390_i2c_probe(struct i2c_client *i2c,
>
> struct max98390_priv *max98390 = NULL;
> struct i2c_adapter *adapter = i2c->adapter;
> + struct gpio_desc *reset_gpio;
>
> ret = i2c_check_functionality(adapter,
> I2C_FUNC_SMBUS_BYTE
> @@ -1073,6 +1074,17 @@ static int max98390_i2c_probe(struct i2c_client *i2c,
> return ret;
> }
>
> + reset_gpio = devm_gpiod_get_optional(&i2c->dev,
> + "maxim,reset-gpios", GPIOD_OUT_LOW);
> +
I don't know why did you CC me, but since I am looking at this - you
have to update bindings.
Do not add random properties to drivers without updating bindings.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-03-12 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 0:24 Steve Lee
2022-03-12 10:40 ` Krzysztof Kozlowski [this message]
2022-03-13 5:40 ` Lee Steve
2022-03-12 12:58 ` Nuno Sá
2022-03-13 5:42 ` Lee Steve
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=009acb4c-d59c-c1ad-60b0-cc85fe7ad73d@kernel.org \
--to=krzk@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=geert@linux-m68k.org \
--cc=jack.yu@realtek.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=perex@perex.cz \
--cc=rf@opensource.wolfsonmicro.com \
--cc=ryans.lee@maximintegrated.com \
--cc=shumingf@realtek.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=steve.lee.analog@gmail.com \
--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
all inboxes | Powered by JetHome®