From: Robin Murphy <robin.murphy@arm.com>
To: Judy Hsiao <judyhsiao@chromium.org>, Heiko Stuebner <heiko@sntech.de>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Brian Norris <briannorris@chromium.org>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Chen-Yu Tsai <wenst@chromium.org>,
alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/3] ASoC: rockchip: i2s: switch BCLK to GPIO
Date: Thu, 23 Jun 2022 10:15:48 +0100 [thread overview]
Message-ID: <4bec03b5-c496-ec0d-b968-d4d0e5d2e782@arm.com> (raw)
In-Reply-To: <20220623021153.587423-2-judyhsiao@chromium.org>
On 2022-06-23 03:11, Judy Hsiao wrote:
[...]
> @@ -736,6 +799,20 @@ static int rockchip_i2s_probe(struct platform_device *pdev)
> }
>
> i2s->bclk_ratio = 64;
> + i2s->pinctrl = devm_pinctrl_get(&pdev->dev);
> + if (IS_ERR(i2s->pinctrl)) {
> + dev_err(&pdev->dev, "failed to find i2s pinctrl\n");
If we're still reworking this, it might be good to set i2s->pinctrl to
NULL here, and similarly free and clear if we fail to get the states in
the other path, so that everywhere else could consistently have just a
simple "if (i2s->pinctrl)" check rather than the "IS_ERR() ||
IS_ERR_OR_NULL()" mess.
> + } else { > + i2s->bclk_on = pinctrl_lookup_state(i2s->pinctrl, "bclk_on");
> + if (!IS_ERR_OR_NULL(i2s->bclk_on)) {
> + i2s->bclk_off = pinctrl_lookup_state(i2s->pinctrl, "bclk_off");
> + if (IS_ERR_OR_NULL(i2s->bclk_off)) {
> + dev_err(&pdev->dev, "failed to find i2s bclk_off\n");
> + goto err_clk;
> + }
> + }
> + i2s_pinctrl_select_bclk_off(i2s);
FWIW it seems a bit odd to call this in the case where we didn't even
get "bclk_on".
Robin.
> + }
>
> dev_set_drvdata(&pdev->dev, i2s);
>
next prev parent reply other threads:[~2022-06-23 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 2:11 [PATCH v5 0/3] " Judy Hsiao
2022-06-23 2:11 ` [PATCH v5 1/3] " Judy Hsiao
2022-06-23 9:15 ` Robin Murphy [this message]
2022-06-23 2:11 ` [PATCH v5 2/3] arm64: dts: rk3399: " Judy Hsiao
2022-06-23 2:11 ` [PATCH v5 3/3] ASoC: dt-bindings: rockchip: Document pinctrl-names for i2s Judy Hsiao
2022-06-23 11:04 ` [PATCH v5 0/3] ASoC: rockchip: i2s: switch BCLK to GPIO Mark Brown
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=4bec03b5-c496-ec0d-b968-d4d0e5d2e782@arm.com \
--to=robin.murphy@arm.com \
--cc=alsa-devel@alsa-project.org \
--cc=briannorris@chromium.org \
--cc=broonie@kernel.org \
--cc=heiko@sntech.de \
--cc=judyhsiao@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=wenst@chromium.org \
/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®