Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "chaithrika" <chaithrika@ti.com>
To: 'Mark Brown' <broonie@opensource.wolfsonmicro.com>
Cc: 'Naresh Medisetty' <naresh@ti.com>,
	alsa-devel@alsa-project.org, 'Steve Chen' <schen@mvista.com>,
	davinci-linux-open-source@linux.davincidsp.com,
	'Pavel Kiryukhin' <pkiryukhin@ru.mvista.com>
Subject: Re: [PATCH v3 5/6] ARM: DaVinci: ASoC: Add mcasp	support for DM646x
Date: Thu, 4 Jun 2009 15:27:49 +0530	[thread overview]
Message-ID: <000001c9e4fa$eb726730$c2573590$@com> (raw)
In-Reply-To: <20090603121236.GA25676@sirena.org.uk>

On Wed, Jun 03, 2009 at 17:42:37, Mark Brown wrote:
> On Wed, Jun 03, 2009 at 04:33:51PM +0530, chaithrika wrote:
> 
> > > Why is the McASP driver using platform data called
> > > 'evm_snd_patform_data'?
> > > This suggests that there's some abstraction problem with the
separation
> > > between the machine and McASP drivers.
> 
> > The platform data consists of information specific to EVM and SoC 
> > and is used by the platform driver (McASP driver) to get relevant 
> > data. Therefore it seems right to use the platform data here.
> > Please let me know your opinion.
> 
> It's not the *use* of platform data, it's the fact that you are calling
> this *EVM* platform data.  This suggests an abstraction issue somewhere
> along the line - presumably not all machines with these processors are
> EVMs.  Some of the other issues myself and David identified suggest that
> there are some issues there.
> 
> If this is system-specific configuration data purely for the McBSP port
> it shouldn't mention the EVMs in the name.
> 

OK. I will rename the structure to 'snd_platform_data'. 

Thanks, 
Chaithrika

      reply	other threads:[~2009-06-04  9:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28  9:11 [PATCH v3 5/6] ARM: DaVinci: ASoC: Add mcasp support for DM646x Chaithrika U S
2009-05-30 16:26 ` Mark Brown
2009-06-01 10:30   ` chaithrika
2009-06-03 11:03   ` chaithrika
2009-06-03 12:12     ` Mark Brown
2009-06-04  9:57       ` chaithrika [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='000001c9e4fa$eb726730$c2573590$@com' \
    --to=chaithrika@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=naresh@ti.com \
    --cc=pkiryukhin@ru.mvista.com \
    --cc=schen@mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox