All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@ti.com>
To: Patrick Lai <plai@codeaurora.org>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	"waiw@codeaurora.org" <waiw@codeaurora.org>,
	pl bossart <bossart.nospam@gmail.com>,
	"asishb@codeaurora.org" <asishb@codeaurora.org>,
	"jaywang@codeaurora.org" <jaywang@codeaurora.org>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: soc-dsp questions
Date: Mon, 13 Jun 2011 19:01:01 +0100	[thread overview]
Message-ID: <4DF6505D.9000402@ti.com> (raw)
In-Reply-To: <4DF5982C.6070705@codeaurora.org>

On 13/06/11 05:55, Patrick Lai wrote:
>>> Are you referring to fixup function in the machine driver? It works for
>>> hardware parameter that is fixed per machine. For example, regardless
>>> sample rate of front-ends that are routed to same back-end,
>>> back-end sample rate is fixed to 48KHz. I am already taking advantage
>>> of the hook.
>>
>> Yes.  Since it's code it *could* do conditional things based on some
>> setting if it needs to.
>>
> Yes, I don't see any better way unless propagating knowledge of 
> front-end/back-end all the way to user-space. I plan on adding 
> enumeration of
> channel mode in machine driver which sets variable read by the fix up
> function. So, CPU and CODEC drivers do not need to provide enumeration
> of channel modes. However, same control would have to be added to every
> machine driver.

Ok, sounds like this may be useful code for other DSPs too.

Fwiw, OMAP4 fixups are based on physical BE DAI so we always use the same config for each BE DAI atm, but flexibility would be good.

Liam 

  reply	other threads:[~2011-06-13 18:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-25 22:01 soc-dsp questions pl bossart
2011-04-26  9:41 ` Liam Girdwood
2011-04-26 10:18   ` Mark Brown
2011-06-10  6:58     ` Patrick Lai
2011-06-10  9:42       ` Mark Brown
2011-06-11  1:19         ` Patrick Lai
2011-06-11 11:48           ` Mark Brown
2011-06-13  4:55             ` Patrick Lai
2011-06-13 18:01               ` Liam Girdwood [this message]
2011-06-13 17:55             ` Liam Girdwood
2011-06-13 17:49           ` Liam Girdwood
  -- strict thread matches above, loose matches on Subject: below --
2011-11-08  8:22 Vinod Koul
2011-11-08 20:20 ` Girdwood, Liam
2011-11-09  8:04   ` Vinod Koul

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=4DF6505D.9000402@ti.com \
    --to=lrg@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=asishb@codeaurora.org \
    --cc=bossart.nospam@gmail.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=jaywang@codeaurora.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=plai@codeaurora.org \
    --cc=waiw@codeaurora.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.