mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linaro-dev@lists.linaro.org,
	Mans Rullgard <mans.rullgard@linaro.org>,
	Jassi Brar <jassisinghbrar@gmail.com>,
	alsa-devel@alsa-project.org,
	Russell King <linux@arm.linux.org.uk>,
	Tony Lindgren <tony@atomide.com>,
	linux-kernel@vger.kernel.org, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.de>, Jarkko Nikula <jhnikula@gmail.com>,
	linux-omap@vger.kernel.org, Liam Girdwood <lrg@ti.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] ASoC: omap: convert per-board modules to platform drivers
Date: Thu, 08 Sep 2011 15:29:11 -0700	[thread overview]
Message-ID: <1315520956.4126.3.camel@finisterre.wolfsonmicro.main> (raw)
In-Reply-To: <3110288.bQbb0H2ME1@wuerfel>

On Thu, 2011-09-08 at 22:28 +0200, Arnd Bergmann wrote:
> On Thursday 08 September 2011 20:05:48 Mans Rullgard wrote:

> > I had the same thought, but I couldn't find a suitable string anywhere.
> > Are you suggesting an if(machine_is_foo()) cascade in omap_init_audio()?

> > I'll be the first to agree this patch is not particularly pretty.

> My general feeling is that practically every time someone writes
> machine_is_*(), they are doing it wrong. There are of course exceptions,
> but I would strongly recommend to have the initialization calling up
> from the board file into more general functions instead of having all
> boards calling the same function which then goes to board specific
> code again.

I have to agree, that seems tasteless. I'd expect something like
triggering registration of devices based off walking down a table of
machine IDs or something. One other issue to consider here is that we
don't want to discourage people from sharing machine drivers while we
can so it can't be completely automatic, it 

Perhaps some sort of generic machine type based mechanism for
instantiating drivers a bit like what's done with DMI might be useful,
video will have a similar issue I guess.


  reply	other threads:[~2011-09-08 23:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08 17:34 Mans Rullgard
     [not found] ` <CABb+yY0b607kDSGU+trycqQuvGMhC-zpHcv20wjgmEcaK7dz8Q@mail.gmail.com>
2011-09-08 18:18   ` Mark Brown
     [not found]   ` <CAG5Tg6UOuztenNid1=YbH9a4ZH5MqV4YhohG+r9R+7F=zXs=CQ@mail.gmail.com>
     [not found]     ` <CAJe_ZhdGaKFU9kVii83KX+TmN9_edcfCU8TohEzJ4oKaQTEgHw@mail.gmail.com>
2011-09-08 19:26       ` Mans Rullgard
2011-09-08 20:28     ` Arnd Bergmann
2011-09-08 22:29       ` Mark Brown [this message]
2011-09-08 22:37         ` Russell King - ARM Linux
2011-09-08 22:47           ` Mark Brown
2011-09-08 23:01             ` Russell King - ARM Linux
2011-09-08 23:59               ` Mark Brown
2011-09-09  8:48                 ` Jassi Brar
2011-09-09  9:41                 ` Russell King - ARM Linux
2011-09-09 16:11                   ` Mark Brown
2011-09-09 19:01                     ` Russell King - ARM Linux
2011-09-09 19:30                       ` Mark Brown
2011-09-09 20:56                         ` Russell King - ARM Linux
2011-09-10 20:37                           ` Arnd Bergmann
2011-09-10 21:43                             ` 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=1315520956.4126.3.camel@finisterre.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=arnd@arndb.de \
    --cc=jassisinghbrar@gmail.com \
    --cc=jhnikula@gmail.com \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=lrg@ti.com \
    --cc=mans.rullgard@linaro.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.de \
    --cc=tony@atomide.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

all inboxes | Powered by JetHome®