All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: broonie@kernel.org
Cc: patches@opensource.cirrus.com, alsa-devel@alsa-project.org,
	lgirdwood@gmail.com
Subject: [RFC PATCH 0/4] Initial prototype of DAPM sample rate domains
Date: Thu, 11 Oct 2018 17:28:27 +0100	[thread overview]
Message-ID: <20181011162831.26351-1-ckeepax@opensource.cirrus.com> (raw)

Here is a first pass at adding dapm sample rate domain
support. Things are still pretty rough in quite a few places and
I expect some major refactoring before they are ready to merge,
but things are far enough along for people to look at the approach
I am taking to the problem. And should provide enough for discussion
at the mini-conference, although hopefully I will get some more done
next week as well.

The basic high level summary is two new concepts are added to
ASoC, one being a sample rate domain and the other being a domain
group. The domain groups represent widgets that are limited by
hardware restrictions to always run at the same sample rate as each
other. Sample rate domains represent a slot on a device for a sample
rate. Both of these are currently limited to be within the scope of
a single component.  The core will track which groups are connected
together, then as a group is powered up it will be allocated a domain
based on the other groups it is connected to. Domain groups are
implemented as a new type of DAPM widget and the domains themselves
are a new thing which devices add through their component drivers.

As we have previously discussed my intention would be that we also
add bridges between domains although I haven't started work on that
yet. The current code is limited to within a single component and
I think that the bridges will allow better support for propagating
rates between components as well as obviously for SRCs. Currently
the SRCs on wm5110 are just being handled as points where the
domain groups don't connect to another peer.  This allows them to
function but doesn't accurately convey things like the limitations
which input rates support which output rates on the ISRC.

Thanks,
Charles

Charles Keepax (4):
  ASoC: dapm: Add support for hw_free on CODEC to CODEC links
  ASoC: dapm: Add support for a rate domain widget
  ASoC: domain: Add sample rate domain support
  ASoC: arizona: Add rate domain support

 include/sound/soc-dapm.h   |  14 ++
 include/sound/soc-domain.h |  98 +++++++++++
 include/sound/soc.h        |   8 +
 sound/soc/Makefile         |   2 +-
 sound/soc/codecs/arizona.c | 255 ++++++++++++++++++++++------
 sound/soc/codecs/arizona.h |  76 ++++++++-
 sound/soc/codecs/wm5110.c  | 414 ++++++++++++++++++++++++++++++++++-----------
 sound/soc/soc-core.c       |   8 +
 sound/soc/soc-dapm.c       |  57 ++++++-
 sound/soc/soc-domain.c     | 412 ++++++++++++++++++++++++++++++++++++++++++++
 10 files changed, 1183 insertions(+), 161 deletions(-)
 create mode 100644 include/sound/soc-domain.h
 create mode 100644 sound/soc/soc-domain.c

-- 
2.11.0

             reply	other threads:[~2018-10-11 16:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11 16:28 Charles Keepax [this message]
2018-10-11 16:28 ` [RFC PATCH 1/4] ASoC: dapm: Add support for hw_free on CODEC to CODEC links Charles Keepax
2018-10-19 12:26   ` Applied "ASoC: dapm: Add support for hw_free on CODEC to CODEC links" to the asoc tree Mark Brown
2018-10-19 12:34   ` Mark Brown
2018-10-11 16:28 ` [RFC PATCH 2/4] ASoC: dapm: Add support for a rate domain widget Charles Keepax
2018-10-11 16:28 ` [RFC PATCH 3/4] ASoC: domain: Add sample rate domain support Charles Keepax
2018-10-11 16:28 ` [RFC PATCH 4/4] ASoC: arizona: Add " Charles Keepax
2018-10-22 14:27 ` [RFC PATCH 0/4] Initial prototype of DAPM sample rate domains Pierre-Louis Bossart
2018-10-23 14:36   ` Charles Keepax

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=20181011162831.26351-1-ckeepax@opensource.cirrus.com \
    --to=ckeepax@opensource.cirrus.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=patches@opensource.cirrus.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.