All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Sebastian Siewior <al+sa@ml.breakpoint.cc>,
	alsa-devel@alsa-project.org, dtor@mail.ru,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org
Subject: Re: [alsa-devel] [RFC] ucb1400 touchscreen,	irq auto probing and ac97 with its	private field
Date: Thu, 24 Apr 2008 18:09:52 +0200	[thread overview]
Message-ID: <s5hr6cvb5f3.wl%tiwai@suse.de> (raw)
In-Reply-To: <20080424145749.GB22369@sirena.org.uk>

At Thu, 24 Apr 2008 15:57:52 +0100,
Mark Brown wrote:
> 
> On Thu, Apr 24, 2008 at 04:04:59PM +0200, Sebastian Siewior wrote:
> 
> > I've sent a RFC to the alsa mailing list [1] about adding an extra field in
> > order to pass the IRQ from the AC97 driver to the ucb1400 driver. The
> > result was:
> 
> > Now I'm curious what solution the people here prefer:
> > - adding a private field [1] (my favorite)
> 
> As I indicated in reply to your initial RFC any such private field
> ought to be a void * in order to allow other information to be passed
> through to drivers.

The problem with void * is that you don't know what it really is.
Yes, it's exactly the purpose - to be generic.  But, this means that
the true shape of the tossed data from the ac97 controller driver to
the platform driver is anonymous, too.

So, from that perspective, I find 'int irq' better to assure a strong
binding.  Of course, if there are more other use cases, this argument
doesn't apply well.

> Note that this will also need changes in all the relevant AC97 drivers
> to support getting the private data from platform/machine definition
> code to the relevant driver using whatever methods are appropriate for
> the platform.

What kind of data are needed be passed?


thanks,

Takashi

  parent reply	other threads:[~2008-04-24 16:09 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24 14:04 [RFC] ucb1400 touchscreen, irq auto probing and ac97 with its private field Sebastian Siewior
2008-04-24 14:32 ` Jaroslav Kysela
2008-04-24 14:35   ` Sebastian Siewior
2008-04-24 14:57 ` Mark Brown
2008-04-24 15:02   ` Mark Brown
2008-04-24 15:02   ` [alsa-devel] " Mark Brown
2008-04-24 15:44     ` Sebastian Siewior
2008-04-24 21:33       ` [alsa-devel] " Mark Brown
2008-04-24 15:35   ` Sebastian Siewior
2008-04-24 20:04     ` Mark Brown
2008-04-24 16:09   ` Takashi Iwai [this message]
2008-04-24 18:56     ` [alsa-devel] " Mark Brown
2008-04-25  7:02       ` Takashi Iwai
2008-04-25  7:10         ` [alsa-devel] " Jaroslav Kysela
2008-04-25  7:18           ` Takashi Iwai
2008-04-25  7:35             ` Jaroslav Kysela
2008-04-25  7:46               ` Sebastian Siewior
2008-04-25  7:52               ` Takashi Iwai
2008-04-25  8:23                 ` Jaroslav Kysela
2008-04-25  9:17                   ` Takashi Iwai
2008-04-25  9:45                     ` [alsa-devel] " Jaroslav Kysela
2008-04-25 10:05                       ` Takashi Iwai
2008-04-25 10:18                         ` Jaroslav Kysela
2008-04-25 10:54                   ` Sebastian Siewior
2008-04-25 11:10                     ` Takashi Iwai
2008-04-25 11:22                       ` [alsa-devel] " Jaroslav Kysela
2008-04-25 13:04                         ` Takashi Iwai
2008-04-25 12:49                       ` Sebastian Siewior
2008-04-25 13:01                         ` Takashi Iwai
2008-04-25 15:31               ` Dmitry Torokhov
2008-04-25  9:51         ` Mark Brown
2008-04-25 10:15           ` Takashi Iwai
2008-04-25 10:20             ` Jaroslav Kysela
2008-04-25 10:28             ` [alsa-devel] " 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=s5hr6cvb5f3.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=al+sa@ml.breakpoint.cc \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dtor@mail.ru \
    --cc=linux-input@vger.kernel.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 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.