From: Mark Brown <broonie@kernel.org>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh@kernel.org>,
Linux-ALSA <alsa-devel@alsa-project.org>,
Lars-Peter Clausen <lars@metafoo.de>,
kernel@pengutronix.de, devicetree@vger.kernel.org,
Sascha Hauer <s.hauer@pengutronix.de>,
Liam Girdwood <lgirdwood@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [PATCH] ASoC: ssm2602: Fix ADC powerup sequencing
Date: Fri, 25 May 2018 11:26:09 +0100 [thread overview]
Message-ID: <20180525102609.GK4828@sirena.org.uk> (raw)
In-Reply-To: <20180525094724.3f4edofopk52i3v6@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 408 bytes --]
On Fri, May 25, 2018 at 11:47:24AM +0200, Marco Felsch wrote:
> I found the: "ti,charge-period (sound/ti,tas5086.txt)" binding which
> represents nearly the same but it is not common. One opportunity would be to
> introduce a common "charge-period-us" binding and change the ti binding the
> common binding later.
Are you sure what you have is a charge period and not some stabalization
time or something?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2018-05-25 10:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 13:30 [PATCH] ASoC: ssm2602: Fix ADC powerup sequencing Marco Felsch
2018-05-17 16:14 ` Rob Herring
2018-05-18 10:46 ` Philipp Zabel
2018-05-23 16:53 ` Rob Herring
2018-05-25 9:47 ` Marco Felsch
2018-05-25 10:26 ` Mark Brown [this message]
2018-05-25 11:42 ` Marco Felsch
2018-05-25 14:52 ` Mark Brown
2018-05-25 15:18 ` Philipp Zabel
2018-05-25 17:24 ` Mark Brown
2018-06-05 9:58 ` Philipp Zabel
2018-06-05 16:06 ` Mark Brown
2018-05-25 15:42 ` Rob Herring
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=20180525102609.GK4828@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=m.felsch@pengutronix.de \
--cc=mark.rutland@arm.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
/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.