From: Dan Murphy <dmurphy@ti.com>
To: Camel Guo <camel.guo@axis.com>, <lgirdwood@gmail.com>,
<broonie@kernel.org>, <tiwai@suse.com>
Cc: alsa-devel@alsa-project.org, kernel@axis.com,
linux-kernel@vger.kernel.org, Camel Guo <camelg@axis.com>
Subject: Re: [PATCH v2 2/3] ASoC: tlv320adcx140: Add support for configuring GPIO pin
Date: Tue, 15 Sep 2020 13:41:00 -0500 [thread overview]
Message-ID: <da35edb3-bc41-967c-d530-4df4363ddddf@ti.com> (raw)
In-Reply-To: <20200911080753.30342-2-camel.guo@axis.com>
Camel
On 9/11/20 3:07 AM, Camel Guo wrote:
> From: Camel Guo <camelg@axis.com>
>
> Add support to configure the GPIO pin to the specific configuration.
> The GPIO pin can be configured as GPO, IRQ, SDOUT2, PDMCLK, MICBASE_EN,
> GPI, MCLK, SDIN, PDMDIN1, PDMDIN2, PDMDIN3 or PDMDIN4 and the output
> drive can be configured with various configuration.
>
> Signed-off-by: Camel Guo <camelg@axis.com>
> ---
> sound/soc/codecs/tlv320adcx140.c | 44 ++++++++++++++++++++++++++++++++
> sound/soc/codecs/tlv320adcx140.h | 4 +++
> 2 files changed, 48 insertions(+)
>
> diff --git a/sound/soc/codecs/tlv320adcx140.c b/sound/soc/codecs/tlv320adcx140.c
> index f33ee604ee78..97f16fbba441 100644
> --- a/sound/soc/codecs/tlv320adcx140.c
> +++ b/sound/soc/codecs/tlv320adcx140.c
> @@ -837,6 +837,46 @@ static int adcx140_configure_gpo(struct adcx140_priv *adcx140)
>
> }
>
> +static int adcx140_configure_gpio(struct adcx140_priv *adcx140)
> +{
> + int gpio_count = 0;
> + u32 gpio_outputs[2];
This is #defined in configure_gpo and configure_gpi would like to see
the consistency here.
> + u32 gpio_output_val = 0;
> + int ret;
> +
> + gpio_count = device_property_count_u32(adcx140->dev,
> + "ti,gpio-config");
> + if (gpio_count == 0)
> + return 0;
> +
> + if (gpio_count != 2)
Same comment as above.
> + return -EINVAL;
> +
> + ret = device_property_read_u32_array(adcx140->dev, "ti,gpio-config",
> + gpio_outputs, gpio_count);
> + if (ret)
> + return ret;
> +
> + if (gpio_outputs[0] > ADCX140_GPIO_CFG_MAX) {
> + dev_err(adcx140->dev, "GPIO config out of range\n");
> + return -EINVAL;
> + }
> +
> + if (gpio_outputs[1] > ADCX140_GPIO_DRV_MAX) {
> + dev_err(adcx140->dev, "GPIO drive out of range\n");
> + return -EINVAL;
> + }
> +
> + gpio_output_val = gpio_outputs[0] << ADCX140_GPIO_SHIFT
> + | gpio_outputs[1];
> +
> + ret = regmap_write(adcx140->regmap, ADCX140_GPIO_CFG0, gpio_output_val);
> + if (ret)
> + return ret;
Just do return regmap_write no reason to check it. It is checked by the
caller.
Dan
next prev parent reply other threads:[~2020-09-15 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 8:07 [PATCH v2 1/3] dt-bindings: tlv320adcx140: Add GPIO config and drive config Camel Guo
2020-09-11 8:07 ` [PATCH v2 2/3] ASoC: tlv320adcx140: Add support for configuring GPIO pin Camel Guo
2020-09-15 18:41 ` Dan Murphy [this message]
2020-09-15 19:05 ` Dan Murphy
2020-09-11 8:07 ` [PATCH v2 3/3] ASoC: tlv320adcx140: Add proper support for master mode Camel Guo
2020-09-15 18:50 ` Dan Murphy
[not found] ` <507f2f53-e236-f894-cb17-4fc84cf00326@axis.com>
2020-09-16 11:46 ` Dan Murphy
2020-09-15 18:35 ` [PATCH v2 1/3] dt-bindings: tlv320adcx140: Add GPIO config and drive config Dan Murphy
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=da35edb3-bc41-967c-d530-4df4363ddddf@ti.com \
--to=dmurphy@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=camel.guo@axis.com \
--cc=camelg@axis.com \
--cc=kernel@axis.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.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