All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
	jsarha@ti.com, zonque@gmail.com
Subject: Re: [PATCH 0/2] ASoC: davinci-mcasp: Improved suspend/resume support
Date: Thu, 2 Oct 2014 10:21:31 +0300	[thread overview]
Message-ID: <542CFCFB.4060709@ti.com> (raw)
In-Reply-To: <20141001160240.GC4273@sirena.org.uk>

On 10/01/2014 07:02 PM, Mark Brown wrote:
> On Wed, Oct 01, 2014 at 04:02:10PM +0300, Peter Ujfalusi wrote:
>> Hi,
>>
>> With this series the McASP will continue to work after deep sleep during audio
>> activity.
>> Without these changes the ongoing audio will not resume and it will time out,
>> but streams started after resume were worked correctly.
> 
> Applied both, thanks.  Might be worth converting to regmap and using the
> cache code?

Yes, it is in my to-do list. One thing I'm a bit puzzled currently is on how
to handle the serializer registers. Depending on the SoC the McASP is
integrated in we can have different number of serializers, also in some SoC
different McASP ports have different number of serializers. I do not want to
have separate regmap struct for all of these (which would most probably means
different compatible flag in DT). I also want to avoid wiring in some max
limit of the serializer registers. But probably I need to do this at the end.

-- 
Péter

  reply	other threads:[~2014-10-02  7:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01 13:02 [PATCH 0/2] ASoC: davinci-mcasp: Improved suspend/resume support Peter Ujfalusi
2014-10-01 13:02 ` [PATCH 1/2] ASoC: davinci-mcasp: Convert the context save/restore to use array Peter Ujfalusi
2014-10-01 13:02 ` [PATCH 2/2] ASoC: davinvi-mcasp: Proper suspend/resume support while audio is active Peter Ujfalusi
2014-10-01 16:02 ` [PATCH 0/2] ASoC: davinci-mcasp: Improved suspend/resume support Mark Brown
2014-10-02  7:21   ` Peter Ujfalusi [this message]
2014-10-02 10:56     ` 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=542CFCFB.4060709@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=jsarha@ti.com \
    --cc=lgirdwood@gmail.com \
    --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.