mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Nikesh <noswal@opensource.wolfsonmicro.com>
Cc: Nikesh Oswal <nikesh@opensource.wolfsonmicro.com>,
	lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.de,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	patches@opensource.wolfsonmicro.com, Nikesh.Oswal@cirrus.com
Subject: Re: [PATCH] ASoC: make dapm cache search depth configurable
Date: Thu, 10 Sep 2015 11:31:35 +0100	[thread overview]
Message-ID: <20150910103134.GE20922@sirena.org.uk> (raw)
In-Reply-To: <55F1509A.4040303@opensource.wolfsonmicro.com>

[-- Attachment #1: Type: text/plain, Size: 769 bytes --]

On Thu, Sep 10, 2015 at 10:42:50AM +0100, Nikesh wrote:
> Hi Mark,

As I'm fairly sure I've had to tell you before don't top post.  This
means that when someone sees something like this:

> The reason I though this will be usefull is as below:

while reading they know what the "this" you are talking about is.

> the widgets in wm5110_dapm_widgets[]) as defined in this macro. But if you
> notice the way DSP widgets are created they use a WM_ADSP2 macro which
> creates a preloader widget for every DSP widget and we want to skip past
> this preloader widget when doing a cache search so increasing the cache
> search depth helps here.

Why is the solution to this problem to add device specific tuning?  Is
this extremely expensive so no other device would want it?

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

      reply	other threads:[~2015-09-10 10:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08 10:11 Nikesh Oswal
2015-09-08 10:42 ` Mark Brown
2015-09-10  9:42   ` Nikesh
2015-09-10 10:31     ` 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=20150910103134.GE20922@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Nikesh.Oswal@cirrus.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nikesh@opensource.wolfsonmicro.com \
    --cc=noswal@opensource.wolfsonmicro.com \
    --cc=patches@opensource.wolfsonmicro.com \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®