From: David Brownell <david-b@pacbell.net>
To: davinci-linux-open-source@linux.davincidsp.com
Cc: Naresh Medisetty <naresh@ti.com>, alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/9] ARM: DaVinci: ASoC: Adds ASoC driver support for TI DM646X EVM platform
Date: Mon, 16 Mar 2009 10:38:05 -0700 [thread overview]
Message-ID: <200903161038.05404.david-b@pacbell.net> (raw)
In-Reply-To: <1237204945-30039-1-git-send-email-naresh@ti.com>
On Monday 16 March 2009, Naresh Medisetty wrote:
> @@ -43,14 +48,14 @@ static int evm_hw_params(struct snd_pcm_substream *substream,
> unsigned sysclk;
>
> /* ASP1 on DM355 EVM is clocked by an external oscillator */
... and on this DM646x EVM ... ?
> - if (machine_is_davinci_dm355_evm())
> + if (cpu_is_davinci_dm355() || cpu_is_davinci_dm646x())
Shouldn't that stay as a machine_is_*() test,
just adding a machine_is_davinci_dm646x_evm() case?
Code tends to get modified by clone-and-modify,
and making this code be cpu-specific instead of
board-specific will thus promote errors.
On top of that, there's currently an effort to
minimize the amount of cpu_is_*() testing found
in drivers. Patches that increase such testing,
especially needlessly increasing it!, seem to be
the wrong direction...
> sysclk = 27000000;
>
> /* ASP0 in DM6446 EVM is clocked by U55, as configured by
> * board-dm644x-evm.c using GPIOs from U18. There are six
> * options; here we "know" we use a 48 KHz sample rate.
> */
> - else if (machine_is_davinci_evm())
> + else if (cpu_is_davinci_dm644x())
> sysclk = 12288000;
>
> else
next prev parent reply other threads:[~2009-03-16 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 12:02 [PATCH 1/9] ARM: DaVinci: ASoC: Adds ASoC driver support for TI DM646X EVM platform Naresh Medisetty
2009-03-16 14:57 ` Mark Brown
2009-03-18 11:37 ` Medisetty, Naresh
2009-03-16 17:38 ` David Brownell [this message]
2009-03-19 17:33 ` Kevin Hilman
2009-03-19 19:19 ` 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=200903161038.05404.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=alsa-devel@alsa-project.org \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=naresh@ti.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.