From: Shawn Guo <shawnguo@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Shawn Guo <shawn.guo@linaro.org>,
Baoyou Xie <xie.baoyou@sanechips.com.cn>,
Xin Zhou <zhou.xin8@sanechips.com.cn>,
Jun Nie <jun.nie@linaro.org>, Baoyou Xie <baoyou.xie@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] ASoC: zx_aud96p22: add ZTE ZX AUD96P22 codec driver
Date: Thu, 22 Jun 2017 00:03:41 +0800 [thread overview]
Message-ID: <20170621160340.GE3372@dragon> (raw)
In-Reply-To: <20170620124059.r55r363y3y3if6jg@sirena.org.uk>
On Tue, Jun 20, 2017 at 01:40:59PM +0100, Mark Brown wrote:
> On Tue, Jun 20, 2017 at 11:19:55AM +0800, Shawn Guo wrote:
> > On Mon, Jun 19, 2017 at 05:19:10PM +0100, Mark Brown wrote:
> > > On Sat, Jun 17, 2017 at 10:09:34PM +0800, Shawn Guo wrote:
>
> > > > + /* Overall power-up */
> > > > + regmap_update_bits(regmap, AUD96P22_PD_0, PD_0_PDZ, PD_0_PDZ);
>
> > > Why is this not done with DAPM?
>
> > As this is a overall power bit, which is not for any specific component.
> > I'm not sure which DAPM widget should be used for it, and how it should
> > be arranged in the widget route. Any suggestion or example will be
> > appreciated.
>
> Sounds like a fairly standard use for a supply widget.
Yes, it can be a supply widget. But it's a bit that controls device
overall power rather than any particular component power. Since every
single operation of the device will need this power bit to be on, I
think it makes sense to configure the bit in .startup/.shutdown hooks,
rather than creating a widget for it and attaches the widget to a bunch
of components.
>
> > > > + /* Reset ADC and DAC path */
> > > > + regmap_write(regmap, AUD96P22_RESET, 0x0);
> > > > + regmap_write(regmap, AUD96P22_RESET, 0x3);
>
> > > What does this mean?
>
> > It's a de-assert/assert of ADC and DAC reset. I will add proper
> > defines for the bits to make this clear.
>
> Why are we resetting these - won't this loose settings?
It only resets some hardware internal states, and software settings
won't be affected.
> And if it's
> just something to be done as part of starting the DAC and ADC why isn't
> it done via DAPM?
Yes, it sounds like a better approach. Will try to do that.
Shawn
WARNING: multiple messages have this Message-ID (diff)
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ASoC: zx_aud96p22: add ZTE ZX AUD96P22 codec driver
Date: Thu, 22 Jun 2017 00:03:41 +0800 [thread overview]
Message-ID: <20170621160340.GE3372@dragon> (raw)
In-Reply-To: <20170620124059.r55r363y3y3if6jg@sirena.org.uk>
On Tue, Jun 20, 2017 at 01:40:59PM +0100, Mark Brown wrote:
> On Tue, Jun 20, 2017 at 11:19:55AM +0800, Shawn Guo wrote:
> > On Mon, Jun 19, 2017 at 05:19:10PM +0100, Mark Brown wrote:
> > > On Sat, Jun 17, 2017 at 10:09:34PM +0800, Shawn Guo wrote:
>
> > > > + /* Overall power-up */
> > > > + regmap_update_bits(regmap, AUD96P22_PD_0, PD_0_PDZ, PD_0_PDZ);
>
> > > Why is this not done with DAPM?
>
> > As this is a overall power bit, which is not for any specific component.
> > I'm not sure which DAPM widget should be used for it, and how it should
> > be arranged in the widget route. Any suggestion or example will be
> > appreciated.
>
> Sounds like a fairly standard use for a supply widget.
Yes, it can be a supply widget. But it's a bit that controls device
overall power rather than any particular component power. Since every
single operation of the device will need this power bit to be on, I
think it makes sense to configure the bit in .startup/.shutdown hooks,
rather than creating a widget for it and attaches the widget to a bunch
of components.
>
> > > > + /* Reset ADC and DAC path */
> > > > + regmap_write(regmap, AUD96P22_RESET, 0x0);
> > > > + regmap_write(regmap, AUD96P22_RESET, 0x3);
>
> > > What does this mean?
>
> > It's a de-assert/assert of ADC and DAC reset. I will add proper
> > defines for the bits to make this clear.
>
> Why are we resetting these - won't this loose settings?
It only resets some hardware internal states, and software settings
won't be affected.
> And if it's
> just something to be done as part of starting the DAC and ADC why isn't
> it done via DAPM?
Yes, it sounds like a better approach. Will try to do that.
Shawn
next prev parent reply other threads:[~2017-06-21 16:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-17 14:09 [PATCH 0/2] Add ZTE ZTE zx-aud96p22 audio codec driver Shawn Guo
2017-06-17 14:09 ` Shawn Guo
2017-06-17 14:09 ` [PATCH 1/2] ASoC: add bindings for ZTE zx-aud96p22 audio codec Shawn Guo
2017-06-17 14:09 ` Shawn Guo
2017-06-19 16:16 ` Mark Brown
2017-06-19 16:16 ` Mark Brown
2017-06-20 3:11 ` Shawn Guo
2017-06-20 3:11 ` Shawn Guo
2017-06-20 14:33 ` Mark Brown
2017-06-20 14:33 ` Mark Brown
2017-06-21 13:22 ` Shawn Guo
2017-06-21 13:22 ` Shawn Guo
2017-06-17 14:09 ` [PATCH 2/2] ASoC: zx_aud96p22: add ZTE ZX AUD96P22 codec driver Shawn Guo
2017-06-17 14:09 ` Shawn Guo
2017-06-19 16:19 ` Mark Brown
2017-06-19 16:19 ` Mark Brown
2017-06-20 3:19 ` Shawn Guo
2017-06-20 3:19 ` Shawn Guo
2017-06-20 12:40 ` Mark Brown
2017-06-20 12:40 ` Mark Brown
2017-06-21 16:03 ` Shawn Guo [this message]
2017-06-21 16:03 ` Shawn Guo
2017-06-21 16:13 ` Mark Brown
2017-06-21 16:13 ` 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=20170621160340.GE3372@dragon \
--to=shawnguo@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=baoyou.xie@linaro.org \
--cc=broonie@kernel.org \
--cc=jun.nie@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=shawn.guo@linaro.org \
--cc=xie.baoyou@sanechips.com.cn \
--cc=zhou.xin8@sanechips.com.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.