From: Daniel Mack <zonque@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/5] ASoC: codecs: tas5086: fix documentation
Date: Mon, 24 Jun 2013 18:46:48 +0200 [thread overview]
Message-ID: <51C877F8.2010106@gmail.com> (raw)
In-Reply-To: <20130624160551.GU27646@sirena.org.uk>
On 24.06.2013 18:05, Mark Brown wrote:
> On Mon, Jun 24, 2013 at 04:25:28PM +0200, Daniel Mack wrote:
>> The property 'ti,charge-period' must be given in nanoseconds, not
>> microseconds.
>
> Applied al, thanks. Though specifying this in nanoseconds does seem
> absurdly high resolution...
Meh, I was confused, sorry. That first patch need to be revered (or
dropped), the documentation was correct as it stood. The time values are
given in fractions of milliseconds, not microseconds. My bad.
> Not sure where the "codecs: " in the subject line came from either.
No problem, I can drop that in my future submissions.
Thanks,
Daniel
next prev parent reply other threads:[~2013-06-24 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 14:25 [PATCH 1/5] ASoC: codecs: tas5086: fix documentation Daniel Mack
2013-06-24 14:25 ` [PATCH 2/5] ASoC: codecs: tas5086: open-code I2C transfer routines Daniel Mack
2013-06-24 14:25 ` [PATCH 3/5] ASoC: codecs: tas5086: add more register defines Daniel Mack
2013-06-24 14:25 ` [PATCH 4/5] ASoC: codecs: tas5086: add DAPM mux controls Daniel Mack
2013-06-24 14:25 ` [PATCH 5/5] ASoC: codecs: tas5086: add support for pwm start mode config Daniel Mack
2013-06-24 16:05 ` [PATCH 1/5] ASoC: codecs: tas5086: fix documentation Mark Brown
2013-06-24 16:46 ` Daniel Mack [this message]
2013-06-25 9:26 ` 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=51C877F8.2010106@gmail.com \
--to=zonque@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.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 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.