linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Jon Smirl" <jonsmirl@gmail.com>,
	linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org,
	"Grant Likely" <grant.likely@secretlab.ca>
Subject: Re: [alsa-devel] [PATCH 2/2] Allow a custom ASOC machine driver with soc-of-simple
Date: Wed, 23 Jul 2008 11:16:17 -0400	[thread overview]
Message-ID: <9e4733910807230816m474af04ch9b6650cdbb96ffec@mail.gmail.com> (raw)
In-Reply-To: <20080723151431.GA22926@sirena.org.uk>

On 7/23/08, Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
> On Wed, Jul 23, 2008 at 10:09:01AM -0400, Jon Smirl wrote:
>  > On 7/23/08, Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
>
>
> > > ...this doesn't just allow a custom machine driver, it requires that
>  > >  something configures at least the machine name.  That's not a problem
>  > >  from the ASoC point of view but possibly from the PowerPC side?
>
>  > You have to configure at least the name. Otherwise if the machine
>  > driver is the last to register, how do you know to hold off the final
>  > registration and wait for the machine driver to appear?
>
>
> I understand why you have made this change but it's a substantial change
>  which should at least be documented in the changelog (I'd expect to see
>  some mention of how this is supposed to be configured, for example).
>  I'd also expect something to handle the existing user.

This is a modification to Grant's new driver. Grant is the only other user.

>
>  Like I said, I'm not entirely sure that you're supposed to be using this
>  driver if you want a machine driver: this is a machine driver and I'm
>  not sure if it's supposed to cover all cases or not.  Grant?
>
>
>  > Or is it ok for me to change these after the platform device has been created?
>  >               of_soc->dai_link.ops = machine_ops;
>  >               of_soc->machine.name = machine_name;
>
>
> No.
>


-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2008-07-23 15:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22 23:53 [PATCH 1/2] Support internal I2S clock sources on MPC5200 Jon Smirl
2008-07-22 23:53 ` [PATCH 2/2] Allow a custom ASOC machine driver with soc-of-simple Jon Smirl
2008-07-23  5:30   ` Stephen Rothwell
2008-07-23 10:53   ` [alsa-devel] " Mark Brown
2008-07-23 14:09     ` Jon Smirl
2008-07-23 15:14       ` Mark Brown
2008-07-23 15:16         ` Jon Smirl [this message]
2008-07-23 15:36           ` Mark Brown
2008-07-27  1:14         ` Grant Likely
2008-07-24  6:20       ` filling dummy struct snd_dma_buffer dinesh
2008-07-27  1:12   ` [PATCH 2/2] Allow a custom ASOC machine driver with soc-of-simple Grant Likely
2008-07-27  4:44     ` Jon Smirl
2008-07-27  5:29       ` Grant Likely
2008-07-27 14:07         ` Jon Smirl
2008-07-23 10:36 ` [alsa-devel] [PATCH 1/2] Support internal I2S clock sources on MPC5200 Mark Brown
2008-07-27  2:05 ` Grant Likely
2008-07-27  4:48   ` Jon Smirl

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=9e4733910807230816m474af04ch9b6650cdbb96ffec@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).