From: Takashi Iwai <tiwai@suse.de>
To: Sebastian Siewior <al+sa@ml.breakpoint.cc>
Cc: Jaroslav Kysela <perex@perex.cz>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
dtor@mail.ru, Dmitry Torokhov <dmitry.torokhov@gmail.com>,
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 15:01:39 +0200 [thread overview]
Message-ID: <s5hprsejdfw.wl%tiwai@suse.de> (raw)
In-Reply-To: <20080425124908.GA7152@Chamillionaire.breakpoint.cc>
At Fri, 25 Apr 2008 14:49:08 +0200,
Sebastian Siewior wrote:
>
> >> What I intended in first place is to allocate a private field in the bus
> >> struct so can pass informations to the lower driver.
> >
> >As mentioned in my earlier mail, I'm fine with your first patch. The
> >problem occurs when we generalize it.
> Generalize? You mean once you need an array of multiple parameters like
> struct ressource where the controler driver and device driver are
> independent and don't know each other?
Right, that's why void pointer was proposed and I'm against. The
controller driver and the device driver are independent and
implemented so. If they have the exlusive tight connection, then you
must have no problem. But, you can bind any device driver to any
controller driver in theory as long as they use the same bus, and
there is no check to prevent it.
Takashi
next prev parent reply other threads:[~2008-04-25 13:01 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 ` [alsa-devel] " Mark Brown
2008-04-24 15:44 ` Sebastian Siewior
2008-04-24 21:33 ` [alsa-devel] " Mark Brown
2008-04-24 15:02 ` Mark Brown
2008-04-24 15:35 ` [alsa-devel] " 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 [this message]
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=s5hprsejdfw.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 \
--cc=perex@perex.cz \
/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.