All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Hebbar, Gururaja" <gururaja.hebbar@ti.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"Nori, Sekhar" <nsekhar@ti.com>,
	"davinci-linux-open-source@linux.davincidsp.com"
	<davinci-linux-open-source@linux.davincidsp.com>,
	"'sudhakar.raj@ti.com" <'sudhakar.raj@ti.com>,
	"alsa-user@lists.sourceforge.net"
	<alsa-user@lists.sourceforge.net>, "Girdwood, Liam" <lrg@ti.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: How to handle parameter variation across different boards but same platform
Date: Wed, 4 Jul 2012 14:17:50 +0100	[thread overview]
Message-ID: <20120704131749.GZ4111@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1BAFE6F6C881BF42822005164F1491C33EA3532A@DBDE01.ent.ti.com>


[-- Attachment #1.1: Type: text/plain, Size: 509 bytes --]

On Wed, Jul 04, 2012 at 12:45:03PM +0000, Hebbar, Gururaja wrote:

You should fix your mailer to word wrap at less than 80 columns.

> Using machine_is_xxx() is not sufficient because there are 2 other
> boards on same Platform/machine but with different values.

> So, how to specify these parameters for the new board?

What do you mean by "board"?  If these are plugin modules for your
platform you need to either identify this at runtime and register a
different machine driver or select at compile time.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: How to handle parameter variation across different boards but same platform
Date: Wed, 4 Jul 2012 14:17:50 +0100	[thread overview]
Message-ID: <20120704131749.GZ4111@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1BAFE6F6C881BF42822005164F1491C33EA3532A@DBDE01.ent.ti.com>

On Wed, Jul 04, 2012 at 12:45:03PM +0000, Hebbar, Gururaja wrote:

You should fix your mailer to word wrap at less than 80 columns.

> Using machine_is_xxx() is not sufficient because there are 2 other
> boards on same Platform/machine but with different values.

> So, how to specify these parameters for the new board?

What do you mean by "board"?  If these are plugin modules for your
platform you need to either identify this at runtime and register a
different machine driver or select at compile time.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120704/076061df/attachment-0001.sig>

  reply	other threads:[~2012-07-04 13:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-04 12:45 How to handle parameter variation across different boards but same platform Hebbar, Gururaja
2012-07-04 12:45 ` Hebbar, Gururaja
2012-07-04 13:17 ` Mark Brown [this message]
2012-07-04 13:17   ` Mark Brown
2012-07-04 13:43   ` Hebbar, Gururaja
2012-07-04 13:43     ` Hebbar, Gururaja
2012-07-04 14:01     ` Mark Brown
2012-07-04 14:01       ` Mark Brown
2012-07-04 14:17       ` Hebbar, Gururaja
2012-07-04 14:17         ` Hebbar, Gururaja
2012-07-04 14:27         ` Mark Brown
2012-07-04 14:27           ` Mark Brown
     [not found]           ` <20120704142745.GC4111-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-07-05  5:42             ` Vaibhav Hiremath
2012-07-05  5:42               ` Vaibhav Hiremath
2012-07-05  8:32               ` Arnd Bergmann
2012-07-05  8:32                 ` Arnd Bergmann
2012-07-05  9:38                 ` Mark Brown
2012-07-05  9:38                   ` 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=20120704131749.GZ4111@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc='sudhakar.raj@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=gururaja.hebbar@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lrg@ti.com \
    --cc=nsekhar@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.