From: Mark Brown <broonie@kernel.org>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Rob Herring <robh+dt@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Liam Girdwood <lgirdwood@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Andrea Venturi <ennesimamail.av@gmail.com>,
Code Kipper <codekipper@gmail.com>,
gianfranco@moddevices.com
Subject: Re: [PATCH 2/4] ASoC: sunxi: Add Allwinner A10 Digital Audio driver
Date: Fri, 10 Jun 2016 01:37:55 +0100 [thread overview]
Message-ID: <20160610003755.GC7510@sirena.org.uk> (raw)
In-Reply-To: <20160609210515.GI5242@lukather>
[-- Attachment #1: Type: text/plain, Size: 1550 bytes --]
On Thu, Jun 09, 2016 at 11:05:15PM +0200, Maxime Ripard wrote:
> On Thu, Jun 02, 2016 at 11:26:51AM +0100, Mark Brown wrote:
> > > +static int sun4i_i2s_params_to_sr(struct snd_pcm_hw_params *params)
> > > +{
> > > + switch (params_width(params)) {
> > > + case 16:
> > > + return 0;
> > > + }
> > > +
> > > + return -EINVAL;
> > > +}
> > The switch statement here and in the _wss() function look weird because
> > they don't have default cases. Since there's only one user of both
> > functions it seems better to have the switch statements inline anyway.
> I don't know, maybe it's just me, but I really find it cleaner that
> way, and the compiler will probably inline it anyway. If you insist,
> I'll change it though.
Yes, it's really not helping here.
> > > + for (i = 0; sun4i_i2s_mclk_div[i].div; i++) {
> > > + const struct sun4i_i2s_clk_div *mdiv = sun4i_i2s_mclk_div + i;
> > Why not just write these as normal array lookups?
> By normal, you mean using ARRAY_SIZE()?
array[index].
> > > +static int sun4i_i2s_dai_probe(struct snd_soc_dai *dai)
> > > +{
> > > + struct sun4i_i2s *i2s = snd_soc_dai_get_drvdata(dai);
> > > + /* Enable the whole hardware block */
> > > + regmap_write(i2s->regmap, SUN4I_I2S_CTRL_REG,
> > > + SUN4I_I2S_CTRL_GL_EN);
> > Runtime PM? It also seems like this is something that ought to be
> > covered in the suspend and resume callbacks.
> runtime_pm is supported, and uses the regmap cache to keep those
> changes.
No, my point is that I'd expect to see the block powered off on suspend.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-06-10 0:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 17:54 [PATCH 0/4] ASoC: sunxi: Add i2s controller support Maxime Ripard
2016-06-01 17:54 ` [PATCH 1/4] dt-bindings: Add A10 I2S controller binding documentation Maxime Ripard
2016-06-02 10:09 ` Mark Brown
2016-06-06 13:08 ` Rob Herring
2016-06-09 17:15 ` Maxime Ripard
2016-06-01 17:54 ` [PATCH 2/4] ASoC: sunxi: Add Allwinner A10 Digital Audio driver Maxime Ripard
2016-06-02 8:03 ` Code Kipper
2016-06-09 21:06 ` Maxime Ripard
2016-06-02 10:26 ` Mark Brown
2016-06-09 21:05 ` Maxime Ripard
2016-06-10 0:37 ` Mark Brown [this message]
2016-06-10 7:36 ` Maxime Ripard
2016-06-01 17:54 ` [PATCH 3/4] ARM: sun7i: Add mod1 clock nodes Maxime Ripard
2016-06-01 17:54 ` [PATCH 4/4] ARM: sun7i: Add DAI nodes Maxime Ripard
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=20160610003755.GC7510@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=codekipper@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=ennesimamail.av@gmail.com \
--cc=gianfranco@moddevices.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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