From: Mark Brown <broonie@kernel.org>
To: Rob Herring <robh+dt@kernel.org>
Cc: Frank Rowand <frowand.list@gmail.com>,
Linux-ALSA <alsa-devel@alsa-project.org>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Daniel Mack <zonque@gmail.com>
Subject: Re: ASoC: new ac97 bus and codec clock
Date: Wed, 27 Jun 2018 12:23:35 +0100 [thread overview]
Message-ID: <20180627112335.GI1779@sirena.org.uk> (raw)
In-Reply-To: <CAL_JsqKBOdZBuDnRUAcpARP1fFquc7vpcUayYRaJAMSPrhsPdg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 773 bytes --]
On Wed, Jun 20, 2018 at 11:16:15AM -0600, Rob Herring wrote:
> Does AC97 specify a common programming model? That's were a common
> compatible is used (though experience has proven things like
> "generic-ehci" are don't work).
Yes, there is a standard register interface which all AC'97 CODECs
implemented and which does work effectively for drivers that only use
that. Devices can offer extensions which do need specific drivers, and
there are ID registers which can be used to enumerate. However one of
the things that some of the devices targetted at embedded systems do is
offer non-standard clocking features that need some configuration during
initialization (and may need to work with input clocks too) which
complicates things, especially in the context of DT.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2018-06-27 11:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-17 20:03 ASoC: new ac97 bus and codec clock Robert Jarzmik
2018-06-19 15:02 ` Mark Brown
2018-06-19 17:56 ` Rob Herring
2018-06-20 14:52 ` Robert Jarzmik
2018-06-20 15:10 ` Rob Herring
2018-06-20 17:04 ` Robert Jarzmik
2018-06-20 17:16 ` Rob Herring
2018-06-20 19:36 ` Robert Jarzmik
2018-06-20 20:00 ` Rob Herring
2018-06-27 11:23 ` Mark Brown [this message]
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=20180627112335.GI1779@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=frowand.list@gmail.com \
--cc=robert.jarzmik@free.fr \
--cc=robh+dt@kernel.org \
--cc=zonque@gmail.com \
/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.