From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Sebastian Siewior <al+sa@ml.breakpoint.cc>,
ALSA development <alsa-devel@alsa-project.org>,
linux-input@vger.kernel.org
Subject: Re: [alsa-devel] [RFC] ucb1400 touchscreen, irq auto probing and ac97 with its private field
Date: Fri, 25 Apr 2008 11:31:03 -0400 [thread overview]
Message-ID: <20080425112954.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0804250931050.7882@tm8103.perex-int.cz>
On Fri, Apr 25, 2008 at 09:35:47AM +0200, Jaroslav Kysela wrote:
> On Fri, 25 Apr 2008, Takashi Iwai wrote:
>
> > > Sure. I applied the simple 'void *device_private_data' patch, because
> > > current usage request is really trivial. We can implement complex code to
> > > handle data for multiple "extra" devices on AC97 bus later.
> >
> > Actually, it's not "used" yet. The ucb1000 reads the data but no one
> > stores yet. And, if its usage request is trivial, we should use "int
>
> Yes, I hope that the appropriate initialization code will be added to SoC
> drivers, too.
>
> > irq" as in the original patch instead of void data and cast.
>
> But other SoC (or other) drivers might want to pass to extra devices on
> AC97 bus something different or more complex. Mark Brown already noted
> that. I would keep it as 'void *'.
Need to pass irq data will be fairly common so we should probably have
it in its own right and allow additional data be attached via a void
*.
--
Dmitry
next prev parent reply other threads:[~2008-04-25 15:32 UTC|newest]
Thread overview: 33+ 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 ` [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 ` [alsa-devel] " Takashi Iwai
2008-04-24 18:56 ` 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 [this message]
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=20080425112954.ZZRA012@mailhub.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=al+sa@ml.breakpoint.cc \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-input@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).